Closed youlib closed 4 years ago
More info regarding getting an API key. I am attaching my postman request, plus the unlocked status from the gui, while I make the request:
I had a similar issue the other day with my raspberry pi 4. I had missed step 1 in the installation guide https://phoscon.de/en/raspbee/install
Would you like the serial port hardware to be enabled? → Yes
After doing this and a reboot deconz was able to connect to the device.
Thanks for the reply, LeroyShirto, but if I'm non mistaken this step refers to rasbian, I have a hassio
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Were you able to fix this? I'm having the same issue.
same for me. How to fix this?
Hi, I have a pi 4 with a hassio installed, together with a RaspBee. The board is on the pi, and if I check under system->hardware, I see "serial: /dev/ttyAMA0. ". deCONZ plugin is installed, and started. "discovery" is on my yaml, and under integrations the device shows up. If I go to the Phoscon page and do discovery, my philips hue light is not discovered. Under gateway, firmware shows as "Not connected". I have not managed to do anything regarding the API key, and I cannot understand how to address this. If I visit the integrations hassio page, I cannot trigger the API key call, in any way. HassOS 3.4 What am I missing?