[New device support]: TS0601 - _TZE200_cirvgep4 -- Smart Life/TuYa Temp, Humidity sensor and Clock with Backlit LCD #17008
Labels
new device support
New device support request
Comments
|
Bump? any help would be much appreciated. I've still been trying to setup the converter for this but haven't had any success |
|
Could you check if the issue is fixed with the following external converter: const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_bq5c8xfe'},
{modelID: 'TS0601', manufacturerName: '_TZE200_bjawzodf'},
{modelID: 'TS0601', manufacturerName: '_TZE200_qyflbnbj'},
{modelID: 'TS0601', manufacturerName: '_TZE200_cirvgep4'},
{modelID: 'TS0601', manufacturerName: '_TZE200_9yapgbuv'},
{modelID: 'TS0601', manufacturerName: '_TZE200_zl1kmjqx'}
],
model: 'TS0601_temperature_humidity_sensor',
vendor: 'TuYa',
description: 'Temperature & humidity sensor',
fromZigbee: [fz.tuya_temperature_humidity_sensor],
configure: tuya.configureMagicPacket,
toZigbee: [],
exposes: (device, options) => {
const exps = [e.temperature(), e.humidity(), e.battery()];
if (!device || device.manufacturerName === '_TZE200_qyflbnbj') {
exps.push(e.battery_low());
exps.push(exposes.enum('battery_level', ea.STATE, ['low', 'middle', 'high']).withDescription('Battery level state'));
}
exps.push(e.linkquality());
return exps;
},
};
module.exports = definition;
external_converters:
- ext_converter.js
|
|
Sorry for delay on this. Yes, your converter did properly apply to the device, I think my main issue was I was adding my converter to my root directory, while not realizing that it needed to be within the zigbee2mqtt directory. Although the converter is now applying correctly, it still isn't exposing any options and I haven't been able to figure out how to discover those values. |
can you make a screenshot of the exposes tab? |
|
|
|
Correction, LQI is reporting
|
|
Mine exposes most of the data: I just wonder, if it is possible to set the time as this rectangular version ( _TZE200_cirvgep4) has a time display. |
|
I updated #17008 (comment), can you try to: force remove the device through z2m frontend, restart z2m and re-pair the device? |
|
Hi, I've got the same device (_TZE200_cirvgep4) at home. With the provided external converter (#17008 (comment)) I'm able to pair the device and also get some values from it (temperature, humidity and linkquality). Unfortunately only the linkquality value changes. Temperature and humidity always showing 17.4 °C and 55 % over hours while the device shows different values on its display.
Do you have any idea, how to fix this? |
|
With the following external converter can you do the following.
Note: no values will change, this is expected |
|
Thank you for the instructions. I'm running z2m via docker on the latest version (v1.30.3). |
|
Whoops, updated https://gist.github.com/Koenkk/d6203adca293f76b03687ce3254f3a1e |
|
Thanks for the updated script. Now I was able to start z2m in debug mode and dump the following log: |
|
Thanks, can you provide the debug log when leaving the device connected for some time and then blowing into it (provide the log of just this), I want to see wether it reports a new temperature. I also updated https://gist.github.com/Koenkk/d6203adca293f76b03687ce3254f3a1e for the time sync. |
|
I tried the updated converter and waited some time before dumping the logs as suggested. Unfortunately the time sync does not seem to work... Also I noticed, that the display now doesnt show a temperature or humidity change if i blow into it. Only after restarting the device by removing and reinstalling the batteries it shows different values. |
That's strange, I guess that explains why I don't see any temperature/humidity updates in your log. Does it also do this when not being connected to zigbee2mqtt? |
|
I can confirm the behavior. |
|
I also confirm this behavior. Temperature and humidity are not updated. |
|
same device and same problem here |
|
Wondering if this is a lost cause? I really like the possibilities for this device - I was able to solder a USB cable to forego its need for batteries - very easy since it's a 3xAAA setup - just solder USB cable leads to each battery post and power with a 1A supply - good to go. But currently I am seeing the same - no updates on display and no updates in HA from the device. Anyone able to get further? |
Maybe this is the reason the device stops updating. If it expects to receive the time sync after pairing and this fails it locks up. Can we diagnose this any further? PCB for reference, serial runs on 2.8v, i'm unsure if i can safely connect a 3.3v uart? |
|
Hi |
|
I have two of these and would happily send one of them to you @Koenkk or someone else who would be able to progress this issue. Would that be helpful? |
|
Yes, the time does not sync, but changes. Temperature and humidity does not change at all untill restarting. |
|
Hi,
|
|
Hello, I'm also sitting in the same boat. |
I started like this, but after a few minutes it was like I sent earlier |
|
Hi there, I have the same module and I fail :( I have implemented the ext_converter.js from the gist, and I receive only the LQI. ext_converter.js const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_bq5c8xfe'},
{modelID: 'TS0601', manufacturerName: '_TZE200_bjawzodf'},
{modelID: 'TS0601', manufacturerName: '_TZE200_qyflbnbj'},
{modelID: 'TS0601', manufacturerName: '_TZE200_cirvgep4'},
{modelID: 'TS0601', manufacturerName: '_TZE200_9yapgbuv'},
{modelID: 'TS0601', manufacturerName: '_TZE200_zl1kmjqx'}
],
model: 'TS0601_temperature_humidity_sensor',
vendor: 'TuYa',
description: 'Temperature & humidity sensor',
fromZigbee: [tuya.fz.datapoints],
configure: tuya.configureMagicPacket,
toZigbee: [],
onEvent: tuya.onEventSetTime,
exposes: (device, options) => {
const exps = [e.temperature(), e.humidity(), e.battery()];
if (!device || device.manufacturerName === '_TZE200_qyflbnbj') {
exps.push(e.battery_low());
exps.push(exposes.enum('battery_level', ea.STATE, ['low', 'middle', 'high']).withDescription('Battery level state'));
}
exps.push(e.linkquality());
return exps;
},
meta: {
tuyaDatapoints: [
],
},
};
module.exports = definition;Here are some filtered logs: edit: time is still not set either. Can somebody please help me? :) |
After pair wait +- 20/30 minutes and look again the values |
|
great, with 1.33.1 sensor is working, except battery status!! thanks if anyone has a hint to get battery status working...pls let me know...already repaired the device....didnt help greets |
|
I have problem with this device as others, I can sucesfully pair it, sometimes I can even get data from it. But when it's paired and I click the top button to lid the screen, the data on screen stop updates. When I unpair it it starts to work till I pair it again. Any suggestions what I can do? |
|
Similar problem with 1.34.0 Very first time device was connected, time on display was set and it seems to work for some time. Logs from this time: Then it ceased to work. Logs from this attempt: Time on display is not set and updates are not provided. 
Network icon flicking showing attempts to connect. |
|
Do you have coordinator firmware up-to-date? I've updated my coordinator fw at that time too (to the latest). |
|
It's |
|
Update: Switched to dev branch (because of problems with _TZE204_upagmta9) and tried to add device again: And then it failed to be configured: But then was configured at which point correctly time was set on screen and it started to report parameters: Then I pressed on light button which caused network icon to flicker and device never reported anything again. Then I restarted z2m without deleting of the device: Nothing changed but published data contains temperature and humidity from the last report at 21:00:11 (which don't match current values on screen) but different linkquality. And then again - remove, reboot: Device added, time was set, changes in temperature and humidity were reported correctly as they was presented on screen. |
|
And then with debug logging. Then I pressed backlight button, connection icon started to flicker again, and in logs: Last messages were repeated after each next press of the backlight button. And this one after some time: |
|
Hi, i'm on Z2M 1.35.1 and i still don't have time sync working. Any solution ? |
|
I also bought this device because I thought it is supported.... But I do not get any data except link quality. Did several restarts , several force delete, several new pairing. Did NOT press the light button... I am on [1.35.1] commit: [9eaaa0f] Every help welcome. UPDATE: After another to restarts I got the temperature and humidity... It´s seems as difficult as my Aqara motion sensors P1 Mike |
|
I have these thermometers with WiFi for all my rooms. Since I now want to get away from the cloud completely and can't flash the thermometers to open beken, I'm currently in the process of switching them all to Zigbee. I've already bought 3 and just bought 10 that aren't here yet. I had initially integrated the thermometers with ZHA. But as soon as I pressed the button, nothing worked anymore and some things didn't work well anyway. That's why I switched to Z2M. Everything works great. It's just these thermometers that are giving me a headache.
|
|
@Koenkk I think you can add |
Koenkk
added a commit
to Koenkk/zigbee-herdsman-converters
that referenced
this issue
May 8, 2024
|
@vivalton done! |
i'am the only one with this problem now? short: did i have to do extra work for implement TS0601 - _TZE200_cirvgep4? Backlight Button permanently ends connection and short PowerLoss dont finds reconection |
@grericht I also have the same issue. I have read the comments of this issue with great attention and it seems that some people managed to get everything working : time, temp., humidity, link quality and even the problem you describe is fixed. It is quiet annoying to have this problem because I cannot tell people not to press this button especially with kids... I am willing to help but please guide me. I am not an expert it z2m, zigbee or tuya. |
|
Some update : I have added in my zigbee network two zigbee light bulbs (they act as routers). Before adding the light bulbs, I had all my temp. / humidity sensors "disconnected" (wifi symbol going up, not blinking). Now that I added the bulbs, it seems that the temp/hum. sensors connected to it auto-magically. |
|
That's exciting. For me it seems to be the other way around at the moment. The 4 sensors in the basement that are directly connected to the stick seem to be connecting themselves. All the others that are partially connected to repeaters are not connecting themselves. Or rather, most of them are connecting themselves but are not sending any data. z2m says he had contact a few seconds ago but no new data is coming into the Home Assistant. |
|
All, The most recent replies seem to suggest poor Zigbee networks or impatience in the reporting-period of said devices. Please do further research before adding to this fixed-issue. |
|
Original issue fully resolved |
|
Hi all, New development of things about _TZE200_cirvgep4 ... I have this weird Tuya (pleonasm!) device (_TZE200_cirvgep4) and experiencing the same behaviour when backlit button is clicked: network icon on device starts building up and temperature/humidity data is never reported back to z2m. Time is still present on display, but if I pull batteries off and on, this also stops working. It is probably not synchronized anyway. New observation: if button is pressed a second before "reconfigure" icon for device in z2m is pressed, device fully recovers without repairing (values are reported, time synces, network icon stops buildup). If reconfigure is called without pressing the button on device, this error appears in the ~10 seconds and device is not reconfigured: Interestingly, removing and putting back batteries is not causing this error nor need for reconfiguration: in a 1-2 minutes, time synchronizes and network symbol stops buildup. Now if only z2m get give that "something" to that weird device after button is pressed and screen illuminated. Many people bought this device because of nice backlit and time display. Better then SONOFF SNZB-02D on the first glance, with one small difference: SONOFF one works without voodoo. :-) EDIT: I have another one which is _TZE204_cirvgep4 on remote location. I minutes ago, I was able to get it back in life by brute forcing "reconfigure" 7-10 times hoping device will see message while not sleeping in some moment, which apparently happened. |
|
same mistake here |
|
Eh, now what I have I have, let's try to make it work before I give up ... Looks like workaround may be to start reconfigure on device announce. Now I need only to figure out for a workaround and further research, do that automatically ... probably by sending some mqtt message via automations in Home Assistant. EDIT: It works by sending |
|
I'm not much familiar with mqtt and zigbee but ... I'm aware this potato-styled workaround really sucks, but at least it justifies 3 devices and approx. 80€ spent on them. :-) I hope it will be useful to other misfortune people who brought this device. |
|
i think dont understand all. i have 14 of these devices. i have to write an automation for all of them? is there a chance to get a better integration of the device without automation? |
My automation is a workaround. It works for me, and it works surprisingly well. However, to make this in Zigbee2mqtt is up to developers. This is a logical flow in device itself. For example, yesterday I was changing batteries in my UPS and all was down, including Home Assistant and Zigbee2Mqtt. If this ZTH08-E is illuminated during that time, it will go in that endless "device_announce" mode and sucking all the battery in few days or hours if Z2M is not coming up to send it "configure". Logically, this sucks probably also with "intended" tuya zigbee coordinator, which I don't have. The right place to fix this is a firmware of the device itself. Zigbee2mqtt can only provide fix, or you can make it yourself as I did with Home Assistant automation above. |
Perfect! This logic works with OH rules as well. Thank you! |
|
Excuse me, but I have to ask again: what exactly does the script do and what does it help with? I have 11 of these thermometers in use. I have them hard-wired to 3.3v - that's enough. I have 2 problems:
Does the script help with either of the two problems? |
|
so for me the behavior of the thermometers looks like this: If I press the button once, then from that moment on it sends the same temperature and humidity the whole time. and that about every 5-10 seconds. That's probably why the battery runs out so quickly. for me nothing is posted in bridge/event only when I press the button for a long time and the signal symbol flashes completely, then the following is posted: {"data":{"friendly_name":"xyz","ieee_address":"0xyz"},"type":"device_leave"} and this causes the command the answer: {"data":{"id":"xyz"},"error":"Device 'xyz' does not exist","status":"error"} so the error seems to be that no "device announce" is posted for me. and unfortunately, posting does not seem to cause the device to start sending the correct temperature again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Link
https://www.aliexpress.us/item/3256805012073037.html?srcSns=sns_Copy&spreadType=socialShare&bizType=ProductDetail&social_params=20860570604&aff_fcid=f197f56d14424505a1711d26f8b5cab3-1678614555564-09999-_mPN4oRU&tt=MG&aff_fsk=_mPN4oRU&aff_platform=default&sk=_mPN4oRU&aff_trace_key=f197f56d14424505a1711d26f8b5cab3-1678614555564-09999-_mPN4oRU&shareId=20860570604&businessType=ProductDetail&platform=AE&terminal_id=bab527b0baa3498a868b1d3db53245c7&afSmartRedirect=y&gatewayAdapt=glo2usa4itemAdapt&_randl_shipto=US
Database entry
{"id":79,"type":"EndDevice","ieeeAddr":"0xa4c1380178ab4857","nwkAddr":25022,"manufId":4417,"manufName":"_TZE200_cirvgep4","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[4,5,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"\u0000\u0000\u0000\u0000\u0011","65506":56,"65508":1,"stackVersion":0,"dateCode":"","appVersion":72}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":72,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1678581068121,"defaultSendRequestWhen":"immediate"}
Comments
I tried setting up a TuYa converter for this item but haven't gotten anywhere. No real progress was made and I've edited it too many times, so I'm not including it below - pointless. I found this appears to be very similar, if not exactly the same device as the following link from Z2M's database of supported devices, but haven't been able to mask it as the same or get any usable output from the device. Any way to make my device report as the one below, if not just to test if the same datapoints report correctly?
https://www.zigbee2mqtt.io/devices/JM-TRH-ZGB-V1.html
External converter
No response
Supported color modes
No response
Color temperature range
No response
The text was updated successfully, but these errors were encountered: