New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] Silvercrest SAPZ A2 (TS011F par _TZ3000_ynmowqk2 ) #2708
Comments
I just got several of these plugs too - same behavior. For reference: HA forum discussion . It indicates that this works with Z2M where it is declared in lidl.js . I tested the Tuya Magic Spell - not working better. |
Here are some decodings of relevant packets from a sniffer log. It's the device that is requesting to leave the network. |
I have only fast looking and the device is getting the network key OK and then the coordinator is requesting and getting the Node Descriptor Request, OK (R22 device) and the device is requesting the same and is getting R22 so shall being OK. Must looking deeper of the flags and comparing with other device sniffs that is working OK. PS Its one TELink choped devices so can being buggy. |
By the way is the Ti coordinator running on updated firmware (2023) ? |
@MattWestb Thanks for checking! It's not a TI coordinator for me - it's an EZSP. I opened a topic to see if anybody has the way to update the EZSP: I've seen and add-on that seems to help with that, but not much of a procedure. |
Im very sorry but its only 2 frames with key and both looks the same only network key and the sender is 0x000= and its .. . .
Have you burning one new IEEE in the Silabs chip ?
|
The latest EZSP and RCP 7.3.x / 4.3.x can loading one software IEEE that is not burned in the chip (stored in the NVM3) but its no problem running older firmware that cant do it only if migrating to one other hardware if not having that support ZHA is burning one new IEEE in the chip and cant being reverted (with SWD flashing its possible then its in user data that cant being OTA flashed normally). |
Yes - I migrated from a CC2531. An add-on I found to flash is: https://github.com/home-assistant/addons/tree/master/silabs_flasher . |
Shall working OK i have not testing it as addon only before in veritual env. |
I have SonOFF ZBDongle-E to enable - it had v6.10.3 . The Multiprotocol Add-on did not want to startup (did not find the port), so I have reboots the HAOS system (OS itself). It still complains about "Failed to connect, secondary seems unresponsive" . Trying to find out what to do... |
I did not program the correct firmware, it was Zigbee FW with new version. The insturctions indicate:
So I removed it using the UI and then the configuration as well, but after restoration I do not have the entities .. Kind of furious... However, I could pair the TS011F |
One very interesting question is the RCP using the original IEEE or the burned one from the CC2531 but now you shall also having the possibility changing it without burning the chip IF our Puddly have making all right. |
It's using the TI IEEE address. To recover entities (different than those I had), I:
Luckily I had an export of the critical devices in devices.csv with zha-toolkit which helped map the devices to their original entity names and locations. |
If the IEEE was the same in the "new network" and the old backup its likely the frame counter was set to zero and the network was throwing all frames from the coordinator as replay attack. Great that you is up and running after some hardware digging (its little different for code digging but its more my thing as code is yours) !! |
@MattWestb and @mdeweerd : Thank you very much for your investigation into this issue.
I have no idea how this network firmware can be updated even though I saw the following links: |
I migrated many months ago already and the migration was flawless! I think that changing to the RCP FW using the multiprotocol Add-on should also be don by initiating a migration rather than removing "everything" - the only issue being the port - ZHA might grab the port before the add-on does. So the trick would be to change the ZHA port to a bad port (currently by hacking) or disabling it until the add-on starts up I guess.
My things are HW and SW (I design HW boards and SW from FW to application level - I've also worked on design and verification of baseband ASICs for phones) ! However you noticed the Link key issue!
I'ld suggest you to stick with the Zigbee SW version. Nabu Casa indicates there are no known issues with the current FW, but this is one! https://skyconnect.home-assistant.io/firmware-update/ The add-on silabs-flasher seems to be an official method to update the key. I'ld make sure to have a recent backup, then proceed with the upgrade (implies disabling - not removing - zha) and enable zha again. The network info is probably maintained and if not you can restore it. Of course - up to you if and when you want to try the upgrade. And I would report this to Nabu Casa anyway. A Coordinator FW change fixes it so it can be argued that there is an issue with the coordinator FW. |
Finally I configured the Multi Protocol Support of my HA Yellow (even though I'm not using Thread at the moment) |
I have the same exact issue with
|
Problem description
I try to pair a LIDL Device (Silvercrest SAPZ A2 : a new version sold in France with power consumption measuremenst of the SAPZ A1 which already works well with ZHA) .
During the pairing ZHA loads the quirk "zhaquirks.tuya.ts011f_plug.Plug" and everything seems to works, but the device stays in pairing mode, it disconnect/ reconnects multiple times before disconnecting defintevly.
Solution description
A well connected ZHA device ...
Screenshots/Video
Screenshots/Video
[
]
Device signature
Device signature
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: