-
Notifications
You must be signed in to change notification settings - Fork 510
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
Moes BHT-006 loses connection #680
Comments
Have you found any solution? Mine does the same thing. |
Same issue here. The behavior Schmarni decribed is what I had from the beginning on and I was able to get it working correctly when I added "debounce: 1". Not it is back and unclear as to where this comes from... |
I'll try and let you know if it works for me too. |
My solution now is that I sent the thermostat back and bought another one. Now it works very well. The new one ist the BEOK TGM50-ZB-WP. |
I agree the Moes devices are not very reliable. I have some radiator units that have similar topics. |
I've been experimenting with what you suggested and other options, but it's still unstable. The last one I bought from moes |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Description of the issue
I integrated the Moes thermostat into z2m. When I reconnect it, the connection remains for about 2 - 5 minutes. After this time I can no longer make any changes and the card in the dashboard freezes at the current settings. Settings on the card are not carried out. The value of the LQI constantly jumps from 20 to 80 to 100 and back. However, if the automation for the heating control changes the value, this is displayed on the thermostat itself and it also works. Only the values in z2m do not change.
I also noticed in the log that a log is sometimes created several times per second due to fluctuations in the LQI. Could this accumulation of logs possibly cause the device to crash?
Example:
Addon version
1.42.0-2
Platform
Core
2024.12.5
Supervisor
2024.12.0
Operating System
14.1
Logs of the issue (if applicable)
no information in loggfile
The text was updated successfully, but these errors were encountered: