[Device Support Request] Tuya Zigbee Repeater - Ts0207Device name #4175
Comments
|
Hi there, is the repeater the one with USB? Thanks. |
Correct, it's a mini USB stick with a 10 dBm range. https://zigbee.blakadder.com/Tuya_TS0207.html |
Ok, thanks for the device request! |
|
And it don't create device in API ? |
Yes, I need these to repeat the signal around my house. I have 6400 sqft to cover and there are some deadzones where the zigbee devices are not routers. The IKEA repeaters are larger and cover 2-3 ports on my USB/120v outlets. The Tuya repeaters take a single USB port on each outlet and do not interfere with other connectors. It does not create a device in Phoscon. |
|
Yep, but you can use it even it s not visible in tha API, do you realy need it visible in the API ? |
I see, well they don't seem to be repeating on the device map. They seem to lose connection to devices (but have a direct connection to the Conbee II) while the Ikea repeaters do not. Aside from that, it would be nice to add it into the API. That way I can pull it into Home Assistant and my device maps.
|
|
@TheAlphaLaw Sorry I have totaly forget you. |
|
No worries! No I only have Windows machines, Home Assistant is running on a VM. |
|
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
|
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
|
Any news on compatibility with Tuya Zigbee 3.0 USB Range Extender (a.k.a. Zigbee Signal Repeater) as a Zigbee Router device? Tuya SKU: RP280 It is however not clear if it really works as a Zigbee Router with third-party gateways or if need Tuya gateway as their description: https://zigbee.blakadder.com/Tuya_TS0207.html Signal Repeater Zigbee 3.0 Model TS0207 manufactured by Tuya Zigbee ID: "TS0207"; "_TZ3000_m0vaazab"; "FNB54-WTS08ML1.0" https://www.aliexpress.com/i/1005001459823340.html?spm=2114.12057483.top.4.55932e050QWoD7 https://www.aliexpress.com/i/1005001274714963.html https://www.aliexpress.com/item/1005002441359324.html https://www.aliexpress.com/i/1005002526017479.html https://www.amazon.com/Extender-Protable-Amplifier-Gateway-Repeater/dp/B08MWBKK4P
|
|
@Hedda Could only be checked if you have the actual device. Can't tell from this unfortunately. |
|
It seem working at least for one user #4443 (comment) |
|
@nukleuz80 Is it possible to relay device states of any kind to Home Assistant? It's being displayed as a water sensor in Phoscon and not as a repeater. Attempting to utilize these repeaters as presence detection for vehicles, for automated garage control. |
|
I m not sure to understand, this device is just a "repeter", can't be used for detection ... |
|
@Smanar Sure it could. If connection status could be reported to Home Assistant, I could use it as presence detection for my vehicles. I do the same with Wifi, connections but its a lot slower to connect when compared to Zigbee, |
|
Ha yes I undersand, you want to use it on your car, and check for the presence on the zigbee network ? State/reachable is not precise enought ? |
|
@Smanar Yes, correct. Phosconz reports it as a light/water sensor. No states though, even if added to a group. Reports "Unknown" to home assistant no matter the connectivity status. |
|
Phoscon is not deconz. There is lot of thing supported by the API, but not in phoscon. As this device don't need reporting, it s possible it was too much "quiet". |
|
Disconnected Connected Any state change on connect and disconnect could be used for me. |
|
So you can use the field "reachable", no ? to check presence. |
|
Yes, that would work. However, the Phoscon integration does not pull that data into Home Assistant for some reason. Deconz is running on a Windows server, instead of on my home assistant instance. So I need to use the Phoscon integration to pull in data.
It reports as "unavailable" no matter what the state. If added to a group, it reports "off" always. |
|
Sorry to highlight you @Kane610 , but you know HA realy better than me, and from my memory state/reacheable is used. |
|
I guess it will not work because it is expected to be a light but doesn't actually report any data expected from a light. If it would be added to HA it would need to be exposed as a binary connectivity sensor. Though I would need to set aside the normal availability reporting to always report sensor available as always True and then use availability status as the main state of the sensor, I'm not sure this device warrants such an implementation. And I'm not sure it would fit in as a device tracker entity either. |
|
Whatever I can do to help, please let me know. There are no other devices I know of that can be easily used this way, because of size and power requirements. |
You can start by evaluating your hypothesis for how relevant it is to use with your car. |
Very relevant. WiFi won't connect fast enough. I have 4 Unifi AC HD inside and even tested an outside AP. I can't get any wifi devices (including my vehicle) to connect fast enough. ZigBee is instant when powered on and even connects farther out. Might be the devices, protocol, or cross-talk; unknown. What I do know is this tiny ZigBee repeater destroys them all. Goal is to open and close garage with vehicle presence. |
|
Can you share events of this as it would be great to keep real life data to use with tests |
|
Can you provide an example of what you'd like to see? |
|
enabling debug logging of Deconz integration in hass shows all events sent from Deconz over web socket, sharing the events for connecting / disconnecting / reconnecting would be great Also a full device print out from Deconz would be helpful for the tests |
|
Sure, I can show for WiFi device. Obviously not for ZigBee device until it's implemented. |
This is only zigbee so no need to share anything but what is implemented in this issue |
|
I'm not sure anything will show in deconz integration for this device but I will check. |
|
Ha ? Or it's the device type itself that causse issue ? |
|
I added basic support to pydeconz, that is not the same as adding it to the integration though. |
Ok thank you! 👍 Do I need to submit a request to those that manage the HA integration? I have Deconz installed on a windows server instead of directly in HA. Unfamiliar with next steps but happy to take them. |
Thats me! I won't give any promise when its implemented and ready. I fully prioritise completing my current rewrite and then I have stuff I have postponed in favour of doing the rewrite. If its not part of the next HA release 2022.5 ping me, then I might have forgotten it |
Sounds like a plan, thank you! |
It doesn't look to be on 2022.5. Any update? Thank you! |
|
Checking back in, confirmed not implemented yet :) |
|
There are some other things I will need to attend prior to revisiting this device. I can't promise anything about when I can get to it |
Any chance on this going in for June? Happy to make a donation if you point me in the right direction. Thank you! |
|
Before I can fix this I need to improve the unique id handling of the integration because it is not sustainable approach right now. My profile on GitHub should have a GitHub sponsors reference. |
Checking back in as a reminder :) Thanks! |
Most architectural changes are in place, so closer than ever :) |
|
@Kane610 How are we looking? Eager to test :). Out of curiosity, will lights that lose connectivity to the Conbee II also show as unavailable in HA? |
If deconz marks the device unavailable so will home assistant. I started looking at how to do this one just a few weeks back. Shouldn't be too long sorry for the slow progress. So much to do and so little time |
Device
Product name: Tuya Zigbee Repeater
Manufacturer: _TZ3000_m0vaazab
Model identifier: Ts0207
Device type : Router/Repeater
Screenshots
The text was updated successfully, but these errors were encountered: