Closed breti closed 2 years ago
I wrote it to the release notes of 1.11.0
I read them, but I obviously I didn't understand them.
You mean this one:
Use entity is_valid for state
Entities are now shown as unknown, as long as HA has not received any events from the CCU, or was not able to fetch data initially.
Old behaviour was to display a DEFAULT value.
As soon as events have been received from the CCU the state will switch to the correct state.
This should be relevant, if HA has been restarted shortly after the CCU has been restart.
See [Readme](https://github.com/danielperna84/custom_homematic#noteworthy-about-entity-states) for further information.
This means that it can take 24 hours for the RHS, for example, until the status is reported by the cyclic report.
With the battery LOWBAT sensors, not a single one has been updated so far, even after 12 hours of waiting time.
Is there no way to pull the state from the CCU, or what's the reason for this?
It's been an illusion that you saw real values when restarting HA and CCU. Binary_sensors just displayed default values.
The reasons can be found in these threads:
Feel free to comment in 1 or 2
None of the HM LOWBAT sensors have recovered so far (Gaswaage is an ESPhome device).
Except from diagnostic entities like LOWBAT and RSSI_XXX: What is state of other entity types?
No "Servicemeldungen" or "Alarmmeldungen" on CCU.
Same here with my HM-ES-TX-WM RSSI and LOWBAT are only and always in unknown state, energy_counter and power is updating as expected.
There seems to be a problem, that the CCU is not sending periodical events on the maintainance channel (0) for some parameters. Other parameters like RSSI_DEVICE, RSSI_PEER and SABOTAGE also seem to be affected.
I think we should close this ticket and go on with the discussion https://github.com/danielperna84/hahomematic/discussions/12#discussioncomment-3114694 to find a solution.
DONT'T DELETE THIS. Please answer all questions as good as possible.
Make sure you have read the documentation at https://github.com/danielperna84/custom_homematic#custom_homematic.
Make sure you are running the latest version of hahomematic or it's custom_component (and Home Assistant) before reporting an issue.
custom_component/hahomematic version (if applicable): 1.11.1
Home Assistant version (if applicable): 2022.7.4
CCU version:
Problem-relevant configuration:
Do you use tls? n Do you use callback? n Do you use username and password? n Which interfaces do you use? BidCoS-RF
Describe the bug A clear and concise description of what the bug is.
I've updated RaspberryMatic, hahomematic and HomeAssistant. Now several sensors and actors show state "unknown" until the state changes. Restarting the RaspverryMatic Add-On or HA doesn't help.
Two switches - they show on/off buttons until the state changes once.
Rotation Handle Sensors - state unbekannt until state changes
LOWBAT sensors - state unbekannt, even after hours
To Reproduce Steps to reproduce the behavior:
I don't know...
Screenshots (if applicable)
Relevant HA log entries (full log)
log.txt
Diagnostic Information (available on every device)
Expected behavior A clear and concise description of what you expected to happen.
Additional context Add any other context about the problem here.