Release pimatic-raspbee@0.1.6

---

[0.1.6]

Fixed

• #47 Hotfix for new deconz version 2.5.78

Hotfix 0.1.7 released

the 0.1.6 was empty.
had me tangled with the branches.

Hi @kosta, thanks very much
Does this update eventually also tackle my demand with regard to the shutter device?
https://forum.pimatic.org/topic/4870/zigbee-shutter-control-not-working-missing-raspbee-shutter-device

Hi.

I updated my deconz to version 2.07.01 / 8.12.2020 and the firmware to version 26660700.
Since I did that I get Bad request every time I try to control my ikea blinds.
All my remotes and motion sensors are not reporting their status.
The funny thing is, the ikea blind reports when I manually press the button to open or close it on the blind,but if I press anything in pimatic, then I just get bad request prompt.

Update. Suddenly the motion sensors and remotes started working. But I’m still getting this bad request thing with the ikea blinds setup as a raspbee dimmer.

Did you rediscover/connect the blinds in deconz and what is the type of device?

@bertreb Good morning.
Yes I tried to delete and rediscover the blinds. Same problem. It was only after updating my deconz and the firmware on the conbee 2 stick that it broke with the ikea fyrtur blinds.

Device in pimatic is RaspBeeDimmer.

I have started migration to zigbee2mqtt, as I already have this running for my door lock, but of course it would be preferable to have deconz working properly with pimatic as well.

Hi, i assume you use the deconz gui to add devices. What is the device type in deconz when you add an Ikea blind?

Ah okay, now I understand. It is setup in Phoscon as a Light.
The remotes are setup as switches.
This setup have worked for the past year or whenever I bought them.

I should just have left them alone and not updated the firmware and software. Don’t fix it if it ain’t broken. Well I guess we learn from our mistakes 😅

Ok, you could try deleting the blinds device in deconz and rediscover/connect it.

Okay. Just tried deleting it in Phoscon. Add the signal repeater and blind again. After that I discovered the new device in pimatic. Still getting the same Bad request error with the blind.

We are waiting for @kosta to add the cover device in pimatic-raspbee.

I created a fork of pimatic-raspbee with a cover device added.
You can try this by downloading the fork (https://github.com/bertreb/pimatic-raspbee.git)

For the minimum change (without the rules actions) 3 files need to be replaces/changed:

• device-config-schema.coffee
• raspbee.coffee (thats where the extra shutter logic is)
• action.coffee

Steps:

• backup the 3 current files
• paste the new files in the pimatic-raspbee directory.
• check if the raspbee debug is enabled in the plugin settings
• restart Pimatic and watch the debug/error log

@bertreb hi again.

I tried to switch the files you mentioned to your version from github and restarted, but no change as far I can see. No new device type when discovering the blind.
Same error if I use the dimmer device as worked before the update.

Can you manually add a RaspBeeCover device?
Did you do a Pimatic discovery or a deconz discovery?

Hmm
No it doesn’t show up either when I try to manually make the device in pimatic.
It was pimatic discovery I tried.
I downloaded this file
https://github.com/bertreb/pimatic-raspbee/archive/master.zip
And extracted the 3 files you mentioned, replaced and restarted the pi.

Very strange that it doesn’t show up in pimatic as an option. When did you add this cover option? It says lays updated in beginning of November.

Strange
Can you check the file device-config-schema.coffee in the pimatic-raspbee directory and see if the coverDevice is there.
If so, stop pimatic daemon and start pimatic via the commandline.
In directory pimatic-app run the command 'sudo node_modules/pimatic/pimatic.js’
You can see if the new files are compiled.

Hmm I don’t understand it.

The device is inside the file. I is just not loaded by pimatic.
I tried deactivating the plugin, restarting and activating again. At the same time I don’t see any error related to this.

I will try a few more times.

Thanks for responding! 😊

RaspBeeCover: {
title: "Raspbee Cover Device"
type: "object"
properties:
deviceID:
description: "Raspbee address"
type: "integer"
transtime:
description: "Raspbee transtime"
type: "integer"
default: 5
}

Stop pimatic (sudo service pimatic stop) and delete the directory .js in the pimatic-raspbee directory (rm -rf .js)
This directory contains the compiled coffeescript files.
Start pimatic again (sudo service pimatic start)
This will force a recompile of the coffeescript files.

Thanks. That did work.
It now shows up in pimatic as raspbee cover and when making a new discovery it does work with the blind.
But sadly the blind have a new strange behavior.

When pressing the ON button it used to close the blind. Now it does nothing when it is open.
I can manually input a value from 1-99 in the dimmer part and it will control the blind correctly, but inverse position from what it used to be . If I press OFF it does go back up like it should. But the position of the slider is wrong.
It’s like that the position is inverted somehow.

I guess I can make some rules to counteract the new behavior, but it is not ideal.