Mi Homey

Which app is this?

I tried using both Mi Home and Aqara Home, but getting the (lack of) response from both of them:

Logging in…
Logged in.

No devices found for server “cn”.
No devices found for server “de”.
No devices found for server “us”.
No devices found for server “ru”.
No devices found for server “tw”.
No devices found for server “sg”.
No devices found for server “in”.
No devices found for server “i2”.

Press ENTER to finish

Any good ideas?

Attention: V3 isn’t supported at all. Other gateways can be added using IP and MAC. Pass will be completed automatically. If the gateyway is supported.
Never ever update your gateway; recent software versions are not supported. Downgrades are not (yet?) possible.
If you have an older version, use the modified app below:

I am a little lost here… :frowning:
Unable to add a new child device in to Homey…

I have connected my dgnwg02lm gateway in the past, incl a few child devices. They all continue to work fine.
But how do I add a new switch? It is this one:



(I use it in the basement out of reach from my Homey, so connecting directly to my Homey is no option :frowning:)

Should be supported according to the app and I do see it in the Xiaomi Home app.
But when I try to add a new device with the Mi Home app it keeps saying it didn’t find any new devices.

I’m afraid I am overlooking something very obvious. Restarting the app and Homey didn’t help. Using the last version of the app. Can someone help me out please?

Did you add this device first in the Xiaomi Gateway ?

1 Like

And are you on the max number of end point devices?

Check this approach to deal with max zigbee devices

Yes I did. The gateway had no problems adding it

No, but as I am adding it to the Xiaomi gateway it should count for the max number of Zigbee devices in Homey. The switch will be in the Xiaomi Zigbee network, instead of Homey’s one.

Will support be added for the Smartmi airpurifier P1 and P2?

Mi ClearGlass Air Detector stops working for me.
I can remove and add device again, but there are no values. :frowning:

1 Like

Hi @Eternity,

I am trying to migrate from Homey zigbee to the Xiaomi zigbee. I have added 2 hubs, but have the “No devices found” issue.

I have confirmed both gateways are chinese, port 9898 are open. I added the gateways in the app and can also add the Gateway speaker to Homey, but no other devices.

Any pointer you can give me?

Thanks,
Frank

Hi Frank,

Sorry for the late response.

I am not sure if I can help, other that show what I did.

I installed the App “Mi Homey”, filled in the details (so you need the IP and the token!) and that was it! I did not include the actual Xiaomi bridge, but the devices that were (and remain) connected to the Xiaomi bridge. These devices I added by selecting them as a “Mi Homey” device and selecting the product you are adding (like a temp sensor or door contact)/

@Eternity No problem…

I did the same, but still got the “No devices found” problem…
Can you tell me what firmware version you have on your gateway? Maybe my gateway firmware are too recent.

Gateway 1: 1.4.1_161.0143
Gateway 2: 1.4.1_176.0220

Thanks again!

I have 1.4.1_176. 0220

1 Like

If you don;t have anytime just tell me!!!

frekel@frekel-ThinkPad-T590:~$ miiocli gateway --ip 192.168.1.149 --token [MYTOKEN] discover_devices
Running command discover_devices
INFO:miio.gateway.devices.subdevice:Gateway model 'lumi.gateway.v3' does not (yet) support get_voltage
INFO:miio.gateway.devices.subdevice:Gateway model 'lumi.gateway.v3' does not (yet) support get_voltage
{'lumi.158d000165ff89': <Subdevice Motion: lumi.158d000165ff89, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 3, bat: 60, vol: None, props: {'motion': False}>, 'lumi.158d0001230087': <Subdevice Motion: lumi.158d0001230087, model: RTCGQ01LM, zigbee: lumi.sensor_motion.v2, fw: 11, bat: 60, vol: None, props: {'motion': False}>}

Do you have the same output?

Funny enough I can see devices when querying the gateway from an other machine. Maybe something in my network between Homey and the gateway that blocks some communication…

Running command discover_devices

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

INFO:miio.gateway.devices.subdevice:Gateway model ‘lumi.gateway.v3’ does not (yet) support get_voltage

{‘lumi.158d0001b1cc89’: <Subdevice Motion: lumi.158d0001b1cc89, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 5, bat: 60, vol: None, props: {‘motion’: False}>, ‘lumi.158d0001ad5b0d’: <Subdevice Motion: lumi.158d0001ad5b0d, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 5, bat: 60, vol: None, props: {‘motion’: False}>, ‘lumi.158d0001df05f0’: <Subdevice Motion: lumi.158d0001df05f0, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 5, bat: 60, vol: None, props: {‘motion’: False}>, ‘lumi.158d0001e15ff0’: <Subdevice Motion: lumi.158d0001e15ff0, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 5, bat: 60, vol: None, props: {‘motion’: False}>, ‘lumi.158d0001fa5c85’: <Subdevice SensorHT: lumi.158d0001fa5c85, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d000395cb39’: <Subdevice Switch: lumi.158d000395cb39, model: QBKG12LM, zigbee: lumi.ctrl_ln2.aq1, fw: 1, bat: None, vol: None, props: {‘status_ch0’: None, ‘status_ch1’: None, ‘load_power’: None}>, ‘lumi.158d000396178b’: <Subdevice Switch: lumi.158d000396178b, model: QBKG12LM, zigbee: lumi.ctrl_ln2.aq1, fw: 1, bat: None, vol: None, props: {‘status_ch0’: None, ‘status_ch1’: None, ‘load_power’: None}>, ‘lumi.158d0001ef61a8’: <Subdevice RemoteSwitch: lumi.158d0001ef61a8, model: WXKG11LM 2015, zigbee: lumi.sensor_switch.aq2, fw: 3, bat: 60, vol: None, props: {‘last_press’: ‘none’}>, ‘lumi.158d000405179e’: <Subdevice RemoteSwitch: lumi.158d000405179e, model: WXKG11LM 2018, zigbee: lumi.remote.b1acn01, fw: 2, bat: 60, vol: None, props: {‘last_press’: ‘none’}>, ‘lumi.158d0004460a5b’: <Subdevice SensorHT: lumi.158d0004460a5b, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d0002cb4394’: <Subdevice Motion: lumi.158d0002cb4394, model: RTCGQ11LM, zigbee: lumi.sensor_motion.aq2, fw: 5, bat: 60, vol: None, props: {‘motion’: False}>, ‘lumi.158d00036b50fe’: <Subdevice SensorHT: lumi.158d00036b50fe, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d00036b5754’: <Subdevice SensorHT: lumi.158d00036b5754, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d00023104a9’: <Subdevice SensorHT: lumi.158d00023104a9, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d0001e42f2e’: <Subdevice Magnet: lumi.158d0001e42f2e, model: MCCGQ11LM, zigbee: lumi.sensor_magnet.aq2, fw: 3, bat: 60, vol: None, props: {‘is_open’: False}>, ‘lumi.158d0003214205’: <Subdevice SensorHT: lumi.158d0003214205, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>, ‘lumi.158d0004216c5e’: <Subdevice SensorHT: lumi.158d0004216c5e, model: WSDCGQ11LM, zigbee: lumi.weather.v1, fw: 3, bat: 60, vol: None, props: {‘temperature’: None, ‘humidity’: None, ‘pressure’: None}>}

1 Like

How do I get that info? I have a Mac can can run terminal

sudo pip3 install python-miio

This should do it!

Yep, managed to get it to work, The output is shown above.

Thanks @Eternity

I have just given up. So I am back to the Aqara & Xiaomi ZigBee app from Ted…

I have debugged the complete source of MiHomey, but I can’t figure out what is the difference between your and mine setup.

I even set-up a home-assistant instance and there everything works like a charm. Even if I use the code from MiHomey that gets the subdevices into a seperate file and running it from a different computer in my network, the subdevices are returned…

So… lost quite a lot of spare time, but gained some Homey-app-development-skills :wink:

Thanks for the help!

1 Like

hello I just installed mi homey, but I encounter a problem the vibration sensor (which worked before with the official aqara application) no longer works as a sensor in heimdall, I think they are not identified as a sensor in mi homey, would it be possible to make this modification?

Will this app be updated to SDK3, @Maxmudjon?
I would love to have it supported on the new Homey Pro 2023…

2 Likes