Release pimatic-raspbee@0.1.6

---

ok, now it loaded again proppely
a bit wondering, as the presence circles of all devices are now not filled any longer, allthough they are ‘online’

Behavior of the TS302 is now again other:
when pressing ‘open’ in the gui, the device is triggered on ‘open’ but the gui stays on 5%, regardless how long ‘open’ is activated
’stop’ in the gui again toggels the device to ‘close’
‘close’ in the gui causes nothing => correction: when open status is larger then 5%, then ‘close’ from the gui also toggels ‘close’ on the device

additionally: when I use the slider and move it beyond 5%, then the gui counts up more, but when reaching e. g. 40%, it toggels itself back to ‘close’ and does the same with the device

The presence dots are not changed, clear the cache and refresh the gui will do the trick.

I will do some more testing on the TS302 tomorrow, and created an update for a new debug round.

ok, lets do this, its late again.
I hope I will be here tomorrow, as we have a mini-event in the family tomorrow

have good night!

Hi, i’ve been trying to reproduce the ‘stop hanging at 5%’.
I have an emulated TS302 and the commands are send ok and the counter is stepping up or down to 0 or 100%. I can stop in between, etc.

It could be that the TS302 is sending something back directly, when sending an up or down command. Can you check that?

But before checking the received messages, can you update raspbee.coffee and test again.
I changed something in the received message handling for the TS0302.

@bertreb said in Release pimatic-raspbee@0.1.6:

raspbee.coffee

ok, changed raspbee.coffe and now it doesn’t stop any longer at 5%
I will check now what comes back when pressing ‘open’ or ‘close’

as it is a bit difficult to find the right lines in the log, I now waited for 20:32h an then clicked:
‘open’ - waited - ‘close’ - waited - ‘stop’

20:32:03.494 [pimatic-raspbee] debug: new message received
20:32:03.501 [pimatic-raspbee] debug: {
20:32:03.501 [pimatic-raspbee] debug:>  e: 'changed',
20:32:03.501 [pimatic-raspbee] debug:>  id: '2',
20:32:03.501 [pimatic-raspbee] debug:>  r: 'lights',
20:32:03.501 [pimatic-raspbee] debug:>  state: { bri: 254, lift: 100, on: true, open: false, reachable: true },
20:32:03.501 [pimatic-raspbee] debug:>  t: 'event',
20:32:03.501 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
20:32:03.501 [pimatic-raspbee] debug:>}
20:32:03.503 [pimatic-raspbee] debug: Received values: {
20:32:03.503 [pimatic-raspbee] debug:>  "id": 2,
20:32:03.503 [pimatic-raspbee] debug:>  "type": "event",
20:32:03.503 [pimatic-raspbee] debug:>  "event": "changed",
20:32:03.503 [pimatic-raspbee] debug:>  "resource": "lights",
20:32:03.503 [pimatic-raspbee] debug:>  "state": {
20:32:03.503 [pimatic-raspbee] debug:>    "bri": 254,
20:32:03.503 [pimatic-raspbee] debug:>    "lift": 100,
20:32:03.503 [pimatic-raspbee] debug:>    "on": true,
20:32:03.503 [pimatic-raspbee] debug:>    "open": false,
20:32:03.503 [pimatic-raspbee] debug:>    "reachable": true
20:32:03.503 [pimatic-raspbee] debug:>  },
20:32:03.503 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
20:32:03.503 [pimatic-raspbee] debug:>}
20:32:03.602 [pimatic-raspbee] debug: updatePosition: 10
20:32:04.606 [pimatic-raspbee] debug: updatePosition: 15
20:32:05.615 [pimatic-raspbee] debug: updatePosition: 20
20:32:05.799 [pimatic-raspbee] debug: new message received
20:32:05.803 [pimatic-raspbee] debug: {
20:32:05.803 [pimatic-raspbee] debug:>  e: 'changed',
20:32:05.803 [pimatic-raspbee] debug:>  id: '3',
20:32:05.803 [pimatic-raspbee] debug:>  r: 'sensors',
20:32:05.803 [pimatic-raspbee] debug:>  state: {
20:32:05.803 [pimatic-raspbee] debug:>    current: 0,
20:32:05.803 [pimatic-raspbee] debug:>    lastupdated: '2021-03-16T19:32:05.797',
20:32:05.803 [pimatic-raspbee] debug:>    power: 0,
20:32:05.803 [pimatic-raspbee] debug:>    voltage: 224
20:32:05.803 [pimatic-raspbee] debug:>  },
20:32:05.803 [pimatic-raspbee] debug:>  t: 'event',
20:32:05.803 [pimatic-raspbee] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04'
20:32:05.803 [pimatic-raspbee] debug:>}
20:32:06.627 [pimatic-raspbee] debug: updatePosition: 25
20:32:07.649 [pimatic-raspbee] debug: updatePosition: 30
20:32:08.655 [pimatic-raspbee] debug: updatePosition: 35
20:32:09.661 [pimatic-raspbee] debug: updatePosition: 40
20:32:10.666 [pimatic-raspbee] debug: updatePosition: 45
20:32:11.485 [pimatic-raspbee] debug: ChangeStateTo close
20:32:11.494 [pimatic-raspbee] debug: move From: 45, To: 0
20:32:11.495 [pimatic-raspbee] debug:  +--> transitSeconds: 9, positionStep: -5
20:32:11.495 [pimatic-raspbee] debug: changeActionTo, @_sendState: {
20:32:11.495 [pimatic-raspbee] debug:>  "open": false,
20:32:11.495 [pimatic-raspbee] debug:>  "lift": 0,
20:32:11.495 [pimatic-raspbee] debug:>  "bri": 0
20:32:11.495 [pimatic-raspbee] debug:>}
20:32:11.506 [pimatic-raspbee] debug: updatePosition: 40
20:32:11.536 [pimatic-raspbee] debug: New value send to device Shutter01
20:32:11.539 [pimatic-raspbee] debug: { bri: 254, on: true }
20:32:11.560 [pimatic-raspbee] debug: new message received
20:32:11.563 [pimatic-raspbee] debug: {
20:32:11.563 [pimatic-raspbee] debug:>  attr: {
20:32:11.563 [pimatic-raspbee] debug:>    id: '2',
20:32:11.563 [pimatic-raspbee] debug:>    lastannounced: null,
20:32:11.563 [pimatic-raspbee] debug:>    lastseen: '2021-03-16T19:32Z',
20:32:11.563 [pimatic-raspbee] debug:>    manufacturername: '_TYZB01_dazsid15',
20:32:11.563 [pimatic-raspbee] debug:>    modelid: 'TS0302',
20:32:11.563 [pimatic-raspbee] debug:>    name: 'Shutter01',
20:32:11.563 [pimatic-raspbee] debug:>    swversion: '0xFFFFFFFF',
20:32:11.563 [pimatic-raspbee] debug:>    type: 'Window covering device',
20:32:11.563 [pimatic-raspbee] debug:>    uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
20:32:11.563 [pimatic-raspbee] debug:>  },
20:32:11.563 [pimatic-raspbee] debug:>  e: 'changed',
20:32:11.563 [pimatic-raspbee] debug:>  id: '2',
20:32:11.563 [pimatic-raspbee] debug:>  r: 'lights',
20:32:11.563 [pimatic-raspbee] debug:>  t: 'event',
20:32:11.563 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
20:32:11.563 [pimatic-raspbee] debug:>}
20:32:11.566 [pimatic-raspbee] debug: new message received
20:32:11.569 [pimatic-raspbee] debug: {
20:32:11.569 [pimatic-raspbee] debug:>  e: 'changed',
20:32:11.569 [pimatic-raspbee] debug:>  id: '2',
20:32:11.569 [pimatic-raspbee] debug:>  r: 'lights',
20:32:11.569 [pimatic-raspbee] debug:>  state: { bri: 0, lift: 0, on: false, open: true, reachable: true },
20:32:11.569 [pimatic-raspbee] debug:>  t: 'event',
20:32:11.569 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
20:32:11.569 [pimatic-raspbee] debug:>}
20:32:11.571 [pimatic-raspbee] debug: Received values: {
20:32:11.571 [pimatic-raspbee] debug:>  "id": 2,
20:32:11.571 [pimatic-raspbee] debug:>  "type": "event",
20:32:11.571 [pimatic-raspbee] debug:>  "event": "changed",
20:32:11.571 [pimatic-raspbee] debug:>  "resource": "lights",
20:32:11.571 [pimatic-raspbee] debug:>  "state": {
20:32:11.571 [pimatic-raspbee] debug:>    "bri": 0,
20:32:11.571 [pimatic-raspbee] debug:>    "lift": 0,
20:32:11.571 [pimatic-raspbee] debug:>    "on": false,
20:32:11.571 [pimatic-raspbee] debug:>    "open": true,
20:32:11.571 [pimatic-raspbee] debug:>    "reachable": true
20:32:11.571 [pimatic-raspbee] debug:>  },
20:32:11.571 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
20:32:11.571 [pimatic-raspbee] debug:>}
20:32:12.512 [pimatic-raspbee] debug: updatePosition: 35
20:32:13.518 [pimatic-raspbee] debug: updatePosition: 30
20:32:14.525 [pimatic-raspbee] debug: updatePosition: 25
20:32:15.199 [pimatic-raspbee] debug: new message received
20:32:15.203 [pimatic-raspbee] debug: {
20:32:15.203 [pimatic-raspbee] debug:>  e: 'changed',
20:32:15.203 [pimatic-raspbee] debug:>  id: '3',
20:32:15.203 [pimatic-raspbee] debug:>  r: 'sensors',
20:32:15.203 [pimatic-raspbee] debug:>  state: {
20:32:15.203 [pimatic-raspbee] debug:>    current: 0,
20:32:15.203 [pimatic-raspbee] debug:>    lastupdated: '2021-03-16T19:32:15.197',
20:32:15.203 [pimatic-raspbee] debug:>    power: 0,
20:32:15.203 [pimatic-raspbee] debug:>    voltage: 224
20:32:15.203 [pimatic-raspbee] debug:>  },
20:32:15.203 [pimatic-raspbee] debug:>  t: 'event',
20:32:15.203 [pimatic-raspbee] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04'
20:32:15.203 [pimatic-raspbee] debug:>}
20:32:15.531 [pimatic-raspbee] debug: updatePosition: 20
20:32:15.900 [pimatic-raspbee] debug: new message received
20:32:15.905 [pimatic-raspbee] debug: {
20:32:15.905 [pimatic-raspbee] debug:>  e: 'changed',
20:32:15.905 [pimatic-raspbee] debug:>  id: '65520',
20:32:15.905 [pimatic-raspbee] debug:>  r: 'groups',
20:32:15.905 [pimatic-raspbee] debug:>  state: { all_on: false, any_on: false },
20:32:15.905 [pimatic-raspbee] debug:>  t: 'event'
20:32:15.905 [pimatic-raspbee] debug:>}
20:32:15.908 [pimatic-raspbee] debug: new message received
20:32:15.911 [pimatic-raspbee] debug: {
20:32:15.911 [pimatic-raspbee] debug:>  e: 'changed',
20:32:15.911 [pimatic-raspbee] debug:>  id: '1',
20:32:15.911 [pimatic-raspbee] debug:>  r: 'groups',
20:32:15.911 [pimatic-raspbee] debug:>  state: { all_on: false, any_on: false },
20:32:15.911 [pimatic-raspbee] debug:>  t: 'event'
20:32:15.911 [pimatic-raspbee] debug:>}
20:32:16.535 [pimatic-raspbee] debug: updatePosition: 15
20:32:17.540 [pimatic-raspbee] debug: updatePosition: 10
20:32:18.546 [pimatic-raspbee] debug: updatePosition: 5
20:32:19.551 [pimatic-raspbee] debug: updatePosition: 0
20:32:20.554 [pimatic-raspbee] debug: stopCoverSend, @_sendState: {
20:32:20.554 [pimatic-raspbee] debug:>  "stop": true
20:32:20.554 [pimatic-raspbee] debug:>}
20:32:20.583 [pimatic-raspbee] debug: New value send to device Shutter01
20:32:20.588 [pimatic-raspbee] debug: { bri: 127 }
20:32:20.804 [pimatic-raspbee] debug: new message received
20:32:20.808 [pimatic-raspbee] debug: {
20:32:20.808 [pimatic-raspbee] debug:>  e: 'changed',
20:32:20.808 [pimatic-raspbee] debug:>  id: '3',
20:32:20.808 [pimatic-raspbee] debug:>  r: 'sensors',
20:32:20.808 [pimatic-raspbee] debug:>  state: {
20:32:20.808 [pimatic-raspbee] debug:>    current: 0,
20:32:20.808 [pimatic-raspbee] debug:>    lastupdated: '2021-03-16T19:32:20.802',
20:32:20.808 [pimatic-raspbee] debug:>    power: 0,
20:32:20.808 [pimatic-raspbee] debug:>    voltage: 224
20:32:20.808 [pimatic-raspbee] debug:>  },
20:32:20.808 [pimatic-raspbee] debug:>  t: 'event',
20:32:20.808 [pimatic-raspbee] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04'
20:32:20.808 [pimatic-raspbee] debug:>}
20:32:22.219 [pimatic-raspbee] debug: ChangeStateTo stop
20:32:22.227 [pimatic-raspbee] debug: changeActionTo, @_sendState: {
20:32:22.227 [pimatic-raspbee] debug:>  "stop": true
20:32:22.227 [pimatic-raspbee] debug:>}
20:32:22.273 [pimatic-raspbee] debug: New value send to device Shutter01
20:32:22.278 [pimatic-raspbee] debug: { bri: 127 }
20:32:26.702 [pimatic-raspbee] debug: new message received
20:32:26.705 [pimatic-raspbee] debug: {
20:32:26.705 [pimatic-raspbee] debug:>  e: 'changed',
20:32:26.705 [pimatic-raspbee] debug:>  id: '3',
20:32:26.705 [pimatic-raspbee] debug:>  r: 'sensors',
20:32:26.705 [pimatic-raspbee] debug:>  state: {
20:32:26.705 [pimatic-raspbee] debug:>    current: 0,
20:32:26.705 [pimatic-raspbee] debug:>    lastupdated: '2021-03-16T19:32:26.700',
20:32:26.705 [pimatic-raspbee] debug:>    power: 0,
20:32:26.705 [pimatic-raspbee] debug:>    voltage: 224
20:32:26.705 [pimatic-raspbee] debug:>  },
20:32:26.705 [pimatic-raspbee] debug:>  t: 'event',
20:32:26.705 [pimatic-raspbee] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04'
20:32:26.705 [pimatic-raspbee] debug:>}

but wondering a bit, as also the ‘stop’ command (with that 50%) you already got working.
Has that now something with the combination of both to do?

Ok, that looks ok.
How is the overall response?

which response? anything else outside the log-file?

if you mean the reaction of the device, this is fine, very quick

but the problem stays, ‘stop’ seems pushing the same as ‘close’

I mean the up, down and stop buttons and the reaction of the shutter.

works good, all propper, except the fault of ‘stop’, as written

Because something changed and what i understand the position doesn’t stop anymore at 5%.
Can you explain what the stop fault is?

@bertreb said in Release pimatic-raspbee@0.1.6:

Because something changed and what i understand the position doesn’t stop anymore at 5%.

right, this mistake has gone

When pressing the ‘stop’ button in the gui, the gui flips to ‘close’ and also the device is triggered to ‘close’.
When in the end the percentages in the gui reaches 0%, then the button in the gui flips back to ‘stop’ where it should have been directly, when pressing it.
That is what I meant by, the ‘stop’ button’ triggers the same as the ‘close’ button.

In addition: this only happens when using the gui. Using the buttons of the device/switch itself, all is good.

To understand, my summary of what you are saying.
The starting position is cover fully open (slider 100%) and the ‘stop’ button is active (blue).
Then you push ‘stop’ again and the button ‘close’ gets active.

…
The starting position is nearly regardless.
Whenever pushing ‘stop’ in the gui, when the position is something >0% open, then the gui directly flips to ‘close’ and also the shutter device is toggled to ‘close’.

or

When moving the slider to something >0% open, it first opens (gui and device), but when reaching the choosen position, e. g. 20%, then ‘stop’ is triggered, what would be correct, but as above, it directly (<1sec) automatically flips to ‘close’ and thus, the device/shutter closes directly again.

… not that easy to explain …

Yes, because i don’t have a real TS0302 its difficult debugging.
I simplified the commands send to the shutter, to the minimum.
Please update raspbee.coffee to test it

I’m sorry, no change.
Shall I search for one of the earlier raspbee-coffee files, where the TS0302 already worked?
Maybe I can derive this by the name ‘raspbee.coffe_bak_something’ I gave the older ones

… or maybe I can first test it here, if it works with TS0302 !?

Yes thats a good plan.

on my way

ok, the problem doesn’t come from raspbee.coffee
I had to change also device-config-schema.coffee

I will send you in parallel both version from 07th of March by mail on which basis the TS0302 already worked

I did an additional check, as the TS130F is still connected:
Steering this by the gui works perfect too, but only the signals coming back from the device doesn’t trigger the gui to change, resp. the movement by manual steering via the device is not reflected.