Rasbee keep changing its internal IP

Hardware
1

Hi all,

I’ve been using Home Assistant for some weeks now, and so far I am very happy with it, although some performance problems I am having, I imagine due to a rpi3 that is getting old.

In any case, the problem I have that I can not resolve nor find how to do it is that my raspbee ii zigbee module is sometimes changing it’s default internal IP, which messes with the deconz integration.

BTW, I already modified the config.txt and raspbee is technically working fine, I can access the Phoscon/deConz configurations etc.

When configured the first time, the deconz integration was automatically discovered and configured itself. All was working fine, and I could interact with the Ikea Tradfri movement sensor. So far so good.

However, I imagine after some rpi reboots, the raspbee changed its IP, and its no longer 172.30.33.1, but 172.30.33.2, so the integration is showing errors in the log as it is trying to connect to 172.33.30.1… Actually, since yesterday, its 172.30.33.3.

I can delete the integration, and configure it again using the new IP. As the entities are configured inside the deconz addon, it will load all of them again and I think everything is working OK, but i really would like to prevent the raspbee changing its IP, if possible…

Is there somebody that encountered the same problem and has a solution??

Many thanks!!

2

Raspbee II module does not use TCP/IP and therefore has no IP-address. It is accessed using a local device path (/dev/ttyAMA0 by default). You probably run a deconz-service on the RPI that has the Raspbee module on it’s GPIO. And the IP address of that RPI changes.

I think that the RPI’s network is using DHCP and an IP address is assigned to it dynamically from your router. Check the router’s management interface, if you can define the IP address that is given to the RPi.

Or use the internal RPIs hostname in your HA configuration (instead of it’s IP).

Or change the network settings on the RPI to using a static address.

1 Like
3

Well, is not that the raspbee may have an IP, actually it’s not my router range of IPs, as i’m on 192.168.1.1.

But it has an “internal” IP, where the integration is trying to connect.

In fact, setting up the integration, it ask for a HOST and a PORT, which in my case are 172.30.33.3 (at this moment) and 40850…

I really don’t know if this is related to your answer, as I think it is well probablemy far beyond my knowledge…

Thanks!!

4

That’s why people typically connect to other docker containers using the container name, and NOT it’s internal IP address. You should also be able to connect simply using localhost.