Hi @kosta, I while ago here
I just was able now to do all updates Phoscon -> 2.05.82, ConBee II firmeware -> 26650700 and last but not least also the raspbee plugin -> 0.1.7
Everything runs fine, but I’m still not able to use the above mentioned shutter steering device.
Besides the PhosconApp shows it as a light, allthough using the discovery routine for a switch, in the deconz gui it is shown correctly and also can be steerd via the gui correctly, in minimum up/down/stop.
As it works fine that way, shouldn’t it be possible to integrate it, or maybe in general a shutter device, in the list of the raspbee devices in Pimatic?
I’m not that deep in these details, but I’m wondering that everything else is availabel there (sensors, dimmers, lights, switches, etc.) but no shutter device.
-
ZigBee Shutter Control not working - missing RaspBee Shutter Device
-
So, I also upgraded my deconz conbee2 and am using this.
I would love to support if i can help somehow to support this device?! -
@kosta
if it helps I would be able to send you one of the shutter controllers, I bought one more -
@Pedder, I made a some adjustments to pimatic-raspbee to support a shutter. Its a fork of the pimatic-raspbee.
I can’t test it, so if you are able to install and test it, i can help to get it working.
This version uses a RaspbeeDimmer as shutter controller. But as i said i didn’t test itI assume in time @kosta will add the Shutter functionality to his plugin.
-
Hi @bertreb, thanks for taking care
I just checked Github, found your fork, but couldn’t find an additional new raspbee ‘version’ there.
If you added something there, could you provide a direct link to a file or something like such?Besides that, with regard of testing an inoffical raspbee version, I would not do that on my productive system.
Meanwhile the trouble of a respective crash would become to large here in my local user ‘community’Thus I will order now a secound ConBee2 stick, which I anyhow planed to have it as spare at home.
As soon as I have it available here, we can start to test. A test Raspi/Pimatic is anyhow already availabe.Regards
Pedder -
I have a little conversation in the deconz github repository. It seems for it to work they will have to do a extra implementation based on the manufacturer name that has to be read with the deconz gui.
I will try to help there, but my system is headless at the moment, I will try to go on there in the next days, so maybe there will be some progress, too.https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3438
-
In Deconz (GUI) the device (SM-SW101-ZC) is already working. I was able to test that and see that up/stop/down in minimum works in both directions, so steering from deconz and also by the device’s buttons.
I provided all the necessary screenshoots myself on Github to get that done, a couple of months ago.Now still the integration in Pimatic/raspbee is missing.
-
@pedder said in ZigBee Shutter Control not working - missing RaspBee Shutter Device:
In Deconz (GUI) the device (SM-SW101-ZC) is already working. I was able to test that and see that up/stop/down in minimum works in both directions, so steering from deconz and also by the device’s buttons.
I provided all the necessary screenshoots myself on Github to get that done, a couple of months ago.Now still the integration in Pimatic/raspbee is missing.
Ok thats funny, I have the same switch (at least by the model number) and it doesnt work on the newest deconz + firmware.
-
@pedder said in ZigBee Shutter Control not working - missing RaspBee Shutter Device:
Hi @bertreb, thanks for taking care
I just checked Github, found your fork, but couldn’t find an additional new raspbee ‘version’ there.
If you added something there, could you provide a direct link to a file or something like such?Besides that, with regard of testing an inoffical raspbee version, I would not do that on my productive system.
Meanwhile the trouble of a respective crash would become to large here in my local user ‘community’Thus I will order now a secound ConBee2 stick, which I anyhow planed to have it as spare at home.
As soon as I have it available here, we can start to test. A test Raspi/Pimatic is anyhow already availabe.Regards
PedderYou are right i didn’t push it yet to github, but its now there.
-
@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 …
-
Using a second Conbee stick for testing is a good idea.
The pimatic-raspbee plugin is using the official deconz api and as far as i can see you can not ruin the Deconz/Conbee setup. Its just using the in Deconz configured devices.But there are still some things to solve like:
- supported functions: open, close, tilt, etc
- pimatic gui
The first version i made is detecting a deconz “Window covering device” or “Window covering controller” and uses the dimmer for shutter position and open/close for that function.
-
Oh, just FYI: They currently sell the Osram Smart+ Plugs in a package of 4 for ~40€, which is a super price
-
@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 cycleUPDATE: 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 whatHowever 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.
-
@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 …