This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official Zigbee SDK2
[App] Xiaomi-mi ZigBee - Main discussion topic (v0.4.1)
This discussion has been closed.
Comments
the remarks about Homey config composer is only for co-developers making changes to the app...
Can you send me the original issue number and indicate which ID’s are shown when the device is included as unknown device?
1 - 0x00158d0001b93d44 - Temp 04 - LUMI - EndDevice - lumi.sens - 260
2 - 0x00158d000155e346 - Unknown - Unknown - EndDevice
I assume the second device (which should be the switch) gets the product ID and profile ID after i reset the Homey. The same happens with the temp/hum sensors.
I won't do that now for continuity reasons, i plan to do it in the weekend.
Or is it already possible to make the aqara watersensor work with the app now?
any thoughts?
In order to make this sensor work with Homey, Athom will need to implement the IAS cluster to Homey's Zigbee implementation (part of the Zigbee rewrite to be done after the 2.0 SW release): for details see: https://github.com/TedTolboom/com.xiaomi-mi-zigbee/issues/26
@PetervdK thanks for following up... can you share the full node ID's information of the Unknown ZigBee device?
Devices tab > wrench symbol > Node information
The productID is shown correctly after the reboot... and is defined (correctly) in the app.
If also the deviceID and profileID are correct, something goes wrong during inclusion... If I have the remaining ID's I'll check with Athom development to check for a solution...
Can you do one additional check?
1. Remove the Unknown ZigBee device from Homey
2. Reset the Xiaomi Wireless switch by press and keep pressed the button (not pinhole) for more than 10 seconds
3. Include the Xiaomi Wireless switch by chosing add device > Xiaomi Zigbee app > Wireless switch and following below steps, and in particular the Note:
Note: keep pressing the reset button every 2 second to keep the sensor awake during the inclusion
After the reset by pressing the switch for more then 10 seconds, the adding went much faster then before so i had hope. But alas it still ended up as unknown device.
However, just after the procedure i saw a window popping up and disappear in a split second and could just read something with "incompatible app" or something like that...
<edit>
Tried it again and saw the phrase "searching for compatible app"
I am willing to provide logs, I just do not know how to get them to show. Running on Homey v1.5.11, and 0.4.0 of this app.
I guess the endpoint for the ctrl_ln1.aq1 is different than I anticipated...
Do you have experience with installing and running an app through the Command Line Interface (CLI)?
As explained in this guide (step 1-3, with Node.js 8.9.4): https://developer.athom.com/docs/apps/tutorial-Getting Started.html
If so, you could create the needed logging by:
1. download the Xiaomi Zigbee app from https://github.com/TedTolboom/com.xiaomi-mi-zigbee
2. Modify (with an text editor) in `/drivers/ctrl_ln1.aq1/device.js`: on line 10 `// this.enableDebug();` into `this.enableDebug();` and on line 13 `// this.printNode();` into `// this.printNode();` (aka uncommenting the log statements).
3. Run the app from the command line (and within the apps directory) with `athom app run`
I'm in particular looking for the Node overview of the ctrl_ln1.aq1, similar to the one of the ctrl_ln2.aq1 (https://github.com/TedTolboom/com.xiaomi-mi-zigbee/blob/master/drivers/ctrl_ln2.aq1/device.js#L96).
Can you copy that for the logging and send it to me?
After this, simply stop (CTRL-C) the running app and install the Xiaomi Zigbee app from the app store.
If you need support to execute these steps, please contact me on Slack.
That sounds to me like an issues in the inclusion process, handled completely outside the app scope (outside to setting the correct ID's)... I'll check with Athom development how to proceed..
In this intermediate update, I fixed the issue with the Aqara Smart Light Wall Switch single (LN-version) as reported by @teowzh.
Changelog:
Just wondering if there is a way to say, if i'm holding the switch dim a device?
E.g. I actually only have the Left switch hard wired, the right switch I have a flow to toggle a yeelight. But it would be nice if i could toggle, but if I hold it down it dims?
Any way to do this?
EDIT: Also noticed that when I go to the "and" column (also just noticed same in the then column) I only get Right Switch or On options - no Left Switch
EDIT2: Think I've just worked it out that On with nothing in brackets IS the left switch
So there is no option to add this to the device / driver...
And yes, you're right, due to limitations of the current Zigbee implementation, it is not possible to create a sub-device (multichannel node) similar to Z-wave.. so I had add the second (right) switch on the same primary device, resulting in a custom made action card to turn on or off / and also speech is not working for the second (right) switch...
When the Zigbee rewrite is completed, I'll update the drivers / app accordingly.
Thanks for the clarification! And yes, didn't think about the inclusion mode kicking in!!
I assumed it was distance but it would seem that is not the case given the new switch is more than close enough...
Is there anything I can do to resolve this, it's driving me nuts. Was working fine immediately after installing switch but this morning just not reporting
“after installing this” refers to after installing the Aqara switch and “HBS” is the Aqara Human Body Sensor (incl. lumminance sensor) or is it the Xiaomi sensor?
And you expected the Aqara switch to create an routing mesh point for the HBS? Correct?
Did you confirm the range issue by moving the HBS closer to Homey; does it respond better in that case?
Typically the Zigbee mesh is a self controlling mechanism, but it will require some time (and patience).
You could try to wakeup the sensor by pressing it’s button from the intended location or removing the sensor and reincluding it (now the switch is part of the network)..
This issue needs to be looked into by Athom.
Can you create an GitHub issue at https://github.com/athombv/homey/issues and describe the steps taken above.
It would be awesome if you could remove one of the troublesome devices, reboot Homey and after all apps have been loaded (safe 30 min after reboot), try to include the device again.
If it fails, send a log to Athom and copy the code into the GH issue.
If you send me the issue number, I’ll contribute to this issue, ok?
- I have a HBS (with luminance) which has been playing up for some time. I figured distance was the (main) issue
- After installing the Aqara switch, I hoped that it would create a routing mesh point - correct
- The HBS did seem to perform better close to Homey, tho I can't be sure...
I might try your last suggestion - it has always been problematic so wonder if just de- and re-including it might help...
Thanks to the soldering skills of @robertklep, I'm again able to listen in on the communication between the Xiaomi hub and the devices... which yielded quite a lot of additional settings for several (mainly mains powered) devices, among other the Curtain controller (ie. reverse direction) and above mentioned switches.
The Aqara Wall Switch Single / Double (L, without Neutral) appears to have an option to disable the relay of either one of the buttons... and create an option to send a scene like command...
if I interpret the data / options correctly, this should (read no guarantees yet) the following options: 1x click, 2x click, hold and release...
So far the 'good' news.
There are (again) some limitations within the Zigbee implementation that currently prevent me from implementing these settings into the app.. I'll check with Athom if we can find a solution, bypassing the issue...
Looking forward to hearing more from your investigation and conversation with Athom!
I have an Aqara Wall Switch Single (L, without neutral).
After pairing, that goes ok, the switch works fine with Homey and some flows.
But after a few hours the connection with Homey seems to be lost and the switch doesn't respond anymore.
Removing it from Homey and pairing again (after reboot or PTP of homey) all is well again, but the same happens, connection gets lost.
All my other zigbee devices (Aqara, Osram, Hue and Innr) keep working fine all the time.
The Aqara Wall switch is only 2 meter away from Homey.
What could be wrong?
Can you check based on what steps the issue becomes reproduceable?
So I can try to reproduce it here at home and what the Zigbee network traffic via my Zigbee sniffer...
@PetervdK great! Much appreciated.
The Xiaomi app was updated in the mean time, so no solution there too.
Github issue created: #2706
Athom log number: 2FB0CBA11D
will it be possible to add support for it in your app, @TedTolboom?
After the pairing of the switch (single button L, without neutral) , that goes ok, i don't do any other steps.
I also don't hold the button to long, (i know that might cause it to go into pairing mode again) but just a quick push and it works ok like it should.
But after a few times switching on/of with a flow triggered by an Aqara doorsensor or with Homeykit it suddenly loses connection.
It mostly happens within 2 hours after after the pairing, but one day it worked for almost 12 hours and then lost connection again.
If i test the flow, the red triangle comes with the message "AF data request fails, status code 205, No network route. Please confirm that the device has (re)joined the network".
All other zigbee devices keep working ok.