New Danfoss 1.32 OTA causes issues on Popp hardware

[sopelt]

Hi @AresMaster , hi @Koenkk ,

I have several Popp TRVs which are a variation of this device/Danfoss Ally. The 1.32 OTA which was added for Danfoss was also offered as an update for the Popp devices.

After the update the valve motor is moved every 1-2 minutes (only very shorty - more like a click) which is annoying and probably a battery killer. Do the Danfoss Ally devices work as expected with this update? I tried downgrading but it seems to be rejected by the device and I get INVALID_IMAGE. I tried all variations of settings and also removed some of the reporting intervals.

As a last resort I removed a TRV from the network, factory reset it and just let it run standalone (without joining any zigbee network) and it still moves the motor every minute which looks like a clear indicator that the firmware introduced this behavior as the devices worked as expected the last two heating seasons.

I would try to avoid offering the OTA to Popp devices until there is more feedback/clarity if this is a general problem for that combination or if it is more complex.

I would appreciate any input on how to further diagnose/resolve this issue.

Thanks for all your work!

[pitat1]

@sopelt Did the issue resolve itself? On Danfoss Ally 1.32 OTA image files #822 there was suggestion that this is caused by PID reset. Do you confirm that?

[sopelt]

Hi @pitat1 .. sorry for not updating this issue yet with more documentation. My status right now is that both Danfoss and Popp TRVs on the current firmware click every 1-2 minutes (unless the valve is 0% or 100%) most of the day. I tried factory resetting, adaptation run, different settings for algorithm, covered, pushing external temperature but nothing really helps. The last two heating seasons we haven't noticed noise anything close to what is happening right now. I am still trying to figure out if there is anything to do besides installing "dumb-TRVs" in rooms where the constant clicking disturbs sleeping.
When setting the reporting thresholds for piHeatingDemand to 60s/3600s/1% one can see that it is every 1-2 minutes and that there is lots of moving back and forth by +/- 1-10% . This can't be good for the motor, battery and noise emissions... Even on TRVs that ran undisturbed for 6+ weeks nothing improved and they are still clicking away ... and ... just to be safe I tried an official danfoss hub + thermometer + TRV ... and even though I can't get detailed data out of it at the first glance it looks like there is lots of micro-adjustments as well. My best guess is that the current firmware is not "great" at least in combination with certain heating scenarios (high flow temperature? local temperature fluctuations?). When not pushing external temperature regularly the distance the valve moves back and forth is even worse. I am not sure what exactly the TRV stores for the valve adaptation run but if it is something like a mapping matrix created from local temperature it might just be terribly noisy and cause stuff like this...

What behavior are you seeing?

[pitat1]

I didn't updated my Popp devices yet ( I am still on 00.28.0008 00.28 ). Can you copy the state josn of your devices? Just to check the config.

I was thinking of update before starting playing with schedule setup, based on this thread: Koenkk/zigbee2mqtt#14352