Mismatch in climatecontrol thermostat with plugwise app when using two tom/floors in a zone

[VraagSander]

The problem

I have a setup where two tom/floors are grouped in a zone. The plugwise app uses the first tom/floor in the zone as the 'thermostat' The homeassistant integration only creates a climate control bound to the last tom/floor in the group.

This creates a mismatch between the temperature readout and because of that issues with controlling the zone using the provided climate thermostat control.

What version of Home Assistant Core has the issue?

core-2024.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Plugwise

Link to integration documentation on our website

https://www.home-assistant.io/integrations/plugwise

Diagnostics information

config_entry-plugwise-01JCBJ4S2MX47CAR9DRWVC4W05.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I've tried moving tom 9400 and reloading which gets me the climate control for tom 4D. However after adding 9400 the climate control for 4D is no longer provided. I've tried adding the toms in a different sequence to the plugwise app, but this did't affect which one was offered as climate control. I've tried renaming toms in the plugwise interface, but this didn't affect which one was created as climate control.

[home-assistant[bot]]

Hey there @compatech, @bouwew, @frenck, mind taking a look at this issue as it has been labeled with an integration (plugwise) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `plugwise` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign plugwise` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

plugwise documentation plugwise source _{^{(message by IssueLinks)}}

[bouwew]

@VraagSander From what the picture shows I would guess that the Plugwise App shows the thermostat that reports the lowest temperature in the Badkamer. I'm wondering, what happens when you change the setpoint of the other Tom to 20? Will it then change the setpoint to 20 in the thermostat shown in the App?

[VraagSander]

@bouwew The setpoints of both toms are linked. If I update the thermostat of the zone via the app, both setpoints are adjusted. I can only adjust the setpoint of one of the toms, changing it is picked up by the plugwise app and then synced to the other toms.

[bouwew]

Ok thanks for trying this. I can see what happens.

The quickest way forward in fixing this would be for you to capture some data from your Adam and sharing this data with me. Based on this data I should be able to find out how to fix this issue.

Please browse to your Adam via the "Visit"-link in HA, enter login (smile) and passwd (Smile ID) and browse to the following path: http:///core/domain_objects. You should see a page with lots of xml data. Right-click anywhere on this page and select Save as ... (xml) into a file on your computer. Please send this file with xml-data to bouwe at westerdijk point info (please change to a real email address :) )

[bouwew]

Also, when you change something in your system, it should be picked up automatically by the Plugwise integration. The thing is, when you change the name, the entity-name in HA will change too. So a name-change is not picked up.

The best way to fix this is to delete the Plugwise integration, wait for the Adam to be discovered, and add it again. If the Adam is not discovered in a few minutes, try restarting HA.

[VraagSander]

I've share the requested document by mail.

(If i update a name in the plugwise app reloading the integration is sufficient to have the namechange reflected in the devices.)

Different case same problem:

The plugwise integration uses the first lisa in the zone as 'primary' thermostat The homeassistant integration in this case gives preference to the last thermostat in the zone (an anna in this case)

[VraagSander]

I stand corrected. According to plugwise's documentation it is indeed either the lowest measured temperature from all thermostats in a zone, or the lowest measuring tom (if only toms are in a zone).

https://plugwisehelp.freshdesk.com/en/support/solutions/articles/44002158527-what-measured-temperature-does-adam-use-

[bouwew]

OK, that's clear too, and thanks for the link!

An interesting use-case you are having at home :) This is the first time that such a use-case comes up.

In the past we did notice the difference between a Tom used together with a Lisa or a standalone Tom. But we had not encountered the scenario you have at home. It will be interesting to see your Adam's xml-data, I'm hoping that it is somehow visible what the roles are of each device.

[VraagSander]

Hi Bouwe, sorry for supplying the wrong file at first. I've now sent my domain.xml. I hope it is useful.

I also included my locations.xml file from /core/locations .

Each location node there has a logs node holding the latest recorded thermostat setpoint and temperature measurement of the particular location. There is also an actuator node included that correctly matches the termostat's state as reflected in the plugwise dashboard (heating, off, cooling) I tested them working by changing the setpoint and heating a node.

Perhaps it can serve as a good source for the locations thermostats.

[bouwew]

@VraagSander Thanks for sending the xml-data!

Yes, I've come to the same conclusion after studying the problem. Us integration-owners were thinking too much device-related because we didn't know better, we only have a single primary thermostat in our homes. But with the info you have provided it became clear that the Plugwise climate entities correspond to a zone/location. Working on a solution...

[bouwew]

@VraagSander I have a solution working in the custom_component Plugwise-beta. If you willing to help test, please let me know at https://github.com/plugwise/plugwise-beta/pull/770