You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a long time I have been trying to convince a family member to make the step from his Trust ICS-2000 to Home Assistant, but after multiple tries and having issues with the ZLED-RGB9 lights, I bought some myself to dive deeper into the issue.
The light is always reported to be offline after set availability period as it does not respond to pings. Diving deeper into the issue it seems like it tries to ping a non existing cluster.
It seems like it is looking for endpoint 1, which only consists of the touchlink clusters, where as genBasic and other clusters live in endpoint 2. After which the ping fails and it states that the device is offline.
Another strange issue, which I don't think can be solved quite easily, is that it's in the same room with the coordinator, as well as 3 other routers, it reports a very low LQI. Always <70 and it is only situated 2.5 meters from the coordinator and less than 15cm from another router (lightbulb). It seems to always respond, so it is not a big issue.
What did you expect to happen?
That the light would stay online and not get greyed out in the Home Assistant front-end. 😂
(Currently bypassed this by adding availability: false to the device config, but would be great to have a proper state report)
How to reproduce it (minimal and precise)
Not much needed, just add the light and make sure you have the availability feature enabled.
YannickvanVugt
changed the title
Trust ZLED-RGB9 trying to ping wrong endpoint/cluster
Trust ZLED-RGB9 ping fails due to wrong endpoint/cluster target
Jun 29, 2023
What happened?
For a long time I have been trying to convince a family member to make the step from his Trust ICS-2000 to Home Assistant, but after multiple tries and having issues with the ZLED-RGB9 lights, I bought some myself to dive deeper into the issue.
The light is always reported to be offline after set availability period as it does not respond to pings. Diving deeper into the issue it seems like it tries to ping a non existing cluster.
It seems like it is looking for endpoint 1, which only consists of the touchlink clusters, where as genBasic and other clusters live in endpoint 2. After which the ping fails and it states that the device is offline.
Another strange issue, which I don't think can be solved quite easily, is that it's in the same room with the coordinator, as well as 3 other routers, it reports a very low LQI. Always <70 and it is only situated 2.5 meters from the coordinator and less than 15cm from another router (lightbulb). It seems to always respond, so it is not a big issue.
What did you expect to happen?
That the light would stay online and not get greyed out in the Home Assistant front-end. 😂
(Currently bypassed this by adding
availability: false
to the device config, but would be great to have a proper state report)How to reproduce it (minimal and precise)
Not much needed, just add the light and make sure you have the availability feature enabled.
Other people reporting the same issue
I am not completely sure how to interpret the code here, but could it be missing some details?
Zigbee2MQTT version
1.31.2
Adapter firmware version
20230507
Adapter
Slaesh's CC2652RB stick, but happening with other adapters too.
Debug log
Warning 2023-06-29 22:38:25Failed to ping 'Inloop Slaapkamer Yannick Trust 1' (attempt 1/2, Read 0x00158d00011ec27a/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 21992 - 1 - 55 - 0 - 1 after 10000ms))
The text was updated successfully, but these errors were encountered: