Closed HAuser1234 closed 1 year ago
That is the only tuya TRV family that no one have getting working and its 4 identical devices that need one new quirk. https://github.com/zigpy/zigpy/discussions/653#
is there any chance that this quirk can be created remotely? (By using the diagnostics info)
if there are any other tests necessary I can also try them out.
Its depends of the devs some can doing it very good.
@jacekk015 do you have time for taking one look on one old new tuya TRV ?? Its first gen TRV but not getting one quirk so some user have it cold in there homes :-))
thank you! I would be very glad if someone could help. Maybe this could also be benefical to other users since this is a whole unsupportet TRV family. I don't know if this helps but for zigbee2mqtt there seems to be a fitting converter: https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices/tuya.js Sadly I dont use that
All first gen tuya TRVs was getting little limited functions but we have getting extended quirks for most of them but this was not getting any basic or extended then no devs and no users was having the interest but i hope its at least we can getting basic support for it.
ok, i would anyways only need to set the temperature and maybe turn it on or off. The rest would be done in Home Assistant anyways btw thanks for the help!!
Thats i have with my Siterwell TRV with the basic quirk and its working OK but is always nice getting all functions of the device then its possible.
The kitchen TRV is holding the temperature in one °C so its working very well :-)))
yes additional functions would be great but I would be more than happy just to set the temperature through zigbee :)
Will look on this. It seems that support in Z2M is available, but as a different device. Blakadder added it as E-TOP https://zigbee.blakadder.com/ETOP_HT-10.html
From tuya TRV matrix:
E-top is making different software IDs for all customers.
OEM / Brand | Model | Manufacturer Name | Model ID | ZHA Quirk | Request -- | -- | -- | -- | -- | -- E-top | HT-10R-Z | _TZE200_2dpplnsn | TS0601 | ⭕ Moes I ? | E-top | HT-10R-Z | _TYST11_2dpplnsn | dpplnsn | ⭕ Moes II ? | Immax | 07703L | _TZE200_wlosfena | TS0601 | ⭕ Moes I ? | 691 Immax | 07703L | _TYST11_wlosfena | losfena | ⭕ Moes II ? | 691 Cloud Even | ? | _TZE200_0hg58wyk | TS0601 | ⭕ Moes I ? |Thank you very much for looking into this :)
Hello, are there any updates on this topic? otherwise I will probably return the TRVs to the seller soon. The deadline for returning is over soon. thank you in advance
I do it in a free time, so there's no strict deadline. You decide.
ok I think I will just wait a little bit longer. If you have spare time until then I would be happy if you can look into this if not it is of course also no problem. I just wanted to know if there is any chance that this can be realised. If there were none I would have send it back now. So thank you again for the help and I am looking forward to a potential solution :)
First version of the quirk. Bugs possible, so enable DEBUG logging and post the logs in case of errors. BTW post the logs of pairing process and 10 minutes after, using quirk below.
logger:
default: info
logs:
homeassistant.components.zha: debug
zigpy: debug
zhaquirks: debug
Restart HA after changes in configuration.yaml and quirk upload. ts0601_trv_etop.py.zip
Hi first thank you very much !!
I can successfully now set the Temperature i can also turn it on or off. after a while it get reely unresponive. If I set the temperature nothing happens an after some time it resets to the last set temperature. But sometimes it accepts the new one. With a automation which sets constantly the new temperature it accepts it after a while The battery state isn't successfully recognised.
Also I cant set the modes schedule/away/manual through the user interface however here it can be changed:
more:
@HAuser1234 Again. I need pairing logs from HA - not pairing window. Enable DEBUG level first and restart HA. Remove device from HA first. I need logs of pairing process and still wait for 10 minutes. After you pair TRV device still sends data in background - that's why we need to wait. DON'T CUT ANYTHING from the logs. You can download logs from HA settings - it's somewhere there - just click download as file. Post it here as a file.
As for other errors just post here part of the logs of time you see the error. Best +/-5 minutes - so I can see what happened before and after.
Same for other functions you want to have. Take a break[for logs clearness] Switch something on TRV Post here part of the logs with that action +5 minutes. Zigbee is slow - when you switch something on TRV then HA gets it after even 10-15 seconds. It can take even longer if the device is far away from coordinator and data need to jump over 2 or 3 routers first. We need that extra log time for that purpose - 5 minutes is safe enough.
ok thanks I wast sure what info is needed Thats the pairing logfile: home-assistant_2023-01-19T07-23-53.570Z.log I have captured it but wast sure if this was it
The delay is still there but only sometimes. At the moment it works fine. Only if I turn it of and then on it takes 30 s for it to turn on in reality. Changing the temperature is much faster but sometimes it has the same problem. I can record this when it happens again.
One thing do you see any option for open window detection to turn on or off? There should be one according to the manual. The problem is that this is tured off bei default
You can post here all problematic parts of the log.
Here you get an error that command could not be sent because of coordinator can't find the route to the TRV -> NWK_NO_ROUTE Check your topology and
2023-01-19 08:17:03.967 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xAB30](TS0601): failed to set attribute: value: False attribute: 1026 cluster_id: 61184 endpoint_id: 1 Request failed after 5 attempts: <Status.NWK_NO_ROUTE: 205>
You link quality LQI is about 85, probably in 255 max scale. That could be reason of late delivery. Check you routers/repeaters around. Maybe some nearby router need to be re-enabled from power.
2023-01-19 08:17:27.377 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xAB30), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=0, profile_id=260, cluster_id=61184, data=Serialized[b'\ta\x02\x00Y\x10\x02\x00\x04\x00\x00\x00\xb4'], tx_options=<TransmitOptions.NONE: 0>, radius=27, non_member_radius=0, lqi=84, rssi=None)
Open window detection never will work properly. TRV is to close to the hot heater. My TRVs reported temp properly when I've put them in the freezer. Many users tried this. Nevertheless I've seen that under 0x0108 attribute:
2023-01-19 08:08:58.165 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0108 (command 0x0002)
Can make sensor of it. But usability probably won't be good.
[edit] Is that a function to turn on/off???? Or just window detection sensor?
ok thank you I have checked most devices on my network have interestingly such a low LQI even those near the main point Maybe I add a usb extension cable. Probably the antenna inside the server rack is not a good Idea, however the other devices dont seem to have a problem with the low LQI score Even the thermostats now react suddenly faster. I have observed this behavior also on door sensors and PIR sensors. Maybe it is a zigbee rerouting thing I dont know.
according to the manual it is a on/off thing, not a sensor. I see that there are issues with that detection, is it a lot of work to enable it to try it out here. The Valve is directly under the window in my house.
Steel rack case is an isolator. Zigbee re-routs all the time, but it's mainly when you add a mains powered device, which acts as a router. Sometimes is best to wait 2-3 hours. You can click after time a topology view and see a connections between devices. Bulb or Zigbee socket is a router. Cheapest solution is to add repeater - IKEA have one cheap device - have one in my network. https://www.ikea.com/pt/en/p/tradfri-signal-repeater-10400408/
Every mains powered device, which acts as a router you can check children LQI under device card in HA. 3 dots button -> Manage Zigbee Device -> Neighbor devices Check LQI to the next router or Coordinator
W can make it a switch. Later evening, off my local time. There will be no name on the switch - not possible to name it technically.
ok thank you very much! The zigbee socket/router next to the antenna has also only 85 LQI I probably will simply add a usb extensioncable to the HA server and put the antenna outside. I was before wondering how everything worked so well with the antenna inside there😂 Probably all works because there are ~20 routers as sockets or cover controllers on my network. I have checked the router yes the stronges connection seems to be only 80 I will change that for sure thank you so much!
That the switch is not named is really no problem. Do you know how to get the operating preset mode 0/1/2 to be controlled by HA since it can be set through the zigbee device managemet option(?)
I've myself switched from Sonoff Zigbee Bridge to Zigbee 3.0 USB Dongle plus E version - it has 20 dBm by default Recently had also Slaesh's CC2652RB stick. One thing to notice is also frequency overlapping between Zigbee and WiFi[and Bluetooth too] They both work on 2.4GHz https://www.metageek.com/training/resources/zigbee-wifi-coexistence/ Best is to wisely choose channels for both.
Do you know how to get the operating preset mode 0/1/2 to be controlled by HA since it can be set through the zigbee device managemet option(?)
Yes - @MattWestb would need to help you with it. Patch to HA file is needed as I remember correctly. Patched file will make the Preset drop-down list to appear for your TRV.
ok thank you for the information. I will look further into this! I have a wifi 6 mesh network with beamforming antennas, which would mean that the wifi intensity is really uneven within the house as well as multiple wifi channels are used at the same time when I understand that correctly. A probably pretty hard environment for zigbee. Oh that would be great if that would work!
@jacekk015 Numbers and functions for the preset and i patching one current file for ZHA.
@MattWestb _TZE200_0hg58wyk
value == 0:
operation_preset = self.Preset.Manual
value == 1:
operation_preset = self.Preset.Away
value == 2:
operation_preset = self.Preset.Schedule
climateE-top.zip
Added all 5 E-top devices i have found.
Copy into the HA container /usr/src/homeassistant/homeassistant/components/zha/climate.py
(make one backup of the original if somthing is going wrong).
Normal is the HA config folder at /config/
.
So if putting the file in your HA config folder you can using cp /config/climate.py /usr/src/homeassistant/homeassistant/components/zha/climate.py
inside the container for doing that and then restarting HA
@HAuser1234 Battery state - that TRV doesn't report battery level in percent. It alarms only if power is low, so probably you will need to wait for reaction when battery will be empty. None of your logs contain 0x0523 attribute report, so the TRV just doesn't report if all is OK Replace the quirk and restart HA - you should see a switch -> Window detection function. ts0601_trv_etop.py.zip
There seems to be a bug in there the thermostat is not recognised anymore home-assistant_2023-01-20T09-18-19.764Z.log (all logs after restart and a new binding of one thermostat) no entitys are found in this thermostat
Yes. Small bug was there. ts0601_trv_etop.zip
ok thank you very much it works now!
what should that mean? (unbekannt = unknown)
@MattWestb
climateE-top.zip Added all 5 E-top devices i have found. Copy into the HA container
/usr/src/homeassistant/homeassistant/components/zha/climate.py
(make one backup of the original if somthing is going wrong). Normal is the HA config folder at/config/
. So if putting the file in your HA config folder you can usingcp /config/climate.py /usr/src/homeassistant/homeassistant/components/zha/climate.py
inside the container for doing that and then restarting HA
does this come eventually in the official release or do I have to copy that in myself?
The HVAC action is one left over from not having patched climate.py and you can deleting it. Until some one can writing tests for all tuya TRVs is the maintainer not accepting merging of this quirks. I have trying getting the updated climate.py for other tuya TRVs but no luck getting them merged so need applying patching every HA update and hoping ZHA is not braking it and must redoing the patch.
Ah ok thank you
Unfortunately your TRV doesn't send any state of TRV or valve. unbekannt is because that is unsupported. Z2M and your logs show one attribute 0x0403 which changes from [0] to [1] https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices/tuya.js#L2329
Maybe that's the state, but strange if Z2M didn't check that. You, as an owner of the TRV, can only check if that value switches if the TRV goes from heating to idle and back.
2023-01-19 08:08:58.056 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:09:13.566 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:09:24.529 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:09:30.641 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [1] for attribute 0x0403 (command 0x0002)
2023-01-19 08:09:51.662 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:09:57.757 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [1] for attribute 0x0403 (command 0x0002)
2023-01-19 08:10:43.655 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:10:48.881 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [1] for attribute 0x0403 (command 0x0002)
2023-01-19 08:11:37.403 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:11:37.561 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:11:37.830 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:11:47.612 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:11:58.561 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:12:09.561 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:12:20.589 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:12:31.586 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:12:42.584 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:04.562 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:15.565 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:26.574 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:37.561 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:48.589 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
2023-01-19 08:13:58.566 DEBUG (MainThread) [zhaquirks.tuya] [0xab30:1:0xef00] Received value [0] for attribute 0x0403 (command 0x0002)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I have baught a Cloud Even TRV and discovered that there is no support yet in ZHA I would be very glad if you can implement this TRV in a Quirk!
I have attached:
Link to the TRV https://www.ebay.de/itm/155337234865?hash=item242ad219b1:g:HxAAAOSwlhZjsVQg&amdata=enc%3AAQAHAAAAoISDpicDt6I%2Fe791mFplU2NF1exk2zrxAshFQvAlbZ73dvXwmzCsD7m5Vged3vjHI4dCOyQo6przUfAkAmWmZGrFvWKL3Ki013kZIqUSnolu8fDvDMWmi4P%2B3pmkd4utooM6pM1DPFgkijhCSClt8grjc2blAWUQo3%2B6b3VUr2W2uzvkrBG460g2Ee8xk%2FOpZZMWi5RR4i5HR2%2FO11zBRRs%3D%7Ctkp%3ABk9SR7Cts4SvYQ#rpdCntId
If you want any further information I am happy to provide that
Device signature
```json { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```json { "home_assistant": { "installation_type": "Home Assistant Supervised", "version": "2023.1.0", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "5.10.0-13-amd64", "supervisor": "2022.12.1", "host_os": "Debian GNU/Linux 11 (bullseye)", "docker_version": "20.10.21", "chassis": "desktop", "run_as_root": true }, "custom_components": { "indego": { "version": "3.8.1", "requirements": [ "pyIndego==2.0.30" ] }, "zha_toolkit": { "version": "v0.8.28", "requirements": [ "packaging>=20.8", "pytz" ] }, "tapo_control": { "version": "4.2.1", "requirements": [ "pytapo==2.8", "onvif-zeep-async==1.2.0" ] }, "hacs": { "version": "1.28.3", "requirements": [ "aiogithubapi>=22.2.4" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.5", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.90", "zigpy-deconz==0.19.2", "zigpy==0.52.3", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 25095, "manufacturer": "_TZE200_0hg58wyk", "model": "TS0601", "name": "_TZE200_0hg58wyk TS0601", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4098, "power_source": "Battery or Unknown", "lqi": null, "rssi": null, "last_seen": "2023-01-06T18:52:40", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional logs
Device detection log: ```python Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=