Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call manual update on sensor #38

Open
Kh3nsu opened this issue Apr 14, 2022 · 8 comments
Open

Call manual update on sensor #38

Kh3nsu opened this issue Apr 14, 2022 · 8 comments
Labels
bug Something isn't working

Comments

@Kh3nsu
Copy link

Kh3nsu commented Apr 14, 2022

Hello,

Is there a way to call an update on a sensor?
As example after I write something to the heat pump I need an sensor update instantly. Sadly the option update_immediately_after_write does not work for me. Idk why, I put it in the configuration.yaml part. Or does it belong to every sensor I want to get updated after a write?

Or even better is there maybe a service luxtronik.write? (luxtronik.update or something?)

@Kh3nsu
Copy link
Author

Kh3nsu commented Apr 16, 2022

Hey I still haven't found a way to do so :(
I also tried update_immediately_after_write again, didn't work .

@Bouni
Copy link
Owner

Bouni commented Apr 16, 2022

Sorry I'm not near a computer until Wednesday (Easter holiday)
That's the earliest I can take a look....

@Kh3nsu
Copy link
Author

Kh3nsu commented Apr 16, 2022

That's no problem ^^ No rush.
I also noticed an error popping up when trying to use homeassistant.update_entity:

Logger: homeassistant.helpers.entity_component
Source: helpers/entity_component.py:41
First occurred: 14. April 2022, 17:53:51 (2 occurrences)
Last logged: 14. April 2022, 17:53:54

Forced update failed. Component for luxtronik.haus_warmwasser_soll not loaded.

@Kh3nsu
Copy link
Author

Kh3nsu commented Apr 21, 2022

Heyhooo is there anything new about this? ^^

@Bouni
Copy link
Owner

Bouni commented Apr 26, 2022

Hi, no not yet, Covid struck and made Easter not so funny for me and my family 😓

@Bouni Bouni added the bug Something isn't working label Apr 26, 2022
@Bouni
Copy link
Owner

Bouni commented Apr 29, 2022

I just had a quick look at this and added a few logging calls to the custome_component as well as the luxtronik lib.
It is clear that a write n combination with the update_immediately_after_write trigers an imediate read:

home-assistant  | 2022-04-29 08:07:02 ERROR (SyncWorker_1) [Luxtronik] WRITE
home-assistant  | 2022-04-29 08:07:02 ERROR (SyncWorker_1) [custom_components.luxtronik] Imediately update triggered!
home-assistant  | 2022-04-29 08:07:02 ERROR (SyncWorker_1) [Luxtronik] READ

But I also see that the HA state of the parameter I've teste changes state only after a while, so I guess that the throttle kicks in somehow ...

@Kh3nsu
Copy link
Author

Kh3nsu commented Jun 19, 2022

Heyyy,

is there maybe anything new about this? :D

@Bouni
Copy link
Owner

Bouni commented Jun 20, 2022

Nope, I have to find out if I can somehow force an update and overcome the throttle mechanism of Home Assistant ....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants