I was able to get the 2.05.00 installed, but at this step of the install
cd deconz-rest-plugin
git checkout -b mybranch V2_04_99
I to changed it to
git checkout -b mybranch V2_05_00
I got this error:
pi@raspberrypi:~/deconz-rest-plugin $ git checkout -b mybranch V2_05_00
fatal: Cannot update paths and switch to branch 'mybranch' at the same time.
Did you intend to checkout 'V2_05_00' which can not be resolved as commit?
pi@raspberrypi:~/deconz-rest-plugin $
So I used 2.04.99 per the site. It went, but I know it’s wrong.
Don’t worry about the second part of the install, that’s only if you want to test the latest commits to the master branch. Not really a production-worthy practice in my view.
All you need to do is: sudo dpkg -i deconz-2.05.00-qt5.deb sudo apt-get install -f
That will install the deb and correct the missing dependencies.
No I’m not sure what if anything changed in the deCONZ core application, there appear to have been a number of additions to the rest plug-in though, going by the git commit history of the master branch.
The web interface at port 80 is the old webapp, Phoscon is the new interface currently in beta. As far as I can tell the difference is mostly cosmetic, but Phoscon may be missing a few features (resetting lights via TouchLink is one I can think of). I prefer using Phoscon as it seemed to be easier to get ie Motion sensors paired. If something isn’t showing up in HA, then I’d suggest to restart deconz (sometimes necessary to get new devices to flow through the rest API) and then Home Assistant. When HA connects to deconz it should pull all of your devices. Be sure to rename the devices in deconz as that name will carry into HA.
For the Dimmer, you should see a battery level entity in HA. Button presses are sent as events in HA, check the HA deconz component docs for example automations using them as triggers.
deCONZ will automatically create groups when you add a device like a switch or sensor - you can then add lights to that group and the switch will control them automatically. I leave the groups empty myself so that I can let HA do the processing of button presses and motion events.
Use Phoscon to delete the motion sensor device, then create it again through Phoscon. Another thing I found was that I needed to give the sensor a hard reset at some point (ie take out the batteries and wait a minute or so).
Both the Wireless Light Control webapp and Phoscon do the same thing - add devices to deCONZ. Phoscon is easier imo as it has the menus that walk you through.
Agreed with @Robban though - if it’s not showing up in HA then it probably didn’t add to deCONZ correctly.
Don’t worry about the other webapp. Mine doesn’t show there either. This is probably a question for @Robban to troubleshoot on (he’s the dev of the deconz HA component).
Here’s tests you can do to give @Robban a head start.
Using a rest API client like Postman, try to do a GET on http://yourdeconzip/api/apikey/sensors. Where apikey found in deconz.conf in your config directory. That will return a json object and your sensor should be listed in there. If it is, @Robban will probably want to take a look at the json payload.
My point is it won’t show in the other webapp. There’s a reason Dresden Elektronik is making and pushing the new Phoscon webapp - it’s going to be better and eventually replace the existing one.
