Release pimatic-raspbee@0.1.6

---

Yes, i can customise it back for the TS0302, but then the TS130F will not work.
They are really 2 different behaving devices. And who knows, how other zigbee shutter devices will work.
Making a seperate raspbee device class for every zigbee shutter implementation, is not how it should work.
I need to find a solution for this.

Will be continued…

ok, I feared that.
As it’s getting late, may we close for today and continue the next days? - when you might have an idea?

I made the following changes:

• removed the simulate mode. The rollerTime countdown/up is now always active
• added selectable coverType to device config => “TS130F” or “TS0302”

Update raspbee.coffee and device-config-schema.coffee

Please remove the ‘simulate’ lines(s) from config.json (to prevent error message) and set the right coverType.

@bertreb said in Release pimatic-raspbee@0.1.6:

simulate’ lines(s) f

Hi again, that looks much better, here the behaviors:
TS130F:
Everything seems working super
When steering by the device, the slider and the percentages are adjusted after stopping. Steering from the gui, directly shows the right percentages, slider moves when stopped.

TS302:
Steering from the device is perfect, incl. that the percentage constantly changes while the shutter is moving.
Steering from the gui has some problems: Pressing ‘close’ is ok, but pressing ‘open’ also triggers ‘close’ and pressing ‘stop’ triggers nothing on the device, whereas the behavior of the slider and the percentages is good.

I looked into config.json and there haven’t been any ‘simulate’ lines. I also do not get any error messages.

The simulate was then default and not in the config. Thats ok.

I made a change to the gui commands for the TS0302, please update raspbee.coffee

And for the TS130F.
The update of the gui at the end of the action, is because the info from the device isn’t send until the stop.
So its not possible to update the gui before that.

@bertreb said in Release pimatic-raspbee@0.1.6:

The update of the gui at the end of the action, is because the info from the device isn’t send until the stop.

… which I already understood

@bertreb said in Release pimatic-raspbee@0.1.6:

I made a change to the gui commands for the TS0302

pressing ‘open’ in the gui now works correct, but when pressing ‘stop’ it toggels the device to ‘close’

When you press ‘stop’, what do you see in the debug on the line ‘Received values: …’

@bertreb said in Release pimatic-raspbee@0.1.6:

the debug

22:50:41.035 [pimatic-raspbee] debug:>}
22:50:41.036 [pimatic-raspbee] debug: Received values: {
22:50:41.036 [pimatic-raspbee] debug:>  "id": 2,
22:50:41.036 [pimatic-raspbee] debug:>  "type": "event",
22:50:41.036 [pimatic-raspbee] debug:>  "event": "changed",
22:50:41.036 [pimatic-raspbee] debug:>  "resource": "lights",
22:50:41.036 [pimatic-raspbee] debug:>  "state": {
22:50:41.036 [pimatic-raspbee] debug:>    "bri": 0,
22:50:41.036 [pimatic-raspbee] debug:>    "lift": 0,
22:50:41.036 [pimatic-raspbee] debug:>    "on": false,
22:50:41.036 [pimatic-raspbee] debug:>    "open": true,
22:50:41.036 [pimatic-raspbee] debug:>    "reachable": true
22:50:41.036 [pimatic-raspbee] debug:>  },
22:50:41.036 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
22:50:41.036 [pimatic-raspbee] debug:>}
```

Thats not what i would expect. This is a state ‘open’ message.

And what is the debug (after the stop) after the line
’ New value send to device …’

I firstly tested to sent all three open, close, stop to the device, that looks as follows
(will check for your question in a minute)

22:58:53.424 [pimatic-raspbee] debug: new message received
22:58:53.427 [pimatic-raspbee] debug: {
22:58:53.427 [pimatic-raspbee] debug:>  attr: {
22:58:53.427 [pimatic-raspbee] debug:>    id: '2',
22:58:53.427 [pimatic-raspbee] debug:>    lastannounced: null,
22:58:53.427 [pimatic-raspbee] debug:>    lastseen: '2021-03-15T21:58Z',
22:58:53.427 [pimatic-raspbee] debug:>    manufacturername: '_TYZB01_dazsid15',
22:58:53.427 [pimatic-raspbee] debug:>    modelid: 'TS0302',
22:58:53.427 [pimatic-raspbee] debug:>    name: 'Shutter01',
22:58:53.427 [pimatic-raspbee] debug:>    swversion: '0xFFFFFFFF',
22:58:53.427 [pimatic-raspbee] debug:>    type: 'Window covering device',
22:58:53.427 [pimatic-raspbee] debug:>    uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
22:58:53.427 [pimatic-raspbee] debug:>  },
22:58:53.427 [pimatic-raspbee] debug:>  e: 'changed',
22:58:53.427 [pimatic-raspbee] debug:>  id: '2',
22:58:53.427 [pimatic-raspbee] debug:>  r: 'lights',
22:58:53.427 [pimatic-raspbee] debug:>  t: 'event',
22:58:53.427 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
22:58:53.427 [pimatic-raspbee] debug:>}
22:58:53.430 [pimatic-raspbee] debug: new message received
22:58:53.433 [pimatic-raspbee] debug: {
22:58:53.433 [pimatic-raspbee] debug:>  e: 'changed',
22:58:53.433 [pimatic-raspbee] debug:>  id: '2',
22:58:53.433 [pimatic-raspbee] debug:>  r: 'lights',
22:58:53.433 [pimatic-raspbee] debug:>  state: { bri: 127, lift: 50, on: true, open: true, reachable: true },
22:58:53.433 [pimatic-raspbee] debug:>  t: 'event',
22:58:53.433 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01'
22:58:53.433 [pimatic-raspbee] debug:>}
22:58:53.434 [pimatic-raspbee] debug: Received values: {
22:58:53.434 [pimatic-raspbee] debug:>  "id": 2,
22:58:53.434 [pimatic-raspbee] debug:>  "type": "event",
22:58:53.434 [pimatic-raspbee] debug:>  "event": "changed",
22:58:53.434 [pimatic-raspbee] debug:>  "resource": "lights",
22:58:53.434 [pimatic-raspbee] debug:>  "state": {
22:58:53.434 [pimatic-raspbee] debug:>    "bri": 127,
22:58:53.434 [pimatic-raspbee] debug:>    "lift": 50,
22:58:53.434 [pimatic-raspbee] debug:>    "on": true,
22:58:53.434 [pimatic-raspbee] debug:>    "open": true,
22:58:53.434 [pimatic-raspbee] debug:>    "reachable": true
22:58:53.434 [pimatic-raspbee] debug:>  },
22:58:53.434 [pimatic-raspbee] debug:>  "uniqueid": "ec:1b:bd:ff:fe:8f:10:92-01"
22:58:53.434 [pimatic-raspbee] debug:>}

Seems that only ‘stop’ is send

may I send the entire logfile via mail? after having again pressed open - stop - close

To prevent that I maybe captured the wrong lines…

Good idea, but please first update raspbee.coffee

hm, larger problems now.

regardless which button I try to click in the gui, Pimatic always says:
‘error [pimatic]: device hasn’t that action’

already restarted Pimatic, I will restart deconz also …

@pedder said in Release pimatic-raspbee@0.1.6:

device hasn’t that action

Please check if the plugin is loaded.

that seems not to be the case:
23:16:47.412 [pimatic] info: Loading plugin: “pimatic-raspbee” (0.1.7)
coffee-cache: compiling coffee-script file “raspbee.coffee”…23:16:53.126 [pimatic] error: unexpected >

I know why the plugin didn’t load. Please update raspbee.coffee