[ENHANCEMENT] Expose Circle marked as "Don't turn off" parameter

[CoHoAppel]

After migrating an existing Stick/Windows PC installation with 7 Circles, by moving the Stick to a HA on RaspberryPi, only the Circles without a marking "Don't turnoff" for manual switching show up with their entities in HA. The Plugs that were marked do not show up at all. HA en Plugwise-beta are at the latest version

[CoHoAppel]

After the HA update 2021.2.1 finished (installed it 1 hour ago) the remaining 4 Circles started popping up one by one in de devices list along with their entities. No explanation, but that did complete the installation. What remains is an option to disable these switches in order to avoid misuse. Comparable to the function in the Plugwise app. Is this hidden somewhere already, or should I enter it as a new feature request?

[brefra]

Nice to read the discovery is working now. It might be due to moving the stick triggered rebuilding the network between the plugwise devices, which could take a few hours to settle down.
To disable the relay (entity) option, just switch off the "Enable entity" at the relay. It's a native build-in feature of HA.

[CoHoAppel]

Works well, thanks. Before going ahead with other integrations I'm considering a fresh restart of HA but this time the 64-bit version (running 32-bit now). Are there any limitations with the Plugwise-beta in that case and, as I'm still new to HA, would it be wise to do this. Would assume that the future is 64-bit anyhow. From: brefra <notifications@github.com> Sent: Saturday, February 6, 2021 2:20 PM To: plugwise/plugwise-beta <plugwise-beta@noreply.github.com> Cc: CoHoAppel <cor_hopman@hotmail.com>; Author <author@noreply.github.com> Subject: Re: [plugwise/plugwise-beta] Circles marked as "Don't turn off" not recognized during integration [BUG] (#150) Nice to read the discovery is working now. It might be due to moving the stick triggered rebuilding the network between the plugwise devices, which could take a few hours to settle down. To disable the relay (entity) option, just switch off the "Enable entity" at the relay. It's a native build-in feature of HA. [image]<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F6314181%2F107119036-3f7c9380-6885-11eb-99ae-dd8e4ca1a11b.png&data=04%7C01%7C%7C30f6859bba924f277e0d08d8caa1d75a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637482143742920126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ahJW4NqypXTNfFzkL%2FBYnAu0W7lxd7Op2AtT7CUNlsc%3D&reserved=0> - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fplugwise%2Fplugwise-beta%2Fissues%2F150%23issuecomment-774476493&data=04%7C01%7C%7C30f6859bba924f277e0d08d8caa1d75a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637482143742930083%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JX%2Bf6UdhnFUsPWfC7qgFRCqU75t6rmemaQ2TX6ZOlpI%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fnotifications%2Funsubscribe-auth%2FAO4SJBETLGJ3Y2BHCSJH57LS5U6WJANCNFSM4XEYX7CA&data=04%7C01%7C%7C30f6859bba924f277e0d08d8caa1d75a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637482143742930083%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Rci9GFv8fydeXMejgl4trIfhvlmHNTbsAQYHiDSZ9aQ%3D&reserved=0>.

[bouwew]

Regarding this topic, in the XML-data from the Stretches and from the Adam I can see this:

<lock>false</lock>
<state>on</state>

I'm planning to add a lock-switch to each Circle/Plug relay switch. But this will only work via the Stretch and the Adam.

@brefra I would assume that the Circles, etc. also provide their lock-state, next to the relay-state?

[dirixmjm]

@CoMPaTech @bouwew we should relabel this as feature request.
In my opinion, considering HAS has this functionality build-in, there is not much incentive for pursuing this.

[CoMPaTech]

@CoMPaTech @bouwew we should relabel this as feature request. In my opinion, considering HAS has this functionality build-in, there is not much incentive for pursuing this.

Might be a good one to test also, I think when you accept the invite @dirixmjm you'll be able to modify it yourself (both the title and the labels).