ZigBee Shutter Control not working - missing RaspBee Shutter Device

---

@pedder said in ZigBee Shutter Control not working - missing RaspBee Shutter Device:

@bertreb, found it now, thanks!
As I never did it that way before: Would I only have to exchange my current ‘device-config-schema.coffee’ (in the node-modules/pimatic-raspbee directory) by your new file? … and then for sure restart Pimatic.

@theslashy, thats wondering. Here it worked definetly after learing it by the Phoscon App as a light - as written in my last post on Github, end of September.

@Both, as written, I will order another stick and then start testing. It’s listet at am…on as 1-Day-Delivery …

For the minimum change (without the rules actions) 2 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

And if you look at the way the changes a made, you can even try yourself to test, debug and solve problems. After changing a file you can restart pimatic.
If you are using a test system, you can stop the daemon (sudo service pimatic stop) and run pimatic via a terminal window/commandline in the pimatic directory.
The command is: sudo node_module/pimatic/pimatic.js
In the commandline you can see directly if there are errors, debug/repair the problem and start-over. Its a faster cycle

UPDATE: added action.coffee as 3 file to be updated

Hi @bertreb, the stick arrived meanwhile, but my personal agenda is that full currently, the I will by able to continue here earliest next week.
Just for your info …

Hi @bertreb,
got the test environment running, the shutter-switch learned to the ConBee stick via Phoscon and did the file-exchange you explained.
But it didn’t work. Error in log says:

23:20:23.816 [pimatic] info: Loading plugin: "pimatic-raspbee" (0.1.7)
coffee-cache: compiling coffee-script file "raspbee.coffee"...23:20:24.023 [pimatic] error: missing / (unclosed regex)

You mentioned that I might start to search for the problems myself, but…
The files you provided are that large > 200kB and > 700kB, that I do not have a clue at all where to start searching and for what

However you might have an idea on the error message?

Afterwards I took the original files again and tested on that basis:
Discovering worked, added the device as a RaspBeeDimmer, but then trying to add it to the frontend caused the following mistake:

23:34:08.644 [pimatic] info: New device "Window Device 2"...
23:34:21.194 [pimatic-mobile-frontend] error: Client error: Cannot read property '__ko__1604613535592' of null

Enough for today, looking forward for next tests …

Edit: Forgot to mention that I tested the shutter switch via the deCONZ gui and from there it worked.

I forgot, you also need to update the file action.coffee.

@bertreb said in ZigBee Shutter Control not working - missing RaspBee Shutter Device:

action.coffee.

I added now also ‘action-coffee’ but the result stays the same:

17:41:11.416 [pimatic] info: Loading plugin: "pimatic-raspbee" (0.1.7)
coffee-cache: compiling coffee-script file "raspbee.coffee"...17:41:11.599 [pimatic] error: missing / (unclosed regex)

Doing a device scan looks like, as the stick isn’t connected in general any longer, as it also doesn’t discover the e. g. raspbee daylight device.

How I copied:

• downloaded on my PC and then simply drag-and-drop to the Raspi ‘Filemanager’ in the Raspbian WEB GUI
• afterwards spent a ‘sudo chmod +x’ and a ‘sudo chmod 777’ for each file via console

With respect to the logging I didn’t find an additional log in the /node_modules/pimatic-raspbee directory, allthough I enabled logging in the settings of the raspbee plugin. Should I have found there one in addition to the general Pimatic log?

The file daemon.log is logging all the debug info, but the error looks in the compile of the coffee script file. Can you post/sent your raspbee.coffee?
One way to do this.
Go to github (bertreb/pimatic-raspbee) and click on the raspbee.coffee file
Click on edit, delete the content and paste your raspbee.coffee.
Save it. It is seen as a pull request and that way i can inspect the file.

@bertreb said in ZigBee Shutter Control not working - missing RaspBee Shutter Device:

the compile of the coffee script file

You mean the one I first downloaded and then used for testing right?

Edit: Just opened Github and realized, that I might wrongly have downloaded ‘action-coffee’ from Trebans repository, let me first check this …

Its the raspbee.coffee file
You can download my pimatic-raspbee repos in a zip file and use the files from there

Hi @bertreb, hope you’re doing well
After all that testings I was a bit clueless how to proceed in general with the remaining problem.

I now just found a bit time to spend some more investigation on the device and found two additonal threads on Github which might contain someting which could help:

https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3269
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3438

In both is a lot of info in. You may read, if there is something which might help us also.
Kind regards
Pedder

Thanks, i’m doing well
The pimatic-raspbee part is not complex and depending on the deconz working and sending the right info and handling the commands.
It looks like the issue is not solved. If a deconz update/solution is available, you could test it directly on deconz. After that we can finish the plugin change.

Ok, I feared that, as the folks on Github seems sticking in the same …, let‘s wait then another while …
In parallel I will continue with my improvements of my motioneye setup and if that runs sufficient, I will start to dig into MQTT, as meanwhile my first Shelly arrived. Maybe by this, the usage of the ZigBee shutter switch might become obsolete… 😉
However, there are ever 1000 things to spend one‘s time for, days really could have 48h sometimes 😄

Hi @bertreb, being again on GitHub with regard to some motionEye issues, I remembered, that I accidentally set up an own fork of Pimatic-raspbee.
I would like to delete this, not to irritate others, but I can not find how to do this. Could you give me a tip how that works?

Hi, go to your fork repos, click on settings and scroll to the bottom (danger area)

Thanks, it worked!
I was on that page but, however didn’t scroll down. Maybe as on my monitor that commenting field ends quiet well in the bottom of my monitor and thus didn’t realize, that there is something below