SOLVED - Xiaomi Gateway not recognized anymore

Xiaomi, Ikea TRÅDFRI, Philips Hue and more.

Moderator: leecollings

Post Reply
melgi
Posts: 23
Joined: Tuesday 15 August 2017 15:50
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

SOLVED - Xiaomi Gateway not recognized anymore

Post by melgi »

I have an issue with my Domoticz installation.

Domoticz ran perfectly on my NAS for years, until I upgraded to the recent Beta after the 2020.1 release. From then on Domoticz didn't work anymore.

So I tried to go back to an earlier version and reinstall my database from a backup. I'm now running version v4.11786 on my Asustor 6210T NAS.

Everything seems to work fine, except my Xiaomi Gateway and my Harmony Hub. I deleted my Xiami Gateway and recreated a new device in hardware. In the log I find this strange message that looks like it doesn't find my Xiaomi as it's missing the last digit of the ip address.

2020-04-07 09:08:12.844 Status: XiaomiGateway (ID=17): Delaying worker startup...
2020-04-07 09:08:17.844 Status: XiaomiGateway (ID=17): Selected as main Gateway
2020-04-07 09:08:17.844 Status: XiaomiGateway (ID=17): Worker started...
2020-04-07 09:08:17.845 Status: XiaomiGateway (ID=17): XiaomiGateway IP address starts with: 111.111.1.
2020-04-07 09:08:34.908 Status: New sensors allowed for 5 minutes...

As you can see, the fourth digit is missing. The IP address of my Xiaomi Gateway is fixed to 111.111.1.175

Does anybody have an idea how I can correct this?

Regards,

melgi
Last edited by melgi on Tuesday 26 May 2020 17:29, edited 1 time in total.
rrozema
Posts: 470
Joined: Thursday 26 October 2017 13:37
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Delft
Contact:

Re: Xiaomi Gateway not recognized anymore

Post by rrozema »

You know you can't just pick any ip address range for your local devices, do you? Only a few specific ranges are reserved for private address ranges and 111.111.1.x isn't one of them. So unless you've got your own range of public ip addresses -which is highly unlikely- you've probably not set your local network up correctly. This can cause strange problems like incorrect routing.

Better reconfigure your router to use on the LAN side addresses in a range starting with 192.168. and then make sure you restart all devices in your network to get a new address from the router's dhcp. I am not sure that this will fix your gateway problem, but at least it does eliminate one potential issue.
melgi
Posts: 23
Joined: Tuesday 15 August 2017 15:50
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Re: Xiaomi Gateway not recognized anymore

Post by melgi »

@rrozema,

Thanx for your reaction!

I put the ip address as a place holder (111.111.1.x), as I didn't know if it was custom to put ip address here in this forum. MY BAD! But the ip address of the gateway is 192.168.1.175. I have the ip address bined to a fix ip address through the mac address. Everything worked perfectly in previous domoticz builds, before I upgraded to version 2020.x.

At the moment I reverted back to version 4.11786 available for my ASUSTOR Nas (based on Docker). In the ASUStor forum Philippe (father.mande) is trying to create a new build for the ASUStor devices. I hope that helps solve my problem.

I thought maybe others also have the same issue using a Xiaomi Gateway, as I read that quite some people have all sorts of issues after upgrading to v2020.x. But looking at the reactions on my post, I'm the only one with this specific issue I guess. I'll wait for a new build for my NAS and keep my fingers crossed that solves my problem.
rrozema wrote: Tuesday 28 April 2020 23:38 You know you can't just pick any ip address range for your local devices, do you? Only a few specific ranges are reserved for private address ranges and 111.111.1.x isn't one of them. So unless you've got your own range of public ip addresses -which is highly unlikely- you've probably not set your local network up correctly. This can cause strange problems like incorrect routing.

Better reconfigure your router to use on the LAN side addresses in a range starting with 192.168. and then make sure you restart all devices in your network to get a new address from the router's dhcp. I am not sure that this will fix your gateway problem, but at least it does eliminate one potential issue.
rrozema
Posts: 470
Joined: Thursday 26 October 2017 13:37
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Delft
Contact:

Re: Xiaomi Gateway not recognized anymore

Post by rrozema »

haha, you're right to be cautious not posting to much (personal) details. I personally don't think the internal ip range is really that sensitive though. 192.168.1 is indeed a good private address range. Offtopic, I've had the problem that 192.168.1.x was used by a vpn network i connected to, which clashed with my local network range, so this is why I since then use 192.168.128.x.

I don't have any experience with xiaomi gateway integration, so I hope someone else will indeed be able to resolve that problem. Keep us informed!
melgi
Posts: 23
Joined: Tuesday 15 August 2017 15:50
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Re: Xiaomi Gateway not recognized anymore

Post by melgi »

Yes! My issue has been resolved with the new Domoticz APKG for Asustor! See here: https://www.domoticz.com/forum/viewtopi ... 80#p248780.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest