Maybe an idea could be that somebody try these sensors with another gateway such as RaspBee since these are Zigbee right ?
Jep! Take a look here: http://faire-ca-soi-meme.fr/news/2017/07/06/edito-avancement-de-passerelle-zigate/
yes but why wait, it’s already developed by dresden elektronik 50€ USB and 35€ for raspberry pi module, they have a REST protocol, also by going this way if you have multiple gateways you can reduce that to one (that beeing said if all are Zigbee), they support IKEA, Philips, Osram and i think also Xiaomi. I just ordered an RaspBee module so i can replace my hue and ikea gateway.
see here :
Can you confirm it works for Xiaomi?
My xiaomi home gateway has access to internet
I doubt the xiaomi profile is supported. Xiaomi is using “zigbee pro”.
check this https://www.dresden-elektronik.de/funktechnik/solutions/wireless-light-control/raspbee/?L=1&cHash=c9c902ccdb43164696acccf81b62b2bd
Brings ZigBee connectivity to Raspberry Pi. The shield allows direct communication with ZigBee PRO devices like Philips Hue, XBee Series 2 and others.
+1 I’m curious too. (just ordered my second Xiaomi gateway ^^)
@syssi well it seems pretty clear to me that it works on at least those two devices in the link i gave you were somebody has confirmed it working.
The issue on github looks very promising.
I didn’t mention that the motion sensor was stuck on ON since more than a day. Restarting HA didn’t help.
To reset the motion sensor I had to unplug the battery from the sensor.
I also have those dresdensrick but never attached it to the pi or even tried to integrate it in Hass. If someone here has a working setup … would be nice if u would share this
You don’t need, just walk/move in front of it and after 2 minutes it goes back to normal because it sends the “no movement” status back to HA.
Did you get your sensors fixed or find out what the issue was?
I have the same motion sensor bug since i switched to this repo, i will debug further when it appears again.
I am using the dev repo. And hass could not discover my xiaomi gateway.
2017-07-25 08:44:21 WARNING (MainThread) [homeassistant.components.updater] Running on ‘dev’, only analytics will be submitted
2017-07-25 08:44:30 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
2017-07-25 08:44:32 WARNING (MainThread) [homeassistant.setup] Setup of xiaomi is taking over 10 seconds.
2017-07-25 08:44:37 ERROR (SyncWorker_5) [homeassistant.components.xiaomi] No gateway discovered
2017-07-25 08:44:37 ERROR (MainThread) [homeassistant.setup] Setup failed for xiaomi: Component failed to initialize.
After 3 hours struggling, installed openHAB2. The gateway was found instantly.
Hass is installed in synology docker, openHAB is installed as synology package. Found someone fixed discover issue by using a different router, but openHAB can find it easily. So I think there must be a way to fix it without a new router.
Can anyone help?
I assume the difference of the both setups is the docker environment. If you are able to start HA in an python-virtualenv the discovery will succeed, too.
I checked there code. https://github.com/octa22/org.openhab.binding.xiaomigateway/blob/master/src/main/java/org/openhab/binding/xiaomigateway/internal/XiaomiGatewayBinding.java#L964
They are only discovering the gateway if the sid or key is not provided.
It would be possible to add that to HA too. If someone is interested to do so, a pull request to https://github.com/Danielhiversen/PyXiaomiGateway is welcome.
I think skipping the discovery does not improve the situation. People without a proper discovery will fail a step later: The discovery of devices / reception of sensor events.