Skip to content
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

EZSP 6.10.3.0 for TUYA TYGWZ01 not working correctly #3

Open
Ordspilleren opened this issue Jan 29, 2023 · 12 comments
Open

EZSP 6.10.3.0 for TUYA TYGWZ01 not working correctly #3

Ordspilleren opened this issue Jan 29, 2023 · 12 comments

Comments

@Ordspilleren
Copy link

Hi, thanks a lot for providing updated firmwares for these devices!

Just to let you know, the latest version of the firmware for TUYA TYGWZ01 in this repo does not seem to work properly.
When trying to pair devices (only tried with IKEA remotes), the handshake is not successful. The device is detected, but pairing ultimately fails.

The previous firmware version (6.10.0.0) you also provided seems to work fine.

@MattWestb
Copy link
Owner

I taking one look later if i was doing somthing wrong.
I have only testing it by loading and see that the network is still working.
I dont remember if 6.10.0 was one with ZGP support and maxed link keys or it was one standard EZSP with 12 link keys.

And the 6.10.3 is the last golden version and i like having it working well on this devices.

I have also doing one RCP for thread and Zigbee but is very likely not working OK but i think its possible getting it working for this device than i have it working very well on my Billy modules with open thread boarder router.

PS: The EZSP 6.10.X is the last possible compiling for this chips then Silabs have deleting all support for MG1X devices in 7.X and only having the RCP still being updated.

Thanks for the feed back Lasse !!

@MattWestb
Copy link
Owner

Was trying making one new NCP 6.10.3.0 with multi-rail and GP with max TC-Link key but was giving up after 5 treys. The updated Simplicity Studio is putting the NVM file (for token and keys) in the middle of the running code instead at the end of the flash.
So was using the old working 6.10.0 and copy to one new project and updating it and it was being build OK and with all the good parameters form the last good one.
I have not testing it at all then i is trying getting RCP 4.2.1 working on my Billys and SkyConnect and need much testing of them for knowing its working OK.

If you is flashing this firmware and the APP is not starting OK you must flashing one working one with SDW probe then you cant getting the chip in bootloader mode (if you not have updating the bootloader with boot pin) so be careful !!!

ncp-uart-hw-gp-61030.zip

@Ordspilleren
Copy link
Author

Thanks for attempting another build!
Looks like the same issue persists. I also cannot form a new network with Bellows on 6.10.3.0, so that might be a quick way to test if it works.

@MattWestb
Copy link
Owner

For the moment is bellows little tricky forming network over network also with RCP + Sirlabs addon. I was not able forming network with one Billy on one ESPHome with serial server but was doing on with one USB-TTL and then connecting it and its working OK.
Then the firmware is not tested it can being bad settings i have made or somthing other thing.
My Billys is running 6.10.3.0 but is build with one earlier version of Simplicity Studio (that is very chaotic for the moment) and dont putting the NVM in the APP code = was doing it OK.

Also can you testing adding one router device like one normal light ?
EZSP 7.X is having very strange problems with direct children and it can being its implanted in this version (i have blocking all my coordinator for having direct children and dont have the problems).

Thanks for testing !!!

@Ordspilleren
Copy link
Author

Same problem with lights, I don't seem to be able to pair any device or form a new network.

@MattWestb
Copy link
Owner

@Ordspilleren I have updating my Billy with EZSP 6.10.7.0 and my production system is up and running with it for some hours on it.
Then i was doing the same for the tuya module but with there settings and it was compiling OK but i have not testing it.
Feel free testing if ts working or not then its very likely the lasts bug fix we is getting for the EFR32MG1B chip or perhaps some security patches but not much is expected for thins like IKEAs MG1P but its running RCP firmware great with Zigbee and Thread on it.

Mvh Mattias

@Ordspilleren
Copy link
Author

@MattWestb Thanks! Just flashed it and it seems to work fine, didn't even have to repair my devices for some reason.
I wish I could run RCP multi-protocol, but the only easy solution seems to be the Home Assistant add-on which I can't use because I run mine as a Docker container.

@MattWestb
Copy link
Owner

Great !!
I shall updating the readme that is tested.
If you running ZHA it can being that all was OK but our Puddly have done great working auto migration so if the NVM was cleared ZHA is restring the last known and then starting the coordinator and you dont see it only the start is taking little longer time.

I shall looking cooking on RCP for the module then the addon have possibility using network connection for the comport to the radio chip / module but it was broken for some mounts ago but it shall being fixed now (i have not testing it) and i think its one great solution also tuya have one newer hardware that is running Zigbee, Thread and Matter but i dont knowing if its the old MG1B or the new MG21 module they using or the TElink ones.
If they is using the same module it shall being great if some can dumping the main flash and the user data of it but we is knowing all pins used so shall not being any problems only getting it working OK can being trickery then i have my Billys running well and its MG1P = the same hardware only higher class of the chip.

I running Supreveised on small devices like RK TV boxes with armbian (23 and 64 bits) and latest Ubuntu. its little work getting it installing and not blocking updates but working well if having more then 512k RAM.
Production system is one RPI3b+ and is running the latest NCP firmware for 2 weeks now but i like migrating it to RCP but i dont do it until the problem if fixed i writing below.

Thread devices is super stable but i only having 2 EVE energy and one Nanoleaf light and is super fast and stable !!
Only bad thing its that HA cant handling the routing if using more then 1 OTBR its loosing the route to the devices but all is online if using the last aroused one.
I shall updating one or both EVE Energy firmware so getting Matter firmware but i need one friend visiting with his iPhone for doing it and its costing one coffee but i think hi taking one flight nest week to Vienna ;-).

I posting the RCP firmware then i have one for testing and pinging you here then i have done it.

@MattWestb
Copy link
Owner

@darkxst Hi man i have seen you have getting the universal-silabs-flasher working with the ZBGW that great and our Puddly was fixing the problems.
If you like testing i have cocking one EZSP 3.10.7.0 that have little more bug and security fixes that looks working but need more testing for our ZBGWs..

I mostly working / using RCP for getting newer EZSP version working on the MG1X chip / modules and like getting it working for the ZBGW and it shall being easier testing with universal-silabs-flasher if its starting OK but its need SWD flashing if somthing is going wrong therefor its little tricky testing it.

@darkxst
Copy link

darkxst commented Aug 27, 2023

I dont have any gateway hardware to test really (I may have a Sonoff Bridge somewhere but not sure where). Ive only done any testing with ZBDongle-E and ZB-GW04 dongles...

@MattWestb
Copy link
Owner

No problem testing if you like / can or not.
Im interesting if its working OK then its doing i i changing the resounded production firmware to 6.10.7.0 but it must working well for our users before i do it.

And thanks for replaying and the work you is doing for our community.

@MattWestb
Copy link
Owner

Cooked EZSP 6.10.8.0 and it shall not being any fixed only underlying things plus the standalone bootloader is fixed for going around the signed firmware but we is using app bootloader but i have doing one new 2 (Version 1.12.4).
Zero tested !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants