Eurotronic Spirit ZigBee (SPZB0001) temperature not updated in device since deCONZ 2.12.6

[bcutter]

Describe the bug

Temperature set in Home Assistant is never being sent/transferred to the device. Local changes are sent back to Home Assistant. As deCONZ sits in between and there were no firmware updates, we believe this issue has been introduced with v2.12.6 (where v2.11.5 is very likely to not have this issue according to another user report (see links below) - full disclosure: I can guarantee the issue didn´t exist with addon v6.8.0/deCONZ v2.10.4).

Steps to reproduce the behavior

1. Set new temperature remotely
2. Wait forever for the device to update

Expected behavior

1. Set new temperature remotely
2. Device target temperature is being updated within max. 20 seconds

Environment

HA 2021.10.6
Latest (only available) SPZB0001 firmware

• Host system: Raspberry Pi
• Running method: Home Assistent deCONZ Add-on (v6.10)
• Firmware version: (26660700)
• deCONZ version: (2.12.6)
• Device: ConBee II
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? If so: Which? /

Screenshots

Additional context

• See detailed symptoms described here @ Ongoing Issues with SPZB0001 / Eurotronic Spirit Zigbee EUROTRONIC-Technology/Spirit-ZigBee#1 (comment)
• See another user @double1968 with similar setup and same issue here @ Ongoing Issues with SPZB0001 / Eurotronic Spirit Zigbee EUROTRONIC-Technology/Spirit-ZigBee#1 (comment)
• See issue raised within HA repo (which is not the right place I think) here @ Deconz - HA thermostat slider does not update the temperature on Eurotronic Spirit ZigBee home-assistant/addons#2244

[close-issue-app]

Hi there.

Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed.
We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format.

In this regard, please take note that:
- read the template thoroughly
- all given header lines (starting with ###) must not be deleted
- everything enclosed by <!-- --> is intended to give you guidance and should be replaced by your input specific to the issue
- Listings regarding your environment must be filled out completely where applicable (bug reports and user questions).
- Not following the template or providing insufficient information can still implicate manual closure.
- Anything that is not clearly a bug can still implicate manual closure. For support we recommend the forum: https://forum.phoscon.de

So please, first help us a bit to help you!

[bcutter]

What the heck? What´s missing in my issue description?

I invested a lot of time and stick thoroughly to the template - what´s missing?!?

[double1968]

I don't understand what's wrong with this issue!
The proposed template has been respected.

[Mimiix]

I would have closed it either way. The firmware is the big issue here as it's buggy. Its so buggy we can't even fix it.

[bcutter]

I would have closed it either way. The firmware is the big issue here as it's buggy. Its so buggy we can't even fix it.

The firmware hasn't changed. My TRVs worked perfectly until ~ April. Now the only thing changed meanwhile is HA and deCONZ version.

And it seems like double1968 can reproduce the issue in terms of: downgrading to a former deCONZ version resolves the issue.

[Mimiix]

I'm on PC now, so i can answer a bit better.

I don't understand what's wrong with this issue! The proposed template has been respected.

I do. The reason the bot closed the issue is because the Screenshots header was removed from the template. Adding it later on doesn't help. In short: the template wasn't respected fully.

The firmware hasn't changed. My TRVs worked perfectly until ~ April. Now the only thing changed meanwhile is HA and deCONZ version.

And it seems like double1968 can reproduce the issue in terms of: downgrading to a former deCONZ version resolves the issue.

Please make sure that bug reports comply with #5113 . That means that the reports should give pointers to the code (for example mentioning it works in 2.1.x and not in 2.2.x). If you can't, we are happy to help on the forums.

@double1968 I suggest you open a proper bug report with the testing you did and steps to reproduce (adding what version works and what version doesn't).