Plugwise USB/Stick beta

Configuration
81

@bouwew Finally time to get the usb stick working on a raspberry pi via ser2net.
So far, so good but how do i change the current path in de working integration without losing entititie id’s in HA? I’ve got 30+ circles working and would really hate it to change all automations.
Is there a solution to simply change the path of the stick without redoing everything?

82

No, at the moment there isn’t. As far as I know.

That would require a reconfiguration function, please create a Feature Request in the plugwise_usb-beta github.

83

Damn…
I will create a feature request for this.
Would there be an off-the-record way to change the path? For instance by editing a config file manually?

84

I’ve started adding a reconfigure function, will take a few more days to finish and test. Will let you know when you can try the function :slightly_smiling_face:

85

Oh, wauw. That would really save the day!
Somehow I cannot find the right feature request location, men can’t search :rofl:

86

@edwin-2023 Please update to v0.59.0b0 and test :slight_smile:

image
image1174×617 53.3 KB

87

Great, and very fast. Need to get some work done but will let you know!

88

When selecting Reconfigure you will see this window pop up:

image
image389×271 8.08 KB

You can then manually update the path-string that has been configured in the past.

89

My plan is to connect the stick via ser2net on a raspberry pi so i guess the path will be: 192.168.2.2:20108 where the ip adres is the pi with the ser2net port number.

Ser2net yaml;
connection: &plugwise_conn
accepter: tcp,20108
enable: on
options:
kickolduser: true
connector: serialdev,
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A4003x3U-if00-port0,
115200n81

90

Sorry, can’t help you here, I have no experience with this. You will just need to try :slight_smile:

91

You could try socket://ip:port or tcp://ip:port.

92

Thnx, not at home until tomorrow. Will try and let you know the result. Raspberry pi 3b+ with 2.5A psu is running zigbee2mqtt and zwave2mqtt each in its own docker-compose container. Ser2net is running straight on os.
This way the proxmox server with haos is running in the concreet basement ans the pi on the first floor to get a decent coverage start.
Plugwise is now the only thing plugged in the server and running via a (to long) usb cable.

93

OK no problem :slight_smile:
The Integration code will validate the new device-path/url that you enter.
If no connection to the Stick is detected the code will throw an error and you should be able to re-enter a different device-path/url.
Only when the Stick is detected then the configuration will be updated and saved.
I don’t know if the Integration then will reload. If is doesn’t you can reload manually.
Good luck!

94

It works, and still lighting fast !!
Clicked on reconfigure and filled in: socket://ip_pi:port_ser2net. The integration automatically does a reload and all existing circles reappear and are also controllable.
SUPER SOLUTION"

95

While i’m on it i’m trying to automate circle reset and join procedure so i can easily add circle’s. In HA i made an autmation that;

  • switches off a z-wave switch for 30 seconds
  • do the procedure
  • switch circle on again to join.

Somewhere i’m screwing up since nothing happens, does someone see my mistake?

YAML of the automation;
f50a9842b967c427597de49f9d2fac6f = z-wave switch
9f508f465aa1da9c03af62357d41118c = Circle+
1298101b15524ff80ce141f3fc01900f = Autojoin button C+

alias: Plugwise Circle v1 Resetvolgorde
description: Voert volledige fabrieksreset uit met vooraf 30s uitgeschakeld
triggers: []
conditions: []
actions:
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_off
    data: {}
  - delay:
      seconds: 30
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_on
    data: {}
  - delay:
      seconds: 3
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_off
    data: {}
  - delay:
      seconds: 3
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_on
    data: {}
  - delay:
      seconds: 3
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_off
    data: {}
  - delay:
      seconds: 3
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_on
    data: {}
  - delay:
      seconds: 8
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_off
    data: {}
  - delay:
      seconds: 8
  - device_id: 9f508f465aa1da9c03af62357d41118c
    domain: button
    entity_id: 1298101b15524ff80ce141f3fc01900f
    type: press
    enabled: true
  - delay:
      seconds: 8
  - target:
      device_id: f50a9842b967c427597de49f9d2fac6f
    action: switch.turn_on
    data: {}
mode: single
96

Nice! I’ll formally release this feature update in v0.59.0 :slight_smile:

97

The sequence should be 3 seconds on, 3 seconds off, 3 seconds on, 3 seconds off, 8 seconds on, 3 seconds off, then on.

98

I think I started with that. Will try later this week and let you now. No entirely sure if the join click works via automation, on the other hand I did not get a reset confirmation from the circle :roll_eyes: