Get, we are working on verifying every Aqara sensor we can get, thanks for let me know Julhio.
Edit,
BTW, have you updated the firmware of the sensor RTCGQ11LM, some user told us that some sensors become unsuppoted after that.
I didn´t actualized the firmware of sensor, I don´t have the Aqara hub and the iHost don´t have this funcionality.
In version 1.10.0 everything worked fine, but from then on it stopped working. It only started working again now in version 1.12.0, but the RTCGQ11LM sensor did not work again.
RTCGQ11LM is quite difficult to paired, @ward told me that he has succeed after times tried, stability still under observing.
Hey,
The sensor struggles to pair both on iHost and my HA setup via Zigbee2MQTT. But it works (no illuminance entity though) so far in version 1.12.0 even iHost did not get the device name and model info.
I assume this was caused by a faster closure for its pairing mode than expected and iHost as well other platforms failed to complete the whole interview process.
If you can not get the device discovered, try constantly pressing the identify aka pair button to keep it awake during the process. Let me know if the trick would work.
Thanks for the feedback.
Ward
The first time I connected the RTCGQ11LM it was fast and after connected it worked very well.
Regarding the faster closure for its pairing mode, I have seen it when I paired some Tuya sensors on iHost.
I tried again pressing the pair button each 1s during the pairing mode, but had no success.
I am using v1.12.0. My Host has now the 1.13 update available, but I am afraid in update and loose again my zigbee devices.
In the spreadsheet shows the aquara door sensor MCCGQ11LM as compatible.
But, it never pairs, even though I’ve turned on the Zigbee2CUBE feature.
Hi Julhio,
I truly understand your frustration in this case. But the sensor did struggle to pair even with Home Assistant. That’s the reason I now prefer standard Zigbee 3.0 gadgets at home.
Here’s other tips might help:
-
Keep the sensor close to iHost/Zigbee routers while pairing
-
Replace the battery (low battery voltage might weaken the signal)
-
Try to pair it with HA via Zigbee2MQTT or an Aqara Hub to check if there’s any firmware update
I am at 1.13, and will help to test this if this sensor work.
Thanks for your patience
Ward
I have tried my Aqara sensors with CUBE V1.3, as follows,
- TH sensor, model WSDCGQ11LM
- Water leak sensor, model SJCGQ11LM
- Motion sensor, model RTCGQ11LM
are all paired to iHost with Zigbee2CUBE feature enabled, and just like @ward tested, that’s tricky, the motion sensor needs to be pressed as one second pace when pairing to keep the sensor “alive”.
1 Like
Trying to find one and verify again on my side, let you know if i make some progress.
Edit,
Aqara window/door sensor, model MCCGQ11LM, paired directly to iHost without Zigbee2CUBE feature enabled.
A little tricky is, press the pairing button as one second pace when pairing to keep the sensor “alive” during pairing.
@luiz.vinicius73 I have five MCCGQ11LM working at home. For connect them, I needed to do the trick of clicking the pairing buttom as one second pace when is pairing.
Another trick I have seen is remove the battery, short circuit the terminals of battery holder to discharge the circuit and then put the battery again and restart the pairing process.
@ward and @yitie, I disabled the Zigbee2CUBE feature and didn´t solve.
So, I updated to v1.13 and for surprise the sensor RTCGQ11LM was already there.
Thanks for the help.
I think the problem is the bomb update v1.11 ended up hiding the sensors (I don’t know how). Since they were always there (but still didn’t work), they couldn’t be paired back in.
In version v1.13, the zigbee map now shows the connection of motion sensor RTCGQ11LM (in green), but the door sensors MCCGQ11LM quality connection are still not showed (in red):
@ward and @yitie, when I updated all my matter devices desappiear.
I can´t see them on matter list., I can´t control them on Google Home.
I’m going to have useless home automation for another month.
Please, implement the roll back function or do more testing before make the release.
I want to install the version v1.12. again.
Hi, I’ve just tried pairing an Aqara RSD-M01 with my Ihost as it appears in the ZigBee2CUBE compatibility list. I can pair it but it shows as a Lumi power switch.
I’ve had a look in the logs and this is what it says when it is discovered.
[INFO] [2023-12-31 12:38:38] mqtt_pub : topic: zigbee/system/discovered, payload: {“manufacturer”:“LUMI”,“model”:“lumi.curtain.acn002”,“serialNumber”:“54ef441000992ea0”,“firmwareVersion”:“1.15”,“displayCategory”:“switch”,“linkLayerType”:“Zigbee-ZED-Mesh”,“capabilities”:[{“capability”:“power”,“permission”:“readWrite”},{“capability”:“rssi”,“permission”:“read”}]}, property: reqClientId:zigbee, reqSequence:1704026318178
[INFO] [2023-12-31 12:38:38] mqtt_pub : topic: zigbee/device/54ef441000992ea0/information, payload: {“manufacturer”:“LUMI”,“model”:“lumi.curtain.acn002”,“serialNumber”:“54ef441000992ea0”,“firmwareVersion”:“1.15”,“displayCategory”:“switch”,“linkLayerType”:“Zigbee-ZED-Mesh”,“capabilities”:[{“capability”:“power”,“permission”:“readWrite”},{“capability”:“rssi”,“permission”:“read”}]}, property: reqClientId:zigbee, reqSequence:1704026318180
[INFO] [2023-12-31 12:38:38] mqtt_pub : topic: zigbee/device/54ef441000992ea0/updated/power, payload: {“powerState”:“off”}, property: reqClientId:zigbee, reqSequence:1704026318202
[INFO] [2023-12-31 12:38:38] mqtt_pub : topic: zigbee/device/54ef441000992ea0/updated/rssi, payload: {“rssi”:-73}, property: reqClientId:zigbee, reqSequence:1704026318203
[INFO] [2023-12-31 12:38:38] mqtt_pub : topic: zigbee/device/54ef441000992ea0/availability, payload: {“online”:true}, property: reqClientId:zigbee, reqSequence:1704026318205
Any idea why its not being picked up correctly?
Sorry for hear that, it’s really weird that i and my colleague haven’t met any issue after upgrade.
The team will do more test and to see if can duplicate the same issue, and the roll back feature has been highly proposed.
Edit 3H later,
We have duplicate the issue and the engineers is on it, one conjecture is something wrong related with the Matter Bridge macro library, need some time to address and confirm.
The dev-team is looking on that, let you know we have any clue.
Hi, may you download the system logs and sent it to me ?
The rollback feature can be done by a button or checkbox. This way the firmware will not be exposed and you can use the same current functions.
Nice. Thank you for the support.
I tried to send the log for you in private message, but the there is a size limit of 8MB for the annex and the log has 24 MB size.
I have sent it inside Feedback 198618, you can get the log there.
Thanks
Got it. We are looking out the problem.