Eurotronic Spirit devices overload logs after update to deCONZ version 2.32.5

deCONZ Setup Support
1

Hi everybody!
When I update my deCONZ service to v.2.32.5 my Eurotronic Spirit Zigbee devices report their LastUpdated state 3 times every few seconds resulting in overloading the Openhabian logs with that information (and probably wasting battery power).

I’m using openHAB 5.1.3 on a Raspberry Pi with my deCONZ gateway running on a second pi using a 32bit Openhabian image and a RaspBee II Zigbee-Gateway.

I tried this update now 2 times having the same result and rolled back to my latest backup. After rollback the reporting interval is back to normal.

Does anybody else have similar effects?
Maybe I’m missing some important update information, or might this be a bug in the latest Eurotronic device support changes?

I think I found a reference to similar behaviour in this PR: DDF for Eurotronic Spirit radiator thermostat (SPZB0001) by mattreim · Pull Request #8361 · dresden-elektronik/deconz-rest-plugin · GitHub .
But as it was merged into the new version, I think it was tested as working correctly.

Any help or information would be highly appreciated!

2

The error has been fixed with this PR and you can use the new DDF as a temporary solution.

3

Needed some minutes to figure out how to bring this DDF in action, but it looks like it does the trick :+1:

Thank you very much for the fast support @mattreim !

4

Since updating deCONZ from v2.31.2 to v2.32.5 on 2026-05-08 (via HA deCONZ addon update v8.5.2 to v8.7.0), I see two issues for the SPZB0001:

  1. Constant device updates according to Phoscon, literally every second (probably multiple times) as reported in this thread
    grafik
    grafik631×484 23.2 KB

This squeezed the batteries quite a lot in those few days (not even a week), now they’re almost empty at 5 % for one device.

2) Complete loss of connection which sometimes returns after a few hours, sometimes never comes back - so the very opposite of issue #1

grafik
grafik635×460 17.5 KB

I’ll give the custom DDF a try now. Wondering
a) if it would fix issue #2 too (could not find any existing issue on this) and
b) how I would discover when a new stable release gets available containing this fix so I get a trigger to remove the custom DDF, assuming it’s better to not run the custom/temporarily activated DDF forever.

5

Update 1: DDF loaded (NOT working via the device integration tab in Phoscon as it does not allow .json files by the way so I had to go the long way).

  • :red_question_mark:Issue #2 needs to be monitored for next few hours and days.
  • :warning: Issue #1 seems to be fixed for device 1, but not for device 2
    grafik
    grafik627×285 11.1 KB

    (device 1 looking good / better)
    grafik
    grafik635×294 11.7 KB

    (device 2 still constantly updating every second)

I checked in deCONZ both devices are using the updated DDF. Something’s still broken…

Thanks for so much trouble with devices working flawlessly for years. Every deCONZ update is a surprise… oh dear I hate that waste of time :smile:

Update 2: After removing device 2’s batteries for a 2nd time and reloading Phoscon page, it seems to work properly for device 2 regarding issue 1.

grafik
grafik644×301 11.8 KB

Now monitoring the connection loss issue.

6

I just copied the json file into the folder /usr/share/deCONZ/devices/eurotronic and restarted deconz.
Since then, everything is running stable, also connection losses are gone and battery drain recovered.
Using this for 12 Eurotronic Spirit devices since a month now.