Plugwise core and custom_component

Just saw this happening in dev/beta, is this supposed to be:

while regular attributes column shows fine:

What are the ā€œconditionsā€ when this is shown? Core 2022.6.0b0 with Core Plugwise, updated as in the beta0 release-log, I assume?

This one is on todays dev nightly

Iā€™m seeing the same with Core Plugwise on 2022.6.0b0. I think this is related to the new HVACMode definitions on the climate platform, nothing related to the plugwise code.

Now that Iā€™m trying Core Plugwise on 2022.6.0b0, Iā€™m seeing some other strange things.
Adding from discovery looks strange, and after adding I see 1 device - Adam and no more.
But all the climates, binary_sensors, etc. are there I think.

Ok thanks. Still, the attributes show correctly in dev tools, just like the preset_modes. Somehow the template doesnā€™t translate directly to that.
btw, I noticed Update Plugwise climate by bouwew Ā· Pull Request #72450 Ā· home-assistant/core Ā· GitHub which is related.

Incorrect, this is the PR youā€™re looking for https://github.com/home-assistant/core/pull/70729

I have only just noticed, but since my update to hass 2022.6 my switches are no longer available in home assistant. They are controllable in the plugwise interface.

I have checked the diagnostics and the devices are no longer in there. I can see the entities, but that is because they are restored. My plugwise version is 0.18.5 (core).

Any clue what could be the cause and how I can fix this? I donā€™t dare delete the integration and re-add, since Iā€™m not sure if the devices will get new IDs and destroy all my automations?

Which Plugwise integration did you use before the upgrade? Plugwise-beta or Core plugwise?

Also core, I did use the beta component before that for a while, but Iā€™m sure I already removed it before upgrading. However, it might be the cause still somehow, I canā€™t really tell.

Ok, when going from Plugwise-beta to Core Plugwise, you are going back to an older version with less features and possibly less devices. For instance, in Core Plugwise there is no configuration of the scan-interval or the refresh-interval, these were not approved.

If you really want to go back to Core Plugwise, my advice is to delete the Plugwise-beta integration, restart HA Core and then add the Core Plugwise integration.

Thanks, I just reinstalled the beta and it is working again. I guess I misunderstood from before that this functionality was now included in the core integration and I prefer to be on stable in general. Will stay on beta for now.

had forgotten about it, so finally made an issue in https://github.com/home-assistant/frontend/issues/13082

update

closed that and moved to Add support for translating attributes

Hi all,
Is it correct, that the Plugwise-beta integration still does not have the ability to register the Circle+ to the stick?
Do you know of any other way to do that besides the Plugwise Source software? Because I do not have a license code for that.
The stick wasnā€™t used in quite some time and I did a reset of the Circles I have in an attempt to get them working with my Zigbee network. Maybe the registration was lost then.
Thanks!

No there is currently no support for registering a Circle+ directly from the plugwise-beta integration yet. However, based on the collected information during the reversed engineering of the plugwise protocol, there are hints for the format of Circle+ registration request message. So it might be possible.
Unfortunately I donā€™t have much spare time to spend to figure this out right now. I want to finish a full rewrite of the backend code to improve stability and performance first. I just created a feature request for this so I wonā€™t forget.

Thanks for the quick response!
No hurry, I wrote to the Plugwise support and told them my problem and they gave me a code no questions asked.
I reset the stick and registered the Circle+ and now it seems to work.

1 Like

Iā€™m not able to pair more than 1 Circle+ to a stick. Using Plugwise Source, after factory resetting a Circle+, I can pair it to the stick. However, adding further Circle+s to that same stick does not work. Plugwise source keeps saying ā€œWaiting for modulesā€¦ā€.

Also, looking at the debug logs of the plugwise-beta integration in homeassistant (installed via HACS), I see it should allow join requests. However, I do not see any new Circle+s added when factory resetting them near either the stick or the already paired Circle+. For the already paired Circle+ I see power usage and energy consumption today, but the other entities are not available. They run firmware version 2011-06-27.

How do you add more Circle+s to the same stick?

AFAIK you canā€™t do that, and why do you want to?
The idea is to link 1 circle+ to the stick and then let all other plugs create a mesh to that ā€œcoordinatorā€/circle+.

@sjoerdos92 I agree with @JeeCee, only one Circle+ can be connected to a Stick, the rest of the devices in the network must be Circles, Stealths, etc.

Is there any way I can disable the persistent notifications on the custom component? Because of the temperatures my floor heating pump has been off for months. Every day I get a notification that the pump has been enabled shortly to prevent clogs and rust forming. Because of this I have a persistent notification every day that isnā€™t really an error, but just infoā€¦

Switch to Core Plugwise, the persistent notifications do not exist in that version.
Core Plugwise is still behind Plugwise-beta but not as far as it used to be. I think it should work for you.