nice that it works now.
the git readme already contains a link to the wiki.
Since only a new package version updates the pimatic plugins page, this is unfortunately missing there.
i will release a new version soon.
(with new readme)
Howto do a Raspee (Conbee II) installation?
nice that it works now.
the git readme already contains a link to the wiki.
Since only a new package version updates the pimatic plugins page, this is unfortunately missing there.
i will release a new version soon.
(with new readme)
@pedder said in Howto do a Raspee (Conbee II) installation?:
But that may take some additional days as I’m now struggling to learn my OSRAM Plugs to the Phoscon App ….
I ran the scan now 5-6 times, while switching the plugs on and off, but they are not registered
Strange, never had issues while pairing a osram smart+ plug. Even in daily use they are very stable and working without any problems within my system.
… well that is really frustrating here.
I started my Test pimatic an hour ago, which worked properly yesterday evening, but pimatic wasn’t able to reconnect to the stick any longer. I got error messages every 30 seconds:
error [pimatic-raspbee]: Connection could not be establised
error [pimatic-raspbee]: websocket keep alive error, try to reconnect
And the stick also wasn’t available via the phoscon WEB GUI any longer.
… reconfigured the plugin, tried another port, reinstalled the plugin, but nothing helps.
I then plugged the stick to my two Computers (Win7/10) and, … both responded that the just plugged in USB device has a problem … … which might also be the reason that I wasn’t able to bind my OSRAM plug to it yesterday.
So, it seems to be, that I’m the lucky one , who got 1 out of 1000 which has a problem in general and I will send it back …
… and additionally, the new stick will be send earliest on 23 of July
Isn’t that frustrating?
i had to send my conbee II back, too and the new one shall be there till friday. couldn’t connect to it anymore, even after firmware update and setting up the pi completely from scratch. but that gave me some time to get to know the deconz docker image - so the setup step isn’t required anymore.
Hmhm, I hope that they do not break too often …
Hi again
I was happy that now, against the former announcements, my new ConBee II stick has been delivered yesterday.
Today I directly took a fresh Test Image an started the installation.
Everything went very well, using @kosta’s install guide from github
But after doing a rebooted I ran into the problem, that deconz seems not to be started automatically and so pimatic comes up with a websocket reconnection error.
I found, that I have always to start the deconz service manually by:
sudo systemctl start deconz
what for sure is not needful, e. g. in terms of a power outage…
So my question today: How can I get deconz also beeing started automatically after a reboot?
Is that similiar like I did already for autostarting pimatic, as it is explained in the wiki?
wget https://raw.githubusercontent.com/pimatic/pimatic/v0.9.x/install/pimatic-init-d
sudo cp pimatic-init-d /etc/init.d/pimatic
sudo chmod +x /etc/init.d/pimatic
sudo chown root:root /etc/init.d/pimatic
sudo update-rc.d pimatic defaults
… or maybe as another solution, as I have installed the shell execute plugin, to execute the above mentioned command only once after a pimatic start - currently have no clue how to do that, as I fear, that it would be executed again and again …
@pedder said in Howto do a Raspee (Conbee II) installation?:
installed the shell execute plugin, to execute the above mentioned command only once after a pimatic start -
Ok, that works for the moment:
WHEN ‘pimatic is starting’ THEN ‘after 5 seconds execute “sudo systemctl start deconz”’
It creats 1-2 errors in the starting phases, but it works
Other solutions are welcome in addition
Hi @kosta,
thanks for the additional hint.
Freshly back from vacations, I will check that the next days …
Best way to install deconz is:
https://hub.docker.com/r/marthoc/deconz
Here is my current docker-compose.yml:
version: "2"
services:
deconz:
image: marthoc/deconz
container_name: deconz
network_mode: host
ports:
- "8090:8090"
- "8443:8443"
restart: always
command: --upnp 0
volumes:
- ./localconfig:/root/.local/share/dresden-elektronik/deCONZ
- /dev/ttyUSB0:/dev/ttyAMA0
devices:
- /dev/deconz
- /dev/ttyUSB1
- /dev/ttyUSB0
environment:
- DECONZ_WEB_PORT=8090
- DECONZ_WS_PORT=8443
- DEBUG_INFO=1
- DECONZ_DEVICE=/dev/deconz
- DEBUG_APS=0
- DEBUG_ZCL=0
- DEBUG_ZDP=0
- DEBUG_OTAU=0
- DECONZ_UPNP=0
The Deconz Device is hard-linkt via udev rule in /etc/udev/rules.d/10-local.rules
ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", SYMLINK+="deconz"
Hope you have fun with this!