Release pimatic-raspbee@0.1.6

---

OK great, here we go
Steering the switch from the gui exactly works as foreseen => no need for adjustments.
What is other, is the behaviour from the device’s side, so how the gui behaves, when it is steered by the device’s buttons.

Moving up and down does not directly trigger the countdown in the gui. The counting and adjustment is triggered after the devices toggels itself back into ‘neutral/stop’. When moving completely up or down, that wouldn’t be a drama, as normaly I guess no one would jump that fast from the shutter location to whatever steering gui, but:
The problem occures, when the switch/shutter is steered to whatever ‘in-between’ status only and stopped there by it’s ‘stop-button’. In this case the gui isn’t adjusted at all to the correct position.
As example: When pressing ‘close’ at the switch , waiting 3 seconds and then pressing ‘stop’ the gui doensn’t change to whatever 20-30%, as it normally should be then. The adjustment of the gui by the switch at least only works, when the switch toggels itself back to ‘neutral/stop’, when it reaches an end-position 'full open or close’
I will sent in here directly some log, to see the bahaviour …

here an example when I pressed ‘open’ and let it run until the switch toggels itself back and the gui reacted afterwards:

0:36:47.231 [pimatic-raspbee] debug: new message received
20:36:47.232 [pimatic-raspbee] debug: {
20:36:47.232 [pimatic-raspbee] debug:>  e: 'changed',
20:36:47.232 [pimatic-raspbee] debug:>  id: '6',
20:36:47.232 [pimatic-raspbee] debug:>  r: 'lights',
20:36:47.232 [pimatic-raspbee] debug:>  state: { bri: 254, lift: 100, on: true, open: false, reachable: true },
20:36:47.232 [pimatic-raspbee] debug:>  t: 'event',
20:36:47.232 [pimatic-raspbee] debug:>  uniqueid: '80:4b:50:ff:fe:2b:f5:c2-01'
20:36:47.232 [pimatic-raspbee] debug:>}
20:36:47.233 [pimatic-raspbee] debug: Received values: {
20:36:47.233 [pimatic-raspbee] debug:>  "id": 6,
20:36:47.233 [pimatic-raspbee] debug:>  "type": "event",
20:36:47.233 [pimatic-raspbee] debug:>  "event": "changed",
20:36:47.233 [pimatic-raspbee] debug:>  "resource": "lights",
20:36:47.233 [pimatic-raspbee] debug:>  "state": {
20:36:47.233 [pimatic-raspbee] debug:>    "bri": 254,
20:36:47.233 [pimatic-raspbee] debug:>    "lift": 100,
20:36:47.233 [pimatic-raspbee] debug:>    "on": true,
20:36:47.233 [pimatic-raspbee] debug:>    "open": false,
20:36:47.233 [pimatic-raspbee] debug:>    "reachable": true
20:36:47.233 [pimatic-raspbee] debug:>  },
20:36:47.233 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:36:47.233 [pimatic-raspbee] debug:>}
20:36:47.234 [pimatic-raspbee] debug: moveTo: 100, target: 0, _transitSeconds: 10, _positionStep: -10
20:36:47.234 [pimatic-raspbee] debug: Received values: {
20:36:47.234 [pimatic-raspbee] debug:>  "id": 6,
20:36:47.234 [pimatic-raspbee] debug:>  "type": "event",
20:36:47.234 [pimatic-raspbee] debug:>  "event": "changed",
20:36:47.234 [pimatic-raspbee] debug:>  "resource": "lights",
20:36:47.234 [pimatic-raspbee] debug:>  "state": {
20:36:47.234 [pimatic-raspbee] debug:>    "bri": 254,
20:36:47.234 [pimatic-raspbee] debug:>    "lift": 100,
20:36:47.234 [pimatic-raspbee] debug:>    "on": true,
20:36:47.234 [pimatic-raspbee] debug:>    "open": false,
20:36:47.234 [pimatic-raspbee] debug:>    "reachable": true
20:36:47.234 [pimatic-raspbee] debug:>  },
20:36:47.234 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:36:47.234 [pimatic-raspbee] debug:>}
20:36:47.235 [pimatic-raspbee] debug: moveTo: 0, target: 100, _transitSeconds: 10, _positionStep: 10
20:36:47.237 [pimatic-raspbee] debug: updatePosition: 90
20:36:47.239 [pimatic-raspbee] debug: updatePosition: 10
20:36:47.281 [pimatic-raspbee] debug: new message received
20:36:47.283 [pimatic-raspbee] debug: {
20:36:47.283 [pimatic-raspbee] debug:>  e: 'changed',
20:36:47.283 [pimatic-raspbee] debug:>  id: '65520',
20:36:47.283 [pimatic-raspbee] debug:>  r: 'groups',
20:36:47.283 [pimatic-raspbee] debug:>  state: { all_on: false, any_on: true },
20:36:47.283 [pimatic-raspbee] debug:>  t: 'event'
20:36:47.283 [pimatic-raspbee] debug:>}
20:36:47.284 [pimatic-raspbee] debug: new message received
20:36:47.285 [pimatic-raspbee] debug: {
20:36:47.285 [pimatic-raspbee] debug:>  e: 'changed',
20:36:47.285 [pimatic-raspbee] debug:>  id: '1',
20:36:47.285 [pimatic-raspbee] debug:>  r: 'groups',
20:36:47.285 [pimatic-raspbee] debug:>  state: { all_on: false, any_on: true },
20:36:47.285 [pimatic-raspbee] debug:>  t: 'event'
20:36:47.285 [pimatic-raspbee] debug:>}
20:36:48.239 [pimatic-raspbee] debug: updatePosition: 80
20:36:48.241 [pimatic-raspbee] debug: updatePosition: 20
20:36:49.243 [pimatic-raspbee] debug: updatePosition: 70
20:36:49.246 [pimatic-raspbee] debug: updatePosition: 30
20:36:50.247 [pimatic-raspbee] debug: updatePosition: 60
20:36:50.250 [pimatic-raspbee] debug: updatePosition: 40
20:36:51.251 [pimatic-raspbee] debug: updatePosition: 50
20:36:51.257 [pimatic-raspbee] debug: updatePosition: 50
20:36:52.256 [pimatic-raspbee] debug: updatePosition: 40
20:36:52.259 [pimatic-raspbee] debug: updatePosition: 60
20:36:53.258 [pimatic-raspbee] debug: updatePosition: 30
20:36:53.260 [pimatic-raspbee] debug: updatePosition: 70
20:36:54.261 [pimatic-raspbee] debug: updatePosition: 20
20:36:54.263 [pimatic-raspbee] debug: updatePosition: 80
20:36:54.469 [pimatic-raspbee] debug: new message received
20:36:54.470 [pimatic-raspbee] debug: {
20:36:54.470 [pimatic-raspbee] debug:>  e: 'changed',
20:36:54.470 [pimatic-raspbee] debug:>  id: '3',
20:36:54.470 [pimatic-raspbee] debug:>  r: 'sensors',
20:36:54.470 [pimatic-raspbee] debug:>  state: {
20:36:54.470 [pimatic-raspbee] debug:>    current: 0,
20:36:54.470 [pimatic-raspbee] debug:>    lastupdated: '2021-03-12T19:36:54.467',
20:36:54.470 [pimatic-raspbee] debug:>    power: 0,
20:36:54.470 [pimatic-raspbee] debug:>    voltage: 226
20:36:54.470 [pimatic-raspbee] debug:>  },
20:36:54.470 [pimatic-raspbee] debug:>  t: 'event',
20:36:54.470 [pimatic-raspbee] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04'
20:36:54.470 [pimatic-raspbee] debug:>}
20:36:55.263 [pimatic-raspbee] debug: updatePosition: 10
20:36:55.266 [pimatic-raspbee] debug: updatePosition: 90
20:36:56.267 [pimatic-raspbee] debug: updatePosition: 0
20:36:56.270 [pimatic-raspbee] debug: updatePosition: 100

I guess in the end there is something in (ID: 3) comming from the Blitz plug

and here an example where, starting from ‘closed’, I pressed ‘open’ waited ~3 sec., pressed ‘stop’, waited again, then pressed again ‘open’, waited again and then ‘stopped’ again. I directly filtered out the other IDs and put in, where I assume that this was toggled by me on the switch, regarding ‘STOP’ I’m not quiet sure:

=> OPEN
20:43:01.192 [pimatic-raspbee] debug: new message received
20:43:01.193 [pimatic-raspbee] debug: {
20:43:01.193 [pimatic-raspbee] debug:>  e: 'changed',
20:43:01.193 [pimatic-raspbee] debug:>  id: '6',
20:43:01.193 [pimatic-raspbee] debug:>  r: 'lights',
20:43:01.193 [pimatic-raspbee] debug:>  state: { bri: 127, lift: 50, on: true, open: true, reachable: true },
20:43:01.193 [pimatic-raspbee] debug:>  t: 'event',
20:43:01.193 [pimatic-raspbee] debug:>  uniqueid: '80:4b:50:ff:fe:2b:f5:c2-01'
20:43:01.193 [pimatic-raspbee] debug:>}
20:43:01.194 [pimatic-raspbee] debug: Received values: {
20:43:01.194 [pimatic-raspbee] debug:>  "id": 6,
20:43:01.194 [pimatic-raspbee] debug:>  "type": "event",
20:43:01.194 [pimatic-raspbee] debug:>  "event": "changed",
20:43:01.194 [pimatic-raspbee] debug:>  "resource": "lights",
20:43:01.194 [pimatic-raspbee] debug:>  "state": {
20:43:01.194 [pimatic-raspbee] debug:>    "bri": 127,
20:43:01.194 [pimatic-raspbee] debug:>    "lift": 50,
20:43:01.194 [pimatic-raspbee] debug:>    "on": true,
20:43:01.194 [pimatic-raspbee] debug:>    "open": true,
20:43:01.194 [pimatic-raspbee] debug:>    "reachable": true
20:43:01.194 [pimatic-raspbee] debug:>  },
20:43:01.194 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:43:01.194 [pimatic-raspbee] debug:>}
=>STOP(?)
20:43:01.194 [pimatic-raspbee] debug: Received values: {
20:43:01.194 [pimatic-raspbee] debug:>  "id": 6,
20:43:01.194 [pimatic-raspbee] debug:>  "type": "event",
20:43:01.194 [pimatic-raspbee] debug:>  "event": "changed",
20:43:01.194 [pimatic-raspbee] debug:>  "resource": "lights",
20:43:01.194 [pimatic-raspbee] debug:>  "state": {
20:43:01.194 [pimatic-raspbee] debug:>    "bri": 127,
20:43:01.194 [pimatic-raspbee] debug:>    "lift": 50,
20:43:01.194 [pimatic-raspbee] debug:>    "on": true,
20:43:01.194 [pimatic-raspbee] debug:>    "open": true,
20:43:01.194 [pimatic-raspbee] debug:>    "reachable": true
20:43:01.194 [pimatic-raspbee] debug:>  },
20:43:01.194 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:43:01.194 [pimatic-raspbee] debug:>}
=>OPEN
20:43:09.009 [pimatic-raspbee] debug: new message received
20:43:09.010 [pimatic-raspbee] debug: {
20:43:09.010 [pimatic-raspbee] debug:>  e: 'changed',
20:43:09.010 [pimatic-raspbee] debug:>  id: '6',
20:43:09.010 [pimatic-raspbee] debug:>  r: 'lights',
20:43:09.010 [pimatic-raspbee] debug:>  state: { bri: 215, lift: 85, on: true, open: true, reachable: true },
20:43:09.010 [pimatic-raspbee] debug:>  t: 'event',
20:43:09.010 [pimatic-raspbee] debug:>  uniqueid: '80:4b:50:ff:fe:2b:f5:c2-01'
20:43:09.010 [pimatic-raspbee] debug:>}
20:43:09.011 [pimatic-raspbee] debug: Received values: {
20:43:09.011 [pimatic-raspbee] debug:>  "id": 6,
20:43:09.011 [pimatic-raspbee] debug:>  "type": "event",
20:43:09.011 [pimatic-raspbee] debug:>  "event": "changed",
20:43:09.011 [pimatic-raspbee] debug:>  "resource": "lights",
20:43:09.011 [pimatic-raspbee] debug:>  "state": {
20:43:09.011 [pimatic-raspbee] debug:>    "bri": 215,
20:43:09.011 [pimatic-raspbee] debug:>    "lift": 85,
20:43:09.011 [pimatic-raspbee] debug:>    "on": true,
20:43:09.011 [pimatic-raspbee] debug:>    "open": true,
20:43:09.011 [pimatic-raspbee] debug:>    "reachable": true
20:43:09.011 [pimatic-raspbee] debug:>  },
20:43:09.011 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:43:09.011 [pimatic-raspbee] debug:>}
20:43:09.011 [pimatic-raspbee] debug: Lift action '85' not supported
=>STOP(?)
20:43:09.012 [pimatic-raspbee] debug: Received values: {
20:43:09.012 [pimatic-raspbee] debug:>  "id": 6,
20:43:09.012 [pimatic-raspbee] debug:>  "type": "event",
20:43:09.012 [pimatic-raspbee] debug:>  "event": "changed",
20:43:09.012 [pimatic-raspbee] debug:>  "resource": "lights",
20:43:09.012 [pimatic-raspbee] debug:>  "state": {
20:43:09.012 [pimatic-raspbee] debug:>    "bri": 215,
20:43:09.012 [pimatic-raspbee] debug:>    "lift": 85,
20:43:09.012 [pimatic-raspbee] debug:>    "on": true,
20:43:09.012 [pimatic-raspbee] debug:>    "open": true,
20:43:09.012 [pimatic-raspbee] debug:>    "reachable": true
20:43:09.012 [pimatic-raspbee] debug:>  },
20:43:09.012 [pimatic-raspbee] debug:>  "uniqueid": "80:4b:50:ff:fe:2b:f5:c2-01"
20:43:09.012 [pimatic-raspbee] debug:>}
20:43:09.012 [pimatic-raspbee] debug: Lift action '85' not supported

Before diving into the debug logs, is the SC400W-EU supported by Deconz?
Because the plugin now implements the api a defined by Deconz for a cover device.
The mapping of device specifics toward the standard api must be done by Deconz (thats what supporting is about).
In the plugin i can’t customize for a specific type of device, because thats not universal and possibly other devices will not work.

So do you have any info on support of this device?

Yes it works by deconz. I tested it already yesterday directly from the deconz gui and was also able to change the time of total movement, resp. until it toggels itself back into neutral.
I’m just searching in parallel on git, to what device it is equal …

As you know in Phoscon you can execute commands and get status info from the device.
Did you tried that?

@bertreb said in Release pimatic-raspbee@0.1.6:

As you know in Phoscon you can execute commands and get status info from the device.
Did you tried that?

Ok

Depends on what you mean.
The device is discovered in Phoscon as a dimable light and the behavior via the Phoscon gui was in the same manner poor as with the first switch we implemented. That was for me the reason to directly test it via the deconz gui.

Or is there additionally another possibility to ‘execute commands and get status’ which I might haven’t seen yet?

that is how it looks like:

A cover is in Deconz a Light device. That looks ok.
Important is that the state command and info are correct mapped.

ok, maybe in addtion, regarding the explained behaviour:
When I do the same and look at the Phoscon App, there the slider also moves to ‘in-between’ positions.
Is that what you are looking for?

What is the device class of the new shutter after a discovery?

RaspBeeCover

@pedder said in Release pimatic-raspbee@0.1.6:

ok, maybe in addtion, regarding the explained behaviour:
When I do the same and look at the Phoscon App, there the slider also moves to ‘in-between’ positions.
Is that what you are looking for?

Can you delete the device in Pimatic and test the behaviour of slider and shutter buttons?

? … but when I delete the device, there aren’t any buttons any longer !?

On the physical shutter?

ok deleted it from Pimatic, pushed the buttons on the device and looked at Phoscon, which works propperly

Yes, but what happens?
button up -> slider does ? for ? seconds and then goes to ?
etc

ahh, in Phoscon, yes?
ok:
pressing ‘open’, waiting 2-3 sec. ‘stopping’ then, the slider is also moved to somewhere around 20%
but also with the delay, means: having pressed ‘stop’ it needs 1-2 sec. that the slider is moved.

pressing only ‘open’ brings the slider, after the device has toggled itself back to ‘stop’, also after 1-2 sec. to 100% open

so it seems working really propperly

Ok, it seems the device has got its own rolling timer. That interferes with the rollingTimer from the plugin. And a stop does not set the slider to 50% (thats good!)
I need to check/edit the plugin on this.