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
KNX Switch state not change #43424
Comments
Is it correct that the status is not initialized correctly after startup, but once set from HA or KNX it is fine again? The initialization problem is already identified and we'll try to fix it soon. (switches and lights don't support context_timeout. Only binary_sensor does) |
Yes only on initialization HA startup, thanks |
I have the same issue and had to revert to 0.117.6 for now. If there are any logs or debug info I can provide, I am happy to help. I'm not a dev however, so wouldn't know how to debug it by myself. |
Hello, I have as well the same issue. The state address is not read by HA. (0.118.2). I have this issue for lights and switches. Hardware: MDT HA 0.117.6 was working. |
Seeing the same issue also. I have a switch that triggers an automation and it doesn't work any more. |
Have same problem after version 0.118.2 - my binary_sensors stoped working, a have added contex_timeout to settings but it only helped for couple of minutes after restart, on next day can't switch buttons anymore. i have connected automations in ha to triton. Reverting to 0.117.6 for now. |
The problem
After Updating to 0.118.0, the status of all switches show "off" (most of them are on).
The status is not updated.
The status of the lights/cover is correct, however.
I don't use context_timeout neither in light nor in switch.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
No logs or erros
Additional information
The text was updated successfully, but these errors were encountered: