Firmware version 0x26540900 for ConBee III
After 24 hours deConz lost the connection with the stick.
After re-flashing the previous firmware, all was good again.
Said that a stable system is going down after a new firmware.
First the light went off line and after that the power plugs.
After the reboot, the stick did not want to connect anymore.
At that moment I decided to go back to the previous version
deCONZ_ConBeeIII_0x26530900.bin.GCF 11-Jul-2024 09:58
All items connect properly and all was running well.
Maybe I will try next weekend.
I was no fun, to notice that the entire system was failing just before going to bed.
That the system is headless and located on a not really accessible location.
I took me some time to flash the old firmware. (which worked as a charm)
Maybe I just stay on the firmware, it is stable, not to many issues.
We will see, no hurry.
I had the same issue and also had to revert to older firmware. Updating to 0x26550900 that @manup suggested has been positive. Been running without issue for a few days now.
Hi, I developed this firmware, and there was a UART-TX buffer pileup at firmware0x26540900 that didn’t occur in my test setups—but users like you have experienced it.
To address this, version 0x26550900 introduces a new request-handling flow and a watchdog that detects such lockup conditions and restarts the ConBee if necessary.
The root cause of the issue relates to the migration to a new SDK, as Silicon Labs now maintains two SDKs, with the older one likely to be deprecated in the near future.
No, 2.28.1 is the latest stable release.
I am not going to work with beta versions.
The system has to be stable.
To many heating valves and other things are running on this system.
I have updated it all, at first sight all looked ok.
But later on I discovered that 4 of the 6 thermostatic control valves where changed/renamed.
(Lights, Plugs, Sensors and Switches where all OK)
Somehow the configuration was changed of these thermostatic control valves
Domoticz was not able to control them anymore.
First I had solve which valve was who. after some try and error, that was arranged.
After that that, I had to reconfigure Domoticz again.
Presently it all works and for the moment it looks stable.
The latest deConz and firmware update has cost me more time than I wanted.
This isn’t related to firmware version as it has no access to any naming/configuration of devices.
I suggest to make a own topic for the related thermostat. Here it would be needed to know the related thermostat modelId, and from which deCONZ version to which your setup was updated to dig deeper.
Yes and No, by these updates and restores things has gone wrong.
(previous firmware failed)
Data has been changed or has been lost some how.
Which has influence on the system.
I took me a good few hours to get all working again.
Does not matter anymore, there all has been solved.
Only as a user, you will get anxious to update and that should not be the case.
What I mean is the firmware can’t do that. The cause can only be at higher levels in deCONZ’s device integration either DDF or legacy code handling it. If it happened in your setup it can happen in others.
That’s why it would be good to know the thermostat modelId and from which deCONZ version to which you updated. With that we can look what was changed for respective device via git.
