I have an issue with running mqtt in parallel with deconz. Deconz is running fine and the moment i install mosquito mqtt and reboot the RPI (running only hassos on rpi4) deconz stops working. Obviously there is some conflict, but cant figure out. If I disable mqtt addon and reboot, everything is fine. This is obviously some easy fix, but can’t figure out… Appreciate any help on the topic
Integration: deCONZ (documentation, issues)
First occurred: 11:27:05 (6 occurrences)
Last logged: 11:29:58
Error connecting to deCONZ gateway at 172.30.33.0
Hi, does mqtt run when you disable deCONZ?
Just a wild guess: your system is not out of RAM?
Yes. It runs. But - look at this. My IP in phoscon has different IP when I run mqtt and do a reboot. Can I somehow change this?
Are you using docker?
It seems that these ?containers? have dynamic addresses or/and maybe you have an address conflict between mqtt & deCONZ.
You have to look in the direction of those IP addresses.
If you’re using HAOS, then these add-ons are each installed in their separate container (docker).
I’m not familiar with it in detail but these containers have their own IP address which are handed out dynamically (DHCP), which might explain why the address changes when run MQTT - or not.
Check your MQTT configuration and be aware that you have 2 MQTT ‘modules’:
- the broker add-on, which is the server part
- the MQTT integration, which is ‘the glue’ between your HA and the broker