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 …
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 …
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