-
Notifications
You must be signed in to change notification settings - Fork 9
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
TYZS4 Module (LIDL Hub) Pinout #2
Comments
Nop !!
And the hardware settings for the UART is looking like this in Simplicity studio with SDK 3.2.3:
The PTI i have in my test firmware but i have not my standard connection for it and its useless for normal user then you need one original Silabs WSTK for using it. The pinout of the comport i think you can finding in the RTL8196E data papers but the hacker have using the default comport tuya is using with the same setting found in the original Linux installed on the device. I cant guarantee that the HA flow control pins / pads is right but its looks working OK but if you is finding its wrong pleas info my and i making one updated firmware with the new settings. For the devs that was hacking the ZBGW it was not interesting digging deeper then needed and we have getting it working and if tuya have doing updated version of the TYZS4 is still pin and firmware compatible with the original one or we have getting complains form user that have not getting it working and need one J-Link for de-bricking there device. |
Sorry for possible confusion, I'm sure that your pin assignment is CORRECT. I'm trying to rebuild the TYZS4 FW with the latest V8 Zigbee stack. Seems this is GSDK 4.0.x (EZSP 7.0.0), so I have to set this pins in the project. Also I traced the PAD connections using photos from different documents and now have the assignment as below. |
Its depend witch SDK you is making the project you is getting one force bootloader pin and its possible deleting but then you must doing more steps for getting the firmware being build OK and ZBGW is not having one hardware for using it so i have left it one one "dummy pin". If you have the box open you can using it by shorting it to ground for getting in the bootloader if the comport is not working for rebooting the NCP in bootloader mode but i think you dont need it then you is very likely having one WSDK that can debricking the chip is hard soft braking it. Mos support for MG1X is taking away or broken in GSDK 4.0.x (EZSP 7.0.0) and higher only RCP for OTR and software on host EZSP is working. I have building one RCP 4.2 for ZBGW but i have not testing it then using it for EZSP for one of my test system. HA log Billy (MG1P) running RCP and have EZSP on thehostaddon:
And looks working great with Zigbee and Open Thread Broader router :-))) My experience with Billy EZSP is the last working is 6.10.3.X and likely is the last that is getting some bug fixes (6.7.11 shall coming but its older in generations). You must setting DC-DC pass thru in the hardware setting or the chip is not booting OK for ZBGW as i have doing with Billy. For the moment is Silabs Simplicity Studio and GSDK very one large inferno with much things not working OK or at all. My Markus project cant building (MGM210LA22JNF2) then the comport is broken but the EZSP is starting on the chip and allocating NVM in the end of the flash. They is also changing the architecture from old "ember" to SL prefixing and also streamlining it with Open thread for making it easy making cross platforms projects. Some user is hacking one hub that looks using one old version of Z3Gateway with MQTT in it zigpy/zigpy#796 and its using one MG1B chip but we have not getting the pins it using so no updated EZSP to 6.10.3.X. If you like having one good Zigbee module for your ZBGW put in one ZS3L its having one MG21 and i can building all projects on it and its working great only need some soldering and i think the pins is not fitting but its not large problem :-))) |
Thank you for the detailed answer. |
I think tuya is not selling them "over the desk". If you is having IKEA in the near all new devices is having one nice MG21 module but its not well supported in GSDK4 so i cant recommend it but i have baying some bulbs for 9€ for getting the module and is working good with registered WSDK for getting the Zigbee stack for EZSP 6.10.3.0. Before it was one SiLabs Thunderboard Sense 2 for 10$ ans was getting license for Zigbee / EZSP SDK but is discontinued and cant getting it longer. What i knowing is the TI Zigbee stack not completely free (is it the toolchange ?) but if you can using it then its very OK. Its depend what you like to do cooking NCP / RCP firmware or making custom devices and deploying. If you like getting NCP / RCP firmware for MG1B and you is knowing the pinout / settings i can cooking them for you if need pre EZSP 7.0. Its looks RCP (Open Thread / Zigbee RCP) can being done and its working on my Billy with MG1P but all normal Zigbee example is away in latest GSDK for them :-(( |
May I ask you to create for me Unix (linux64 makefile) Z3Gateway project with MQTT plugin as described on p21 and share the project directory. |
Witch GSDK is you interested of ? |
I would like to build Z3Gateway host application to work with coordinator via UART. I already flash TYZS4 with your 6.10.3 fw build. I believe it is GSDK 3.2. |
GSDK 7.1 and newer is more cleaned and remakes so more incompatible with MG1X devices. With luck is 7.0 having the MQTT in place i have not looking. Edit: The Host is still in 4.0 with UART https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.0/protocol/zigbee/app/ezsp-host with MQTT source. |
Have you looking on https://github.com/SiliconLabs/Unify_HomeAssistant ?? |
Can't see MQTT in 4.0.0, may be you mean ASH? |
Didn't have time yet, to look deep into Unify Host SDK. This could be another option with RCP fw. |
Early versions of Unify is using UART / EZSP = working with EZSP 6.10.3.0 and newer CPC / RCP. |
I almost finish the build. Few unresolved names left. Those should be implemented in files |
That sounds great !! :-)) |
Most of, I hope :) |
Seems this will be the hardest part. A lot of changes... |
I hope you have all you need i cant doint then im not one code warrior !! |
I managed to adopt the sources and build the Z3Gateway application. |
I'm testing your build 6.10.3 with TYZS4. It seems there is some problem with it. |
I was only making one fast test and was also having problems forming network also with bellows CLI and zigpy CLI but was getting it working somehow. |
I don't have any devices types like openthread etc |
EZSP 6.7.X (latest is 10 in the end but is no real bug fixes) is the most stable version. RCP for IEEE 802.15.4 (Thread and Zigbee) is using mush lesser hardware (the radio and sending the frames to the host) also its possible in combination with BT (alpha code) but i think its not going well for MG1X devices. The EZSP 6.10.3.0 is having more bug fixes so shall being better but im not 110% sure its stable as 6.7.X is. I getting one Nanoleaf Essentials Smart Bulb (20€) tomorrow and shall try getting it in my open thread network :-)) |
Then, maybe it will be better to spend time on RCP testing, as it seems that NCP is near the end-of-life? |
As long using SOC / NCP (the zigbee stack on the chip) is no go with 7.X then its not supported. RCP (Zigbee stack on the host system) is working but have some good and bad things. You can trying building one Multi pan RCP for the ZBGW but you need setting the DC-DC to pass thru in the setting for getting the chip booting it. |
So flashing your RCP build is not sufficient? |
RCP firmware is using one CPC protocol with the host system and need little more software for working but in the end you is getting one normal EZSP communication handle and one Open Thread Boarder Router in HA. Little info is here zigpy/zigpy#894 |
Good reading, thank you. |
Hello,
Can you please check if the pinout below is correct.
Also it seems that this module has different pad numbers as per table 2-1 from Tuya V2.0.0.
Can you also provide connections between TYZS4 pads and RTL8196E CPU.
Thank you.
The text was updated successfully, but these errors were encountered: