Open thomaschampagne opened 1 week ago
Same issue over here, also occurring since update to 1.40.10 also using a CC2531 in case that is relevant. After a zigbee2mqtt it will work again for some hours. did not time it but somewhere in the 6-8 hour range sounds right.
please do NOT use CC2531 anymore - it's really weak in 2024 and not worth to deal with
do consider Upgrade to any CC2652x Coordinator - these are more stable & powerful
CC2531 works as Router flawless
please do NOT use CC2531 anymore - it's really weak in 2024 and not worth to deal with
do consider Upgrade to any CC2652x Coordinator - these are more stable & powerful
CC2531 works as Router flawless
Ok but this is not the solution to this problem. Many people are probably still using the CC2531 and it should be also fixed for project consistency no?
for sure this is the Solution - i doubt anyone is willing to try fix Problems for the outdatet CC2531
for sure this is the Solution - i doubt anyone is willing to try fix Problems for the outdatet CC2531
I have been using zigbee2mqtt for over 6 years (started on version 0.2.0) with a CC2531 without much issues. Back then it was basically the only supported option. I understand that there are now more (and better options) and before this issue happened already ordered a new coordinator based on CC2652.
Phasing out support for CC2531 is something that could happen but would need a proper plan and communication to not alienate loyal zigbee2mqtt users who have been using the project for years with a device that was recommended when they started out.
Just not fixing issues because it is old is certainly not the way to go.
thats true but for now CC2531 is not recommended anymore (and definitely for more than a Year) -> https://www.zigbee2mqtt.io/guide/adapters/zstack.html#not-recommended-cc2530-cc2531-cc2538
I can certainly understand if some People find this stupid, but that's the way it is - Sometimes it's time to shed old braids
I have no problem with deprecating old hardware, it makes sense from a maintenance perspective. My only point is that is should be done thoughtfully with a good (communication) plan. I did see that the CC2531 was "not recommended" anymore, but to me that indicated something completely different than deprecated/no longer supported.
@lux73 I’ve decided to upgrade my hardware after you pointed out that the CC2531 is deprecated and not recommended.
I found this CC2652P dongle: https://www.aliexpress.us/item/3256805998875331.html
There's 2 chips variant : CP2102N or CH9102X.
Thanks for your feedback :)
Q1: i wish i could - i only have Experience with CC2652RB - for me this Stick works very reliable & fast with latest FW 20240710 with actually 59 Devices
btw i have started with CC2531 few Years ago - but from the beginning I kept having inexplicable problems with it
Q2: any USB Extension Cable should work (and really recommended even with CC2652x based Coordinator) - no matter if 2.0 or 3.x Cable
Q1: i wish i could - i only have Experience with CC2652RB - for me this Stick works very reliable & fast with latest FW 20240710 with actually 59 Devices
btw i have started with CC2531 few Years ago - but from the beginning I kept having inexplicable problems with it
Q2: any USB Extension Cable should work (and really recommended even with CC2652x based Coordinator) - no matter if 2.0 or 3.x Cable
Thanks for your help. I will look after CC2652RB too
What happened?
Since version 1.40.2, and after few hours (maybe 6h-8h), turning on/off lights from wall switches don't work anymore.
It affects also version 1.41.0
No issue with 1.40.1 : I rollback to version 1.40.1 on which turning on/off light keep working after few hours
What did you expect to happen?
Turning on/off lights from wall switches still working after few hours or a night
How to reproduce it (minimal and precise)
This is a challenging issue to replicate due to its time-dependent nature. After a week of investigation, I managed to isolate the problem :
The issue pattern:
The debug logs provided below should help understand the problem better I think
I made clean install of home-assistant, mosquitto. Tried mixed combinations of various versions of HA, mosquito, Z2M until I found 1.40.2 was the issue.
Zigbee2MQTT version
1.40.2
Adapter firmware version
20211115
Adapter
Texas Instrument CC2531
Setup
Home-Assistant 2024.10.4, MQTT eclipse-mosquitto 2.0.20, Kubernetes 1.29.9 (k3s), RockyLinux 9.4 (Intel Core i5)
Debug log
You will see 2 debug logs streams here : v1.40.1 OK & v1.40.2 KO
Logs are focusing on a single click of
wc_wallsw
(Wallswitch) entity which must turn on thewc_spot
(Light).