[BUG]: Zigbee devices other than Aqara Smart Plug are not recognized

[bouwew]

Describe the bug.

As reported on Tweakers, https://gathering.tweakers.net/forum/list_message/80723140#80723140, a zigbee device connected to the Adam is not shown in HA.

What version of Plugwise Beta are you using?

Core Plugwise

What was the last working version of Plugwise Beta (or Core if not using beta before)?

None

What version of Home Assistant Core are you using?

core-2024.11.0

What type of installation are you running?

Home Assistant Supervised

How did you install plugwise-beta?

HACS

What kind of Plugwise device is having issues?

Smile: Adam (including Lisa, Tom, Floor)

What firmware version is your Plugwise product at?

3.7.8

Logging

No response

Diagnostics information

No response

Additional information

No response

[VraagSander]

Hi, willing to help test. Let me know what to do!

[bouwew]

OK very good. Do you have HACS installed?

[VraagSander]

Yes! Verstuurd vanaf mijn iPhone Op 24 nov 2024 om 07:37 heeft Bouwe Westerdijk ***@***.***> het volgende geschreven:  OK very good. Do you have HACS installed? — Reply to this email directly, view it on GitHub<#768 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIHFUE7OSBT7RN53GTK6H6L2CFXYZAVCNFSM6AAAAABR4XKNH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHAZTSMRWHA>. You are receiving this because you commented.Message ID: ***@***.***>

[bouwew]

OK clear.

The procedure then is:

• Delete the Plugwise integration from HA.
• Add the plugwise-beta repo in HACS, the repo is here: https://github.com/plugwise/plugwise-beta
• When added to HACS search for plugwise beta and click on it, the detailed repo info should appear. If not, restart HA and repeat searching for plugwise beta.
• Press the 3 vertical dots in the top right corner
• Press Redownload and select version v0.55.0a1, wait for the download to finish
• Restart HA
• Go to Settings --> Devices & Services, your Adam should be shown as discovered, shown as a button.
• Press that button, it will now use the Plugwise beta code to add the integration
• Enter the Smile ID of your Adam and press the ADD button(?)
• Next, look at the devices under the Adam, you should see several more representing your heating-zones.

Now, please test changing the temperature, preset, turn schedule to auto or heating, change to a different schedule.
Any issue, let me know :)

[VraagSander]

Hi Bouwe,

I did some preliminary testing, and the first results are good.

• Temps & setpoints match
• changing setpoints propagate properly both ways
• changing schedules works as expected.
• turing it off turns off the entire regulation by adam. I didn't even know I could do that, but it works nicely.

Finding 1:

• Turning a zone thermostat to 'on' has no effect in Plugwise. I'd say this is desired behaviour as heating demand is linked to the controlling of valves, which is linked to zones requiring heating. Allowing the system to heat with al valves closed (or last ones open) would yield unpredictable heating results .

Finding 2:

• I noticed that one of the zones unexpectedly showed as if it was heating in Homeassistant. (it didn't show as heating in the plugwise interface)
  o ‘Badkamer’ had a setpoint of 14.9 and a thermostat reading of 18.4
• I checked the locations XML and noticed the <control_state> node was missing entirely?!
• After increasing the setpoint beyond the thermostat the node showed up with ‘heating’
• After decreasing the setpoint the node changed to ‘off’

Haven’t had time to (, and wouldn’t know how to) reproduce the node to go missing in the plugwise data again. Perhaps it had to do with an adam reset…

[bouwew]

@VraagSander OK thanks for your feedback.
First, a question: which version are you running? The a1-version? If yes, please upgrade to v0.55.0 the latest released version. This version contains a few final improvements.

[bouwew]

About your finding 2, I've seen similar thing happen a few times before.
Forcing it to an active mode solved it in earlier cases as well. The problem never appeared after that, as far as I know :)

[bouwew]

Also FYI, the updates that are in pw-beta v0.55.0 also have been added to HA Core today.
I expect them to be released in HA 2024.12.0.

[VraagSander]

@VraagSander OK thanks for your feedback. First, a question: which version are you running? The a1-version? If yes, please upgrade to v0.55.0 the latest released version. This version contains a few final improvements.

Yes I was still running the a1 version. Upgraded today :) all still works well ;)

About your finding 2, I've seen similar thing happen a few times before. Forcing it to an active mode solved it in earlier cases as well. The problem never appeared after that, as far as I know :)

Found the cause and was able to reproduce. Switching the regulation to 'Off' deletes all control-state nodes

Also FYI, the updates that are in pw-beta v0.55.0 also have been added to HA Core today. I expect them to be released in HA 2024.12.0.

That's awesome! good work !!! 🥇