Aqara wall switch H1 (WS-EUK04) - not syncing state, not showing power measurement anymore #21679
Comments
|
Hello @adynis, Is it possible to remember what versions your setup had when you paired them? At which month/date maybe? - That could tell us which versions you might had.. |
|
oh ... @mojiro , sorry .. I missed your message. I observed it now by accident. I will answer to you immediately after my intended message. 1.) Something ... less important but I can't avoid mentioning it ... 2.) This I consider it IMPORTANT: |
|
@Nerivec |
Sorry for not answering, I missed the mail when you initially wrote. In the same time, like in the poiint 2.) written above, with some effort I was usually succeeding to join it with power & state-sync working. I couldn't yet understand which was the trick to make it work ... I was trying various things until it was working ... . Things I was trying , independently or combined :
The problem was that all these tests were DIFFICULT because of the Z2M restart issue ( #21118 ) . But somehow in ... ~5-30 minutes of testing I was usually able to make it work ... despite the z2m restarts in the middle of "device configuration" or despite all the "non-understandings" which I have with regards to all previous points while testing |
|
@adynis |
|
Yes, but what do you think it would worth "adding" in the log:
|
|
@adynis wastez may be right. Hopefully, the pending ember PR should also take care of this issue. All newly reported issues (since As for the |
|
@Nerivec : I would be glad to test ! Jsut that .. being in home assistant (on a "productive environment" ) I ask first: can I just change to Z2M-edge addon in HA and all devices will still be there ? |
|
@adynis |
|
In the meantime here's one log: PS.
|
|
Flash https://github.com/darkxst/silabs-firmware-builder/blob/ember-nohw/firmware_builds/yellow/ncp-uart-hw-v7.4.1.0-yellow-115200.gbl again, just to be sure, then definitely set |
|
EZSP logs, 2 files combined, since it was a Z2M restart in the middle: |
|
Oh, I've seen you message now, @Nerivec . Oky , I reflash, set rtscts to false and re do the log 👍 |
|
Firmware log: Does this mean that ... it worked ... or not ... ❓ |
|
a new log:
log_ember_6: Let me know what other logs are helpful to make (ezsp? something else?) |
|
This device is terrible, awful. I'd take a hammer to it if it was mine... 😞 With
|
|
Thanks @Nerivec for looking into it ! |
|
@Nerivec Sorry, I don't understand what's wrong? |
|
@kirovilya Check the logs here. You will see the |
|
@Nerivec hmmm... So many This also happened when connecting via routers - it was solved like this Koenkk/zigbee-herdsman#938 |
|
@kirovilya The log in the post I linked is with |
|
I saw similar behavior not with Aqara devices, but with Tuya. |
|
I'm not sure if it is relevant at this moment/commit_version, but I just tried also with edge, and still no change: Zigbee2MQTT version: 1.36.0-dev commit: 14e0440
I tried removing and re-adding my aqara switch, and here's the log: PS. before making the log I tried a couple of times more, and still nothing. |
|
@adynis I was waiting for a few related changes to be released, since you swapped to edge, before coming back to this. Can you update your edge version so you get herdsman 0.38.0, then let the network settle for an hour or so after the update (it changes a few configs, so just to make sure the mesh readjusts as needed).
|
|
Yes.
|
|
so ... It's a big log, but I tried to write my steps to allow you "focus" only on what you find useful: HomeAssistant Yellow , with Zigbee2Mqtt Edge addon.
Z2m addon config:
Device Under Test:
What I did: PS. something offtopic:
log_ember_edge_3.txt |
|
Thanks! Details much appreciated! It tells you just how much that device's firmware is broken when it doesn't even want to join with another Aqara router... 😞 |
|
Something is very strange with uploading files ... I can not make it work ... I try also in this comment. |
Might be some temporary github problem.
I've found the best way is usually to make an outer circle like you did with green devices (end devices), grouping them near their router, and then a smaller circle inside with blue devices (routers/coordinator). I'm most interested in the links between those Aqara routers (including the coordinator). |
|
Now I'm adding more screenshots (I challange github while attachments do not work properly ... ) After I arranged as you suggested me, I found 3 things as interesting :
|
|
I got the log file yes. Much cleaner with new 0.38.0 version (no more duplicate "device left"), so that's a plus. Unfortunately, it isn't very descriptive in the problems without herdsman debug enabled. I can tell you however, that all the routers you tried to pair the Aqara device to, flat out denied it from joining. Any chance you could try enabling herdsman debug, then re-do one remove/pairing with Coordinator only, and one remove/pairing with a specific router (one from your previous tests, doesn't matter which)? Then you can disable herdsman debug and restart Z2M.
That's normal, through the mesh, they all eventually go back to the coordinator.
Likely another Aqara firmware "mishap" where the device is reporting as an end device, even though it is a router... 😞 Offtopic: I can also tell you from your network map, that most of your end devices have pretty poor connections (below or near 100 LQI). I'm not sure if that makes sense (I'm guessing not!) based on the areas/distances to routers/coordinator, but on top of possibly creating network issues, that can seriously affect battery life. If you have a strategic place where it could be put (need a socket and an old phone charger or something like that), I'd suggest getting a coordinator that you can flash as dedicated router (example here). The device can be quickly paid off by not spending $$$ on batteries... and should increase reliability by a large margin in the area it covers. |
|
Oh ... I forgot to enable hardsman debug in the edge addon 🤦♂️ sorry. Related to LQI ... interesting ... in the Z2M main page, with the list of devices (Except ~4 exceptions) all numbers are much bigger .. |
|
I re-did the test.
Thanks for looking on this and, as before: Just let me know what other tests I could do in order to help debuging (and hopeuflly fixing) this behavior ! |
|
Something I just observerd: Longer:
Later EditI re-did things ALSO with latest edge version: and I found the SAME BEHAVIOR
Same test as above on EZSP with re-joining aqara device, it worked from the 2nd time: |
|
The Let me know how it goes after it is available 😉 |
|
Initial quick & partial test:
IT WORKS !!!!!!!!!! 🎉 🎉 🎉 I removed my "hobby_aqara" and re-joined it 2 times (like previously in last weeks) and now it immediately worked each time: OnOff is synced, measurements values are shown !! 🥳 I need to test more tomorrow evening (because now I can't stay anymore too much) but at least on the first quick, short test it worked. Thank you, @Nerivec . I will come back after a longer testing. |
|
After more days of testing, I can really confirm some things:
Log for showing the error of trying to join a device on a router, not on coordintor: full log (search for : 'was denied joining via' ) : One last question: should I be worried about those strange messages ? (especially those with many not-ASCII values) like: |
|
The workaround to make these Aqara devices work is to make them think the coordinator is the Aqara Hub, so I'm not surprised that they don't pair properly with other devices. Basically Aqara is trying to prevent you from using their devices without their hub...
These are just unknown values that are not hexified before being printed to logs. Not a problem, just unsupported attributes for a device model. When the device has all expected attributes working in Z2M, that usually means the brand is using extra attributes to exchange with their hub & co, that Z2M doesn't care about. I'll let you close this issue if that's alright with you. Thanks ;) |
|
Thanks a lot @Nerivec for fixing this topic (and for offering such a great support) ! 🎉 🥳 🥇 |
What happened?
My kids played with one wall switches - it was showing "red" leds ... 😡 it was removed from Z2M. (probably they pressed more than 6 seconds)
Device: WS-EUK04 (lumi.switch.n2aeu1)
I added it back to Z2M (1000 times) and I can not make it work properly:
Workaround for issue 1. :
I found somewhere on internet this screenshot with the suggestion to add "Reporting" :
I don't know if this is something ok to do, it looks like it has some slower reaction times then before, I'm not sure if this way I make any process to consume "energy" just to check from second to second the status of the switch ... somehow I feel that it's not ok to have this workaround ...
Some remarks:
Final thought: I'm not sure if it is from aqara device itself (since I was having this kind of issues also in the past), or from Z2M , or from new ember, or from something else ... but it would be helpful to have a solution when it happens. Also ... like I already wrote, the workaround I used doesn't "smell nice" to me now (unless someone confirms to me that it's ok :) )
Zigbee2MQTT version
1.36.0, ember
Adapter firmware version
7.4.1 [GA]
Adapter
Home Assistant Yellow - EZSP v13
Setup
HomeAssistant on HomeAssistantYellow
The text was updated successfully, but these errors were encountered: