Update:
The reason for the double Hue Config, is me using the Hassio-Addon AND copying the conbee-files to the addon-folder. After deleting the files I added myself, the “conbee” -folder appeared without me having access. And the double Hue config is gone : )
The app on this url will scan for deCONZ gateways in the local network and connect you to the more modern interface Dresden is developing. Also see the Phoscon app documentation
The Hassio-deconz Addon is running. And there is no option for setting ports. Here is the code for deconz.
The Hassio embedded MQTT broker uses default Port 1883.
The Hassio log is till showing errors.
018-01-23 19:08:02 ERROR (MainThread) [homeassistant.config] Invalid config for [mqtt]: [Port] is an invalid option for [mqtt]. Check: mqtt->mqtt->Port. (See /config/configuration.yaml, line 97). Please check the docs at MQTT - Home Assistant
2018-01-23 19:08:02 ERROR (MainThread) [homeassistant.setup] Setup failed for mqtt: Invalid config.
2018-01-23 19:22:41 WARNING (MainThread) [homeassistant.core] Unable to find service mqtt/publish
2018-01-23 19:22:51 WARNING (MainThread) [homeassistant.core] Unable to find service mqtt/publish
I could use another MQTT broker. But the initial error remains. A conflict between the embedded MQTT and the Addon. As far I can tell.
I have got a api_key in my Hassio deconz.conf file:
“api_key”: “943567HH98”,
“host”: “192.168.0.25”, (PC/Windows 10)
“port”: 80
I have tried with and without “deconz:…” in my Hassio configuration-file (with also “discovery:”).
I am running deConz on Windows 10. Have stopped the firewall. And I am not getting the deConz software to get connected to my RSPI3/Hassio.
I have added some Osram Ligthify bulbs to the local http://hassio.local:80 -deConz interface. I am able to control the bulbs. But I am not getting any sensors in Hassio.
Not sure what was solved here, but please assist me by pointing to a solution? Ive got the Conbee attached to my Pi3 Hassio install and nothing happens? Discovery does nothing, nor can I add the new Integration, because it doesn’t recognize the usb dongle…