Closed breti closed 2 years ago
As long as i could see. This is only related to system variables. Or am i wrong? This is something that has been reported with versions < 1.1.4, but should not happen with versions >= 1.1.4.
Please update to 1.3.0. If issue still exists add the following to the configuration.yaml:
logger:
default: info
logs:
hahomematic: debug
custom_components.homematicip_local: debug
[EDIT] updated 1.2.2 to 1.1.4
What do you restart? HA only or the whole HAOS (with RaspberryMatic-Addon)?
Yes, you're right, it affects all system variables sensors. I've restarted HA, not HAOS/VM.
I've just updated to 1.3.1 and HA 2022.5.2. Now the error has disappeared again for the time being.
Since I don't know when it will occur again, enabling debugging is difficult. I guess enabling that now and letting it run until further notice is not an option because it floods the logfile?
Yes, permanent debugging is a mess. Maybe INFO is enough. Please close this issue for now and reopen it if the issue re-occures.
OK. Thanks.
Same again with 1.5.4. I'm still unable to reproduce this issue so I have no debug logs.
Thanks for the update.
I've just updated to HA 2022.6.0 and custom_homematic to 1.7.2. After restarting HA, all system var sensors were unavailable again. Everything else is working fine.
Logging configuration was:
logger:
default: info
logs:
hahomematic: debug
custom_components.homematicip_local: debug
Hope you find something helpful in the log. home-assistant.log config_entry-homematicip_local-35822aacb390d7028935d6c727a3c230.json(2).txt
That was helpful, but i need to add more debug logging to the next version.
I havent't found a cause, but was able to identify where logging must be intensified. Please update to 1.7.3 before next HA update. Another debug session should give more insights.
Updated to HA 2022.6.1 and custom_homematic 1.7.3. No Sys Var issue this time.
So far i haven't done anything to fix this issue. I just extended debug loggging. Ich think next HA update will be there soon.
Please update to >= 1.8.4 before updating HA to 2022.6.2
Updated to Homematic(IP) Local 1.8.4 and Home Assistant Core 2022.6.2. Again no issue.
Updated to Homematic(IP) Local 1.8.5 and Home Assistant Core 2022.6.3. Issue is back again. Logs attached.
config_entry-homematicip_local-35822aacb390d7028935d6c727a3c230.json(1).txt home-assistant.log
Looks like your platform setup (sensor, binary_sensor) is somehow delayed. This might be the root cause why sometimes SVs are available and sometimes not.
1.8.6 should cover a delayed platform start.
Thanks a lot. I'll try and report back.
Updated to Homematic(IP) Local 1.8.6 and Home Assistant Core 2022.6.4. No issue.
Updated to Home Assistant Core 2022.6.5 without any issues.
Thanks for your support. Please close this issue for now and reopen it if the issue re-occurs.
OK. Thanks for fixing!
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.2.2
Home Assistant version (if applicable): 2022.5.1
CCU version:
Problem-relevant configuration:
Do you use tls? n Do you use callback? n Do you use username and password? y Which interfaces do you use? BidCoS-RF
Describe the bug A clear and concise description of what the bug is.
Sometimes after restarting Home Assistant all CCU sensors (number of service messages, number of alarms, duty cycle etc.) are "unavailable". Everything else works - I can control actuators and get values from sensors like door contacts.
The whole thing has occurred several times with different versions, but is not really reproducible. Currently the error exists again after I updated from HA 2022.5.0 to 2022.5.1 yesterday. Is there any information I can collect that can be helpful in debugging before I restart HA?
In the log I do not see any messages from the Homematic component.
To Reproduce random after restart of HA
Screenshots (if applicable)
Relevant HA log entries (full log) There's nothing logged related to HM
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.