Has anyone updated the gateway to the latest version 1.4.1_151.0143?
I did few weeks ago - all is working fine
Patrik,
Are you using the raspberry as the wifi hotspot for the gateway?
That’s where my problems came from. In my setup with raspberry hotspot one gateway would initialize ok, all sensor values refreshed once, then no more heartbeats and no refresh, also updates don’t work. My second gateway would not initialize at all.
Now with a separate router it works ok but not perfectly, rapid updates sometimes get lost.
.
Hi,
I have connected the Gateway with my fritzBox 7490. i dont use the wlan from the pi. The pi is connected per lan with the fritzBox too.
Hi. I am update Xiaomi gateway to lastest version.
I had some problems getting the binding to auto-discover the gateway (1.4.1_151.0143, btw) - turned out, the Wifi was in powersaving mode! after changing that to off, it works now. Perhaps, that was one part in your setup?
So, running the mihome binding on a wifi connected OH2, be sure, powersaving is off.
I’m still getting some delays between updates (temperature/pressure/humidity sensor), but I’m fine with it.
I have OpenHAB2 Snapshot release. Connect Mi Smoke Sensor (Xiaomi Mijia Honeywell Fire Alarm Detector) over Mi Home Gateway v3. Smoke Sensor have some properties - status and % of charge. Current status is unknow and % of charge is NaN. It’s normally?
i discovered, that the Smoke Detector is one of the trickier ones. Perhaps to save battery, its only sending updates to the Gateway in hour long intervals. You have to be lucky to get an answer just after reloading the items file. Just let OH2 run for a couple hours and then sometime there should be some info from the smoke sensor.
I don’t think, the Gateway persists Information, but only transports live data from the sensors. In the App you get persisted data from the cloud.
Thank you, Thomas. I’ll wait a while.
—or just blow some smoke to it and see what happens! ![]()
Ок, I’ll make a little fire. ![]()
i got a problem, the binding suddenly not work these days.
i checked the trace log, every time i restart the openhab, after several minutes,
the binding will no more sync with token
[home.handler.XiaomiDeviceBaseHandler] - Item got update: {“cmd”:“heartbeat”,“model”:“gateway”,“sid”:“f0b429cc6c98”,“short_id”:“0”,“token”:“h3jWcYRmS76T70Z7”,“data”:“{"ip":"192.168.1.3"}”}
No more the above message
then the binding will not work any more
and i found out it’s my .items or .things file problem.
guess it may be the curtain thing & item throw exception and stopped the thread socket.
I will check and report later
Hi,
to be honest I have no idea what is supposed to work or not. I had the issue that my button stopped working after an update of OH and I found the new rules on the net and they worked for me. I am sorry I can’t help you out on this.
Sven
is your openHAB connected via Wifi or LAN? if it’s Wifi-connected, you must turn off power_save mode. otherwise, the OH2-socket won’t stay connected with the gateway.
HI,
Anyone with xiaomi plug zigbee device problem?
I’ve installes OH1 with xiaomigateway-1.11.0-SNAPSHOT.jar release all works fine but i cant read the load_power consumption.
The log file continuoly show:
2017-12-27 23:09:15.757 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "14.09"
2017-12-27 23:10:15.762 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "13.67"
2017-12-27 23:11:15.765 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "12.56"
2017-12-27 23:12:15.920 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "16.03"
2017-12-27 23:13:15.761 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "13.28"
2017-12-27 23:14:15.770 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "16.60"
2017-12-27 23:14:30.760 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "14.09"
2017-12-27 23:15:15.758 [ERROR] [o.o.b.x.i.XiaomiGatewayBinding] - java.lang.NumberFormatException: For input string: "14.53"
This values are the current power.
The gateway current version is the 1.4.1_151.0143.
Item file:
/* XIAOMI PLUG*/
Switch XiaomiPlugInUse "Xiaomi Enchufe" { xiaomigateway="158d000xxxxxxx.inuse" }
Switch XiaomiPlug "Xiaomi Lavadora" { xiaomigateway="158d000xxxxxxx.plug" }
Number XiaomiPlugConsumed "Xiaomi zigbee plug consumed [%.0f kWh]" { xiaomigateway="158d000xxxxxx.power_consumed" }
Number XiaomiPlugLoad "Xiaomi zigbee plug load [%.0f W]" { xiaomigateway="158d0000xxxxxx.load_power" }
And the sitemap file:
Frame label="Lavadora" {
Text item=XiaomiPlugInUse {
Frame {
Switch item=XiaomiPlugInUse
Switch item=XiaomiPlug
Text item=XiaomiPlugConsumed
Text item=XiaomiPlugLoad
}
}
}
Any ideas?
Thx
I found out the Curtain item has a event , which will cause the whole binding stop working.
Sometimes the curtain motor will report the value “-1”, i have to reset the curtain myself,
Item got update: {“cmd”:“read_ack”,“model”:“curtain”,“sid”:“158d00012d69e7”,“short_id”:56211,“data”:“{"voltage":3600,"curtain_level":"-1"}”}
Though the value range is 0-100, but sometimes when the curtain motor stuck, it will send -1
the -1 will crash the whole binding.
Please check.
Thanks.
Hi @binderth,
How do you check if openHAB power_save mode is On or Off. Cheers
If it’s a Linux System: iw wlan0 get power_save, it should then return if it’s on or off (If your Wifi is wlan0)
[14:23:43] openhabian@openHAB2:~$ iw wlan0 get power_save
Power save: off
to disable it, type sudo iw wlan0 set power_save off - but as that’s only temporarily until the next reboot, you should make it permanent. I didn’t found out how to do this in raspbian stretch (as you shouldn’t touch /etc/network/interfaces), so I just added the iw wlan0 set power_save OFF to my /etc/rc.local.
Hi everyone
I’ll jump onto this topic, as there seem to be several problems with the mi home binding after upgrading to 2.2.
I have an interesting problem as well: I have a few window/door sensors from xiaomi and a motion sensor.
Ever since upgrading to 2.2 the following happens:
- all sensors (including motion sensor) show up as status “online” in Paper UI
- same for the gateway (interestingly, two gateways show up as things (“XIaomi Gateway” and “Xiaomi Smart Home Gateway”), although physically I only have one (but that was always the case, even before upgrading to 2.2)
- If I trigger one of the sensors, it shows up in the Mi Home app as an event (i.e. open/close for door/window and movement detected for the motion sensor)
- now it gets interestiing: In OH2, the motion sensor and the rule(s) associated with it work fine.
- However, the door/window sensor status does not update. There is no event in the event log, and no other log entries in OpenHAB log, even though I set the log level to debug (log:set DEBUG org.eclipse.binding.mihome)
Gateway is on the latest version 1.4.1_151.0143
Anyone have any ideas what this could be (or how I even find out more information)
Thx
Hi Patrick,
do you configure everything (including items) with PaperUI? if not, please post your Things-file and/or your items-file
But please post your rules.
and lastly: your Pi is on LAN or on Wifi?