homebridge-miio
homebridge-miio copied to clipboard
Bluebie
plugin conflict
@Bluebie @aholstenson After updating this plugin homebridge-mi-aqara plugin has few issues. Following are not responding:
- Zigbee plugs
- Gateway light https://github.com/YinHangCode/homebridge-mi-aqara/
I did try with v 0.6.0 with 0.3.1, still same issue. I suspect it's miio library issue. I added @aholstenson and I will update author @YinHangCode of homebridge-mi-aqara plugin.
fyi, incase anyone else is searching forum to do revert back. sudo npm -g install [email protected] sudo npm -g install [email protected]
Hi, I think this is related to both plugins using the developer API and getting out of sync. I changed how miio interacts with the gateway but had not yet released it.
I took some time just now to do a release. In 0.13.0 the gateway should no longer use the developer API for more than receiving events. Hopefully that means that the other libraries using the developer API no longer get confused.
@aholstenson thanks for the explanation. i updated to miio library 0.13.0 but i still couldn't get it to work. Ok, I did get it to work intermittently once which is strange.
-- when i ran miio --discover --sync i got following for one of the zigbee plugs
Device ID: 158d00015dc113 Model info: lumi.motion (motion) Address: Owned by 52051385 Token: Automatic via parent device Support: At least basic
-- traced it back to log in homebridge:
[XiaomiMiio] device discovered 52051385 Investigating Miio Device at udp://192.168.1.10:54321
fyi, i noticed following but it shouldn't be an issue related to above: Loaded plugin: homebridge-miio [7/9/2017, 7:24:13 PM] Registering platform 'homebridge-miio.XiaomiMiio' [7/9/2017, 7:24:13 PM] --- failed to load BLE module!
were there any issues @astrojetson8 ? i'll push a revised version of homebridge-miio if not
no, it's been running fine since yesterday. i'll test the updated version when its up, and report back.
fyi: i was bit perplexed why it worked intermittently as per my original post. however, after gateway restart it worked fine. i could duplicate this multiple times. to get it work i had to restart the gateway.