Release pimatic-raspbee@0.1.6

---

Thanks a lot for the info
The way it works is that when you push a button, the gui reacts and the related command is sent to the shutter device.
The response of the shutter device can influencing the acting of the plugin/gui. And that is something i couldn’t test.
What would help if you can filter messages coming from the shutter device after you pushes an up or down button

And there is no neutral or 50% position anymore in the plugin!
So what do you mean by ‘Out of the neutral 50% position:’?

here we go
Switched ‘open’ out of the ‘neutral’ (50%) position and waited in the end to let the device flip back itself:

21:32:11.163 [pimatic-raspbee] debug: ChangeStateTo open
21:32:11.172 [pimatic-raspbee] debug: moveTo: 50, target: 100, _transitSeconds: 10, _positionStep: 5
21:32:11.179 [pimatic-raspbee] debug: updatePosition: 60
21:32:11.181 [pimatic-raspbee] debug: changeActionTo, @_sendState: {
21:32:11.181 [pimatic-raspbee] debug:>  "open": true
21:32:11.181 [pimatic-raspbee] debug:>}
21:32:11.200 [pimatic-raspbee] debug: Position: 55
21:32:11.259 [pimatic-raspbee] debug: New value send to device WindowCov01
21:32:11.264 [pimatic-raspbee] debug: { open: true }
21:32:11.284 [pimatic-raspbee] debug: new message received
21:32:11.292 [pimatic-raspbee] debug: { e: 'changed',
21:32:11.292 [pimatic-raspbee] debug:>  id: '2',
21:32:11.292 [pimatic-raspbee] debug:>  r: 'lights',
21:32:11.292 [pimatic-raspbee] debug:>  state:
21:32:11.292 [pimatic-raspbee] debug:>   { bri: 254, lift: 100, on: true, open: false, reachable: true },
21:32:11.292 [pimatic-raspbee] debug:>  t: 'event',
21:32:11.292 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' }
21:32:11.294 [pimatic-raspbee] debug: Received values: {
21:32:11.294 [pimatic-raspbee] debug:>  "id": 2,
21:32:11.294 [pimatic-raspbee] debug:>  "type": "event",
21:32:11.294 [pimatic-raspbee] debug:>  "event": "changed",
21:32:11.294 [pimatic-raspbee] debug:>  "resource": "lights",
21:32:11.294 [pimatic-raspbee] debug:>  "state": {
21:32:11.294 [pimatic-raspbee] debug:>    "bri": 254,
21:32:11.294 [pimatic-raspbee] debug:>    "lift": 100,
21:32:11.294 [pimatic-raspbee] debug:>    "on": true,
21:32:11.294 [pimatic-raspbee] debug:>    "open": false,
21:32:11.294 [pimatic-raspbee] debug:>    "reachable": true
21:32:11.294 [pimatic-raspbee] debug:>  },
21:32:11.294 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
21:32:11.294 [pimatic-raspbee] debug:>}
21:32:11.296 [pimatic-raspbee] debug: moveTo: 55, target: 0, _transitSeconds: 11, _positionStep: -5
21:32:11.297 [pimatic-raspbee] debug: updatePosition: 45
21:32:11.307 [pimatic-raspbee] debug: Position: 50
21:32:12.314 [pimatic-raspbee] debug: updatePosition: 40
21:32:12.325 [pimatic-raspbee] debug: Position: 45
21:32:13.334 [pimatic-raspbee] debug: updatePosition: 35
21:32:13.340 [pimatic-raspbee] debug: Position: 40
21:32:14.348 [pimatic-raspbee] debug: updatePosition: 30
21:32:14.351 [pimatic-raspbee] debug: Position: 35
21:32:15.358 [pimatic-raspbee] debug: updatePosition: 25
21:32:15.365 [pimatic-raspbee] debug: Position: 30
21:32:16.372 [pimatic-raspbee] debug: updatePosition: 20
21:32:16.376 [pimatic-raspbee] debug: Position: 25
21:32:17.384 [pimatic-raspbee] debug: updatePosition: 15
21:32:17.389 [pimatic-raspbee] debug: Position: 20
21:32:18.395 [pimatic-raspbee] debug: updatePosition: 10
21:32:18.399 [pimatic-raspbee] debug: Position: 15
21:32:19.406 [pimatic-raspbee] debug: updatePosition: 5
21:32:19.412 [pimatic-raspbee] debug: Position: 10
21:32:20.420 [pimatic-raspbee] debug: updatePosition: 0
21:32:20.426 [pimatic-raspbee] debug: Position: 5
21:32:21.433 [pimatic-raspbee] debug: updatePosition: -5
21:32:21.436 [pimatic-raspbee] debug: Position: 0
21:32:30.298 [pimatic-raspbee] debug: new message received
21:32:30.303 [pimatic-raspbee] debug: { attr:
21:32:30.303 [pimatic-raspbee] debug:>   { id: '1',
21:32:30.303 [pimatic-raspbee] debug:>     lastannounced: null,
21:32:30.303 [pimatic-raspbee] debug:>     lastseen: '2021-02-22T20:32Z',
21:32:30.303 [pimatic-raspbee] debug:>     manufacturername: 'dresden elektronik',
21:32:30.303 [pimatic-raspbee] debug:>     modelid: 'ConBee II',
21:32:30.303 [pimatic-raspbee] debug:>     name: 'Configuration tool 1',
21:32:30.303 [pimatic-raspbee] debug:>     swversion: null,
21:32:30.303 [pimatic-raspbee] debug:>     type: 'Configuration tool',
21:32:30.303 [pimatic-raspbee] debug:>     uniqueid: '00:21:2e:ff:ff:06:15:e6-01' },
21:32:30.303 [pimatic-raspbee] debug:>  e: 'changed',
21:32:30.303 [pimatic-raspbee] debug:>  id: '1',
21:32:30.303 [pimatic-raspbee] debug:>  r: 'lights',
21:32:30.303 [pimatic-raspbee] debug:>  t: 'event',
21:32:30.303 [pimatic-raspbee] debug:>  uniqueid: '00:21:2e:ff:ff:06:15:e6-01' }
21:32:32.708 [pimatic-raspbee] debug: new message received
21:32:32.715 [pimatic-raspbee] debug: { attr:
21:32:32.715 [pimatic-raspbee] debug:>   { id: '2',
21:32:32.715 [pimatic-raspbee] debug:>     lastannounced: '2021-02-21T20:08:24Z',
21:32:32.715 [pimatic-raspbee] debug:>     lastseen: '2021-02-22T20:32Z',
21:32:32.715 [pimatic-raspbee] debug:>     manufacturername: '_TYZB01_dazsid15',
21:32:32.715 [pimatic-raspbee] debug:>     modelid: 'TS0302',
21:32:32.715 [pimatic-raspbee] debug:>     name: 'WindCov01',
21:32:32.715 [pimatic-raspbee] debug:>     powerup: 7,
21:32:32.715 [pimatic-raspbee] debug:>     swversion: '0xFFFFFFFF',
21:32:32.715 [pimatic-raspbee] debug:>     type: 'Window covering device',
21:32:32.715 [pimatic-raspbee] debug:>     uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' },
21:32:32.715 [pimatic-raspbee] debug:>  e: 'changed',
21:32:32.715 [pimatic-raspbee] debug:>  id: '2',
21:32:32.715 [pimatic-raspbee] debug:>  r: 'lights',
21:32:32.715 [pimatic-raspbee] debug:>  t: 'event',
21:32:32.715 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' }
21:33:11.888 [pimatic-raspbee] debug: new message received
21:33:11.893 [pimatic-raspbee] debug: { e: 'changed',
21:33:11.893 [pimatic-raspbee] debug:>  id: '2',
21:33:11.893 [pimatic-raspbee] debug:>  r: 'lights',
21:33:11.893 [pimatic-raspbee] debug:>  state:
21:33:11.893 [pimatic-raspbee] debug:>   { bri: 127, lift: 50, on: true, open: true, reachable: true },
21:33:11.893 [pimatic-raspbee] debug:>  t: 'event',
21:33:11.893 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' }
21:33:11.894 [pimatic-raspbee] debug: Received values: {
21:33:11.894 [pimatic-raspbee] debug:>  "id": 2,
21:33:11.894 [pimatic-raspbee] debug:>  "type": "event",
21:33:11.894 [pimatic-raspbee] debug:>  "event": "changed",
21:33:11.894 [pimatic-raspbee] debug:>  "resource": "lights",
21:33:11.894 [pimatic-raspbee] debug:>  "state": {
21:33:11.894 [pimatic-raspbee] debug:>    "bri": 127,
21:33:11.894 [pimatic-raspbee] debug:>    "lift": 50,
21:33:11.894 [pimatic-raspbee] debug:>    "on": true,
21:33:11.894 [pimatic-raspbee] debug:>    "open": true,
21:33:11.894 [pimatic-raspbee] debug:>    "reachable": true
21:33:11.894 [pimatic-raspbee] debug:>  },
21:33:11.894 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
21:33:11.894 [pimatic-raspbee] debug:>}
21:33:11.896 [pimatic-raspbee] debug: moveTo: 0, target: 50, _transitSeconds: 10, _positionStep: 5
21:33:11.899 [pimatic-raspbee] debug: updatePosition: 10
21:33:11.912 [pimatic-raspbee] debug: Position: 5
21:33:12.918 [pimatic-raspbee] debug: updatePosition: 15
21:33:12.924 [pimatic-raspbee] debug: Position: 10
21:33:13.932 [pimatic-raspbee] debug: updatePosition: 20
21:33:13.935 [pimatic-raspbee] debug: Position: 15
21:33:14.941 [pimatic-raspbee] debug: updatePosition: 25
21:33:14.946 [pimatic-raspbee] debug: Position: 20
21:33:15.953 [pimatic-raspbee] debug: updatePosition: 30
21:33:15.956 [pimatic-raspbee] debug: Position: 25
21:33:16.963 [pimatic-raspbee] debug: updatePosition: 35
21:33:16.970 [pimatic-raspbee] debug: Position: 30

Thanks, good info.
Still a question on ‘neutral’. I understand 50% but not the term neutral.

I the debug log it seems that after send open:true, a open:false is send back. I can add also the lift value, when sending the command.

still the same, only my wording shall mean, that the device(s) are back to ‘stop’, resp. 50% on the slider

And yes I also interpreted it the way that something comes back.
you mean when using the slider, then sending the lift value, right? - because the buttons are anyhow only 0 or 100%, unless someone stops it manually

additional, forgot to mention that below:
the status also shows it wrongly, same as the slider and the percentages

To summarise, the way I designed it

• push close ->
  – send to shutter {‘close’:true,‘lift’:100}
  – slider moves directly to 0%
  – open % steps down to 0%
  – on 0% button stop gets active
  – send to shutter {‘stop’:true}
• push open ->
  – send to shutter {‘close’:false,‘lift’:0}
  – slider moves directly to 100%
  – open % steps up to 100%
  – on 100% button stop gets active
  – send to shutter {‘stop’:true}
• push stop ->
  – current step change stops
  – slider moves to actual open % position
• sliding the slider ->
  – send to shutter {‘lift’:<inverse slider position>}
  – depending on value, in steps go up or in steps go down
  – on up button, open gets ‘active’ – on close button, close gets ‘active’
  – stop at 0% or 100%
  – send to shutter {‘stop’:true}

Let me know if this is what you also expect.
Lets wait for the updated raspbee.coffee what the response of the shutter is.

And i updated raspbee.coffee with the extra info in the command sent to the shutter.

@bertreb said in Release pimatic-raspbee@0.1.6:

with the extra info in the command

I doublechecked twice and it sounds good!

What I’m maybe not getting 100% is this:
sliding the slider ->
– send to shutter {‘lift’:<inverse slider position>}

but I guess that goes back to thew fact, that open position is 0 and close position is 100, right?

Did you implement this already within the last minutes?

What i wrote above is what I designed from the start.
In the debug rounds, i switched off and on some of these steps.
But in the latest version this is all back again.

The slider moves from left: darkblue = closed to right: white = open
The lift value is the opposite (invers) value, because 100% lift is fully closed, so 0 % on the slider

The big question now is, what is the shutter sending back and what to do with it?

Ahh, now I got you. I thought you again developed a new raspee.coffee setup.

Ok, but if it is designed that way, normally it should work, resp. would show a correct behaviour of the gui, if the device wouldn’t send back whatever nonsens …

Wouldn’t it be possible to simply ignor that in general? - except the flip-back to the stop position

You could ignore it, but then you don’t need to use the buttons on the shutter and just see it as a Zigbee receiver.
Is still tilt:50% coming back as stop command?

As send in the logfile below, I guess that this is, what is send back:
(I explicitely waited in that round for the device flipping back to ‘stop’)

21:33:11.888 [pimatic-raspbee] debug: new message received
21:33:11.893 [pimatic-raspbee] debug: { e: 'changed',
21:33:11.893 [pimatic-raspbee] debug:>  id: '2',
21:33:11.893 [pimatic-raspbee] debug:>  r: 'lights',
21:33:11.893 [pimatic-raspbee] debug:>  state:
21:33:11.893 [pimatic-raspbee] debug:>   { bri: 127, lift: 50, on: true, open: true, reachable: true },
21:33:11.893 [pimatic-raspbee] debug:>  t: 'event',
21:33:11.893 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' }
21:33:11.894 [pimatic-raspbee] debug: Received values: {
21:33:11.894 [pimatic-raspbee] debug:>  "id": 2,
21:33:11.894 [pimatic-raspbee] debug:>  "type": "event",
21:33:11.894 [pimatic-raspbee] debug:>  "event": "changed",
21:33:11.894 [pimatic-raspbee] debug:>  "resource": "lights",
21:33:11.894 [pimatic-raspbee] debug:>  "state": {
21:33:11.894 [pimatic-raspbee] debug:>    "bri": 127,
21:33:11.894 [pimatic-raspbee] debug:>    "lift": 50,
21:33:11.894 [pimatic-raspbee] debug:>    "on": true,
21:33:11.894 [pimatic-raspbee] debug:>    "open": true,
21:33:11.894 [pimatic-raspbee] debug:>    "reachable": true
21:33:11.894 [pimatic-raspbee] debug:>  },
21:33:11.894 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
21:33:11.894 [pimatic-raspbee] debug:>}

I made an update of raspbee.coffee that handles only the 50% stop command from the shutter.

nearly perfect

do I have to erase again ‘,js’?

Because I didn’t and now the close and the open buttons causes ‘bad request’ errors

You only updated raspbee.coffee?

yes only …

Ok, delete .js again

no, didn’t work, allthough I additionally deleted the device from Pimatic and then got it newly in

The slider, the percentages and the status now are working perfectly - incl. steering the device.
And also when moving the slider, the ‘open/close’ buttons of the raspbee device are managed propperly.

The conclusion for now is that its working?