Adding a new Mold Helper requires Restart to display values
andyfrei opened this issue · 6 comments
The problem
Is that intended?
Everytime you add a new Mold-Helper (not the config) you have to restart Home Assistant in order to get it calculated?
Other helpers added by the UI are there after a browser refresh so I'm assuming this is not what a helper added via UI should work like, but I may miss something here.
If it is intended the documentation should state that more clear.
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Mold Indicator
Link to integration documentation on our website
https://www.home-assistant.io/integrations/mold_indicator
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
After a restart of Home Assistant all works as expected
That seems odd and has not been the case for all the tests.
Anything in the logs? Are the sensors it's based on available and usable? Same if you wait a bit longer?
Hi @gjohansson-ST
Just figured out that even changing a calibrationfaktor of an existing mold sensor makes the sensor unavailable.
What do you mean by "a bit longer" = ?
Just changed a calibration faktor now and created a new dummy one aswell, reporting aswell "not available" currently. Will report later on the behaviour.
It should make it unavailable but only for a short period until it collected all the information again (as it reloads).
I was just thinking if you wait half a minute and then refresh your screen or if it really never comes back until you restart HA completely.
I could not reproduce myself as when I create them I get it unavailable, I press F5 to refresh my browser, then I see it working perfectly reporting ok.
So its more then 5mins ago now for the creation and the clibration factor change, they both report still unavailable, even after a browser refresh aswell in the developer tools.
Yes, I understood you incorrectly. I see it too that it's not reporting but stays unavailable.
I will look into it.