-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Sonoff TRVZB Schedule (composite) entity state is too long for HA #23199
Comments
Same problem here |
Maybe related to #19788 #home-assistant/core#103141 and #16460? I have this messages:
|
same problem on z2m 1.38.0. Logger: homeassistant.components.mqtt.sensor Cannot update state for entity sensor.office_trv_weekly_schedule after processing payload on topic zigbee2mqtt/Office Trv. The requested state (477) exceeds the maximum allowed length (255). Fall back to unknown, failed state: {'friday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'monday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'saturday': '00:00/16 07:00/19 10:00/19 10:00/19 10:00/19 23:00/16', 'sunday': '00:00/16 07:00/19 10:00/19 10:00/19 10:00/19 23:00/16', 'thursday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'tuesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'wednesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16'} |
Pushed a fix, can you check if it works? Changes will be available in the dev branch in a few hours from now. |
Thanks for doing this. I've tried the dev branch. I think that this truncates the state length for a text entity. Am I right in thinking this is separate to a sensor entity (this is how this field is currently represented)? It doesn't solve the problem with errors for me. |
Yes this should truncate the text, I'm not sure what exactly this error means, @jbouwh, what does the following error mean?
|
@Koenkk Maybe because JSON is expected and the message uses single quotes? |
@raarts I don't think the JSON is interpreted because I guess this error is for the text sensor? |
I was just guessing, reading it back the tone was not how I intended, sorry about that. |
Can cofirm that the error still exist. `Logger: homeassistant.components.mqtt.sensor Invalid state message '{'friday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'monday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'saturday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'sunday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'thursday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'tuesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'wednesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16'}' from 'zigbee2mqtt/Badezimmer Heizung ' `Logger: homeassistant.components.mqtt.sensor Cannot update state for entity sensor.badezimmer_heizung_weekly_schedule after processing payload on topic zigbee2mqtt/Badezimmer Heizung . The requested state (477) exceeds the maximum allowed length (255). Fall back to unknown, failed state: {'friday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'monday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'saturday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'sunday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'thursday': '00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20', 'tuesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16', 'wednesday': '00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16'} i have try to set every day only to 00:00/20 but on safe it create 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 00:00/20 . Setup Info: What did you expect to happen? How to reproduce it (minimal and precise) Zigbee2MQTT version Adapter firmware version Adapter Setup Greatz |
Any update about this issue? |
Same problem here. |
|
Still exist on 1.39.1. :( |
I'm also still seeing the same warning with latest 1.39.1 release. |
I cannot reproduce this issue with my own TRVZB on 1.39.1, can you try to remove the device via the z2m frontend (such that it disappears from HA) and re-pair it? |
I will check it tommorow and let you know. |
I've tried deleting and re-pairing. I'm sorry to say that it still gives me the same error. If you don't use this particular entity, you can of course disable it, which has solved the problem for me! |
Confirm. Delete all trv. Repair them. Error comes back. Disable the enteiti Remove the errors. I Do Not use the sheudle. So it is Not a Problem die me. But it still exist. :) Great |
Problem still exists |
Problem still exists in TRVZB version 1.1.5. |
Finally managed to find and fix the issue! Changes will be available in the dev branch in a few hours from now. |
@Koenkk would it be possible to change the behaviour of the converter to instead split it out into separate attributes for each day:
etc rather than merging the value and truncating them? |
@hilburn That would be really helpful. Currently the weekly_schedule attr is useless in home assistant because it is cut off. As a workaround, you can write a separate mqtt sensor for each day of the week.
|
What happened?
Repeated errors in HA logs because the entity state is too long
What did you expect to happen?
Perhaps split in to multiple entities
How to reproduce it (minimal and precise)
Pair valve, state message rejected.
Zigbee2MQTT version
1.38.0
Adapter firmware version
zStack3x0 20220219 and ConBee2/RaspBee2 0x26780700
Adapter
Sonoff ZB-Dongle-P and ConBee2
Setup
Container on Debian VM / AMD Ryzen processor
Debug log
No response
The text was updated successfully, but these errors were encountered: