thanks! this worked also for me. I could not type in the thing configuration window, so I included one extra line in the code in the configuration section, now it looks like:
Thanks a lot for the hint but it’s still going offline after exactly 5 minutes in my case… Do you know if there is still work being done on the binding to find the root cause?
Sorry, I don’t know if anybody is working on the binding. In fact, in OH2 it was also needed to have the MAC in the Thing definition. Just for reference, find the complete Code, maybe it helps:
UID: mihome:bridge:XiaomiBridge
label: Xiaomi Mi Smart Home Bridge
thingTypeUID: mihome:bridge
configuration:
ipAddress: 192.168.1.61
serialNumber: 286cxxxxxxxx
port: 9898
key: CA5…
Have you tried the workaround I suggested, i.e. backup OH3, remove it, install OH2.5 and then re-install OH3 over the existing 2.5 version?
Also, I know this is not really helpful, but in the meantime I have replaced the Xiaomi Gateway with the DeCONZ gateway and binding - much more stable and besides also replaced two Hue bridges I had…
The DeConz is an entirely new piece of hardware which you have to purchase - and this hardware enables you to use both Hue lights and Xiaomi sensors with just one piece of hardware.
But if you have a Raspi running 2.5, you can install the Xiaomi binding there and then use the remote binding to connect the oh3 installation to the 2.5 installation - that worked well for me too, in the beginning
In the documentation there is following sentences:
At least every 10 seconds you should see a message coming in from the gateway which looks like {"cmd":"heartbeat","model":"gateway","sid":"xxx",“short_id”:“0”,“token”:“xxx”,“data”:"{"ip":"xxx\"}"}
I have tried with OP2.5 and OP3.1.0
On the OP2.5 every 10 seconds I got this line.
On OP3 it comes up only, if I activate the Xiaomi Bridge.
So I believe something with the Server is maybe not working. wrong IP Settings Multicast ect.
Do anyone have an idea. I think there is no heatbeat, and after 5min it will go offline.
But I do not know why the Bridge is not sending the heatbeat to OP3
I already read the link - 87211
But I do not see any helpful ideas
I thought I’d share this. I had the same problem in OH3 with one of the 3 Xiaomi gateways I run (and it was always perfectly visible in OH2).
I had tried the suggestions listed above but finally realized I made the mistake of trying the MAC address as Serial Number, keeping the “:” of the MAC address…
Removing the colons (":") fixed my problem.
I mention it in case someone else would have been doing the same “mistake”… Note that the 2 other gateways are perfectly fine in OH3 without a serial number.
This doesn’t work with me unfortunately.
I’m running OH3.2.0-stable and the bridge goes offline every 5mins.
I can’t put in the serialNumber in the GUI directly, that input field is grey with my installation - I put it in “Code” and then it appears in the Thing-configuration in grey:
I’m back on this topic as it is only partially solved on my end. After some investigation in the past, I’ve realized, that my issue is caused (bridge going offline after 5 min) by the Xiaomi Gateway. The gateway is basically the same device as the bridge, but it is recognized separately by OH and it has channels to control the device itself. I’m using the light on it as a night light in the house, so it’s quite important for me.
The situation is, that if I add the bridge only, then everything is working fine and stable. All connected sensors are also fine. BUT, once I add the gateway thing as well, then everything (the gateway as well) is getting disconnected every 5 mins. I need to re-enable the bridge in OH UI, then everything works for the next 5 mins. Once I remove the gateway thing and re-enable the bridge, then everything is back to normal.
This was working fine for years on OH 2.5, but stopped working from OH 3.0. Can someone give me any hint what to try or how to solve? OR is there any other option to control the light on the device without adding the gateway thing?