Release pimatic-raspbee@0.1.6

---

I send a ‘30’, converted into 16bit integer, as the pop-up of the field says, that it should be that format.

deconz apr rest test? - sorry I have no clue how that works

And scrolling down to the attributes, that looks like, as nothing has been set there:

You are sending 3 different values, 1 for every exec key you use

I assume that there are values send, but how shall I fetch them?

To check it more step-by-step, I made a ‘send only’ version of raspbee.coffee
Only actions from the gui are send to deconz/the shutter

@pedder said in Release pimatic-raspbee@0.1.6:

I assume that there are values send, but how shall I fetch them?

You do not need to check it, lets try the send-only version

ok, exchanged it.
Works as yesterday, but still incl. switching to ‘close’ than to ‘stop’

But pushing the buttons on the shutter, doesn’t have a response in the gui?

correct!

Are you sure that stop is 50%?
I read somewhere on the deconz forum that
open = 100%
close = 50%
stop = 0%

Well, I just checked it in the Phoscon App and there the slider goes to the top when pressing up, to the middle when pressing stop and to the bottom when pressing down. I assume that equal to 100% - 50% - 0% from top to bottom:

Can you check also on the Phoscon app, what the slider does when pushing the buttons on the gui?

just started to write:-) … nothing!

well test again, and a bit happens: when slider is on 0 or 50 and then pressing on the lamp symbol, the slider goes up and the device is toggled on ‘up’

Yes, because you are switching the light on (=100%)

I made an update of raspbee.coffee
Pushing

• close sends lift=100%
• stop sends lift=50%
• open sends lift=0%

and Lift is percentage closed! (the opposite of brightness)

now pressing ‘open’ in the gui decreases the percentages and the device is pressed on 'open’
pressing ‘close’ in the gui increases the percentages and the device is pressed on 'close’
pressing stop still presses the device on ‘close’

Ok, next update of raspbee.coffee with also the depreciated values set

hmhm, now the ‘stop’ and the ‘close’ button in the guis both seems doing nothing.
when pressing ‘open’, the open value decreases and next time, after pressing ‘stop’ in between, the value increases …

that all doesn’t look logical …

And is the Deconz gui also not reacting ok?

I have no clue as I had to close it.
You can run deconz only via the rest api OR via the gui. Both at the same time is not possible.
I learned that last year on GitHub

Without a shutter device, its getting difficult to debug this in an efficient way.
The current plugin/ cover device is just sending 3 ‘light’ type values for the 3 buttons.
And no extra logic is used.
I tried to get such a device, but i didn’t found a fast delivery option.