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
Thanks, I'll update the inclusion instructions accordingly....
For the fun of it, below the formal inclusion instructions.... never got this one working
@off112 yes this is a device limitation. I did not find a solution / option yet to get independent luminance reports.
No, water sensor is not supported yet (waiting for Athom to finalize the Zigbee implementation): see https://github.com/TedTolboom/com.xiaomi-mi-zigbee/issues
The Aqara wireless switch with Gyro will be added in the next release.
For the Curtain controller, I propose to add already basic support for the curtain controller (100% open, 100% closed) in the next release, while awaiting the tracks to arrive and further debugging.
This might mean that with a future update of the app, the curtain controller needs to be re-added to add additional feature...
The Aqara wireless switch with product number WXKG12LM has the Gyro.
Note that I also learned that I accidentally added the product ID's for this version in the last update; so you only have been able to add it based on the last app update.
The version without gyro has product number WXKG11LM.
Please note that both device have different capabilities:
- Aqara wireless switch (Gyro), WXKG12LM: 1x, 2x click, key held, key released, shaken
- Aqara wireless switch, WXKG11LM: 1x, 2x, 3x, 4x click, key held, key released
I will need to start creating a massive matrix to keep track of the differences between the devices..if anyone is willing to support me in creating this matrix, please let me know.
Any chance we could have them made available in the "And (/Or)" part of a Flow?
Thanks!
The direct answer would be 'No not hard to implement',
The current implementation of this device is to create a trigger based on a button press.... which is only accurate when triggering and not directly afterwards (It is a trigger, not a state (change)).
So adding a condition to the AND column ("Key pressed 1x) will only be valid at the moment of the trigger; so no additional benefit compared to the IF column. Basically the same holds for the THEN column, "Press key 1x" which is essentially triggering the same trigger...
I do assume that you would like to link a state to this trigger.
This can be done by creating e.g. a better logic boolean variable (e.g. named light_state) and setting up the following flow(s):
Does this answer your question?
The buttons also have <<Held Down>> as property, so if we could use this in and "And"-statement, it could possibly be used for many things like dimming up/down in flows etc. while still pressed. (To be called upon by another flow).
i.e.
IF: 'This flow is started' (by another flow via <<Held down>>
AND: ButtonStatus='Held Down'
THEN: SetRelativeBrightness=+5%
THEN2: Start a Flow (same flow)
Flow 1 triggered by <<Held Down>>, THEN set LightState=True, triggers Flow2
Flow2 This Flow is started, AND LightState=True, THEN SetRelativeBrightnes=+5, Start a Flow(Flow2)
Flow3 trigger by 'Released', THEN set LightState=False
Got to try this when I get home.
hi mate. did u solved this issue, because i having it right now. latest stable .1.5-8 ..
also i did the rest trick every 2 sec. no help. and also tried with different sensor.
https://github.com/athombv/homey/issues/1956
https://github.com/athombv/homey/issues/2325
https://github.com/athombv/homey/issues/2141
When i am trying to connect the sensor it starts to connect but after 2 minutes it doesn't find anything. Anyone?
Athom has let the community know it's using a library for Zigbee which doesn't fit the Athom standards and is not supported anymore, so there can be some problems here and there with Zigbee -> https://blog.athom.com/behind-magic-march-2018/
Biggest Github zigbee issues:
https://github.com/athombv/homey/issues/1956
https://github.com/athombv/homey/issues/2325
https://github.com/athombv/homey/issues/2141
With the pin, hold the reset button for 3 seconds until the led flashes 3 times and afterwards, keep pressing the same button once every 1-2 seconds until the inclusion has finished?
And like @lubbertkramer indicated, add the devices in close proximity of Homey.
Just keep in mind that the typical developer is lazy and tries to use as little as possible ASCII’s....
So if there is a note added, it is worth reading
but Athom will need to implement support for the IAS Zigbee cluster first. I don't expect that this will be done before release of Homey v2.0.0 firmware
See https://github.com/TedTolboom/com.xiaomi-mi-zigbee/issues/26 for details.
1x, 2x, 3x, 4x click, none of them works..
Does anyone have an idea?
So it includes the addition of support for the Aqara Wireless switch with Gyro function (product type no: WXKG12LM), one of the goals we set.
Like mentioned in the changelog, if you have already included this device (product type no: WXKG12LM) on a previous app version, please remove it and re-include it.
In addition, I made a structural change in the app in the flow card triggers based on buttons / scenes pressed by the Xiaomi / Aqara wireless switches.
So that means that as of this version both options are (still) available.
The DEPRECATED flow card triggers based on dropdown components:
Please replace them in your flows ASAP: they are no longer maintained and will be removed in a later release.
The new flow card triggers based on autocomplete components:
I added the ID's of the Aqara Wireless Switch with Gyro (WXKG12LM) in the previous app version based on the Aqara Wireless Switch (WXKG11LM) driver...
I learned that the Gyro version has a different reporting. As you can see in above announced changelog: support will be added in the next app update. Please note that the capabilities of the 2 devices differ (slightly):
Do I not need to change this one?