thanks Bouwe, when do you expect it in core?
It should be in Core 2022.10.5. That version contains a plugwise update.
Strange, I have 2022.10.5 with the screenshots above. I can confirm it works with the latest beta.
It is in Core 2022.10.5, Iāve double-checked the backend code.
It does not show up because the integration configuration-information in .storage is not updated apparently.
A simple fix for this is to remove the Plugwise Integration, restart Core and re-add it.
tried with your steps go get the extra preset, but doesnāt work here. In what file in .storage can I find the config?
Sorry, I am not looking correctly, the Core Plugwise library is now on v0.21.4, not on v0.24.1 
The vacation preset should be back in Core 2022.11.0, in that version the Plugwise library will be upgraded to v0.25.3, which contains the vacation-preset update.
ah, thanks, Iāll wait for next release.
Iām reading into this component.
I own a stretch and some plug and want to add this.
One question i canāt figure out:
Is there a difference between using the Stretch or plugging in the USB stick ?
Does it result in a different interval, other configuration options, more stable etcā¦?
I would suggest starting with the Stretch. If not stable, you can try with the Stick directly plugged.
aware we can, and I do, set a device_class to the notification, but wouldnāt it be nice if the integration set:
binary_sensor.plugwise_notification:
device_class: problem
and it would automatically and natively use the new alerting colors from frontend 2022.12?
1 Like
I have the same issues, with a USB stick integration using plugwise betaā¦ the power usage has values. For me the consumption switches to Unknown
I hooked up my old Plugwise source to it and let it run for a long time (to extract all historic data )and reset the counters in the plugā¦ since that the integration runs seriously smoother (plug still stop responding but return the mesh now)
How do I change the USB port in the Plugwise beta integration for the Plugwise Stick on my Raspberry PI 4? It seems to have changed from USB port.
I do not want to remove the integration and re-add it as I am afraid all plugwise circles settings/dasboards will become inactive and I need to setup them again in Home Assistant.
Can you access the config/.storage directory?
If yes, you can find and edit the usb_path in the core.config_entries file.
After saving the changes make sure to restart HA.
Also, if you change the path to /dev/serial/by-id/... then your present problem should not happen again.
Thanks for the info. Added the Home Assistant Sky Connect USB stick and restarted HA. Then the errors with the Plugwise beta integration started. Hence I had the idea something changed with respect to the USB ports in HA (plugwise stick still in same physical USB port), hence interest in the file where the USB port would be listed.
It states the following:
"usb_path": "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A103J14J-if00-port0"
So fits advice you provided.
I did a reboot of HA; same errors. Then I shutdown my Raspberry Pi 4, removed the power source for few seconds and plugged in again. When HA was alive again the plugwise stick resumed working.
Strange, but problem solved.
Normally, the /dev/serial/by-id/x_y_z path should be unique. But above the port0 part shows itās not.
I vaguely remember that there is another option, something like /dev/serial/by-?/x_y_z. Do you see something similar on your system? Maybe that path is āmoreā unique?
Issue happened again. If I check the all hardware overview I see the following (no other options):
They all 3 have port0 at the end. First one is the new HA Skyconnect stick, second one the Aeotec Zwave stick and the 3rd one is the Plugwise stick.
Any idea how to solve the port issue apart from my bypass by completely disconnecting the power?
The paths of the UBS stick looks ok, including the if00-port0 part. This is the āpersistent pathā format during reboots and is generally used in HA by many other integrations including the Plugwise-Beta integration.
What is exactly the issue? Could you share some of the error messages?
You mentioned the issues started when you start using the Sky Connect stick. Be aware there might be some radio interference between the Sky Connect and the Plugwise USB-Stick as both operate in the āzigbeeā radio spectrum. I would suggest to make sure they are as far away from each other as possible.
Hi all,
How do I add new Circle plugs?
I had the opportunity to buy a bunch of Circles used for a good price. I got one circle+ and seven circles. When trying to add them to home assistant with the stick and this add-on I get the Circle+ and three circles to show up and work āout of the boxā, real nice. However, no matter what I try, the other three wonāt connect. Iāve tried to reset them already but this does not seem to make a difference. What are my options here?
I noticed that in the previous custom component by brefra there was a known issue stating:
āThis integration does not support adding (linking) or removing devices to/from the Plugwise network (yet). You still need the Plugwise Source software for that.ā
Does this mean I just got lucky with the first four circles? I would like to try to add the others through the Plugwise Source Software, but all the links for the installer I could find are dead. Also, I donāt have a license key for the stick, so that might be an issue.
If anyone knows what more I could try, would love to know, thanks!