TS011F _TZ3000_okaz9tjs plug No Energy Consumption and no OTA update #20028
Comments
|
I have these too, _TZ3000_okaz9tjs TS011F_plug_1, same firmware version, same firmware update failure message. They also report current in mA instead of A, but Z2M doesn't know that and displays thousands of amps. I've verified with a current meter that it's accurate in mA. But it seems a bit strange to me that energy consumption isn't reported for these plugs. I also have a few _TZ3000_gvn91tmx (also TS011F_plug_1) that report it correctly, seemingly through messages like: The _TZ3000_okaz9tjs report the same message but that's not picked up somehow: I'm not sure if I understand all of this correctly but to me it seems that the messages are practically identical but just not picked up at all for the latter plug. Haven't done many tests with them either so I'm not sure if it reports in the same units (divisor) but I believe it should have been exposed in the state regardless. My setup is Z2M (docker) 1.34.0 aae7312, Sonoff ZBDongle-E running coordinator 6.10.3.0 build 297. |
|
I also bought 3 plugs (the only one i already tested) present same symptoms, is there any way to push the firmware upgrade manually to check if it's firmware issue? Mine shows in z2m as manufacturer: |
|
i have the same issue.
|
|
Have the same problem. Following |
|
I also have a few problems with the _TZ3000_okaz9tjs plug. None of these issues are present with the _TZ3000_gvn91tmx plug, so I hope it is all fixable. I especially hope so after reading @DataGhost's comment as the information is published. I am also on 1.34.0 using a Sonoff ZBDongle-E.
This error might be related with me trying to set this attribute once. But generally the reporting seems to be awry; for one of my okaz9tjs's the reporting tab is completely empty. |
|
still the same probleme here with my: Zigbee2mqtt Version 1.34 |
|
Have the same problem. Following. { Zigbee Model: TS011F |
|
Could you provide the data/database.db entry of this device? |
|
I hope this is what you are looking for: {"id":42,"type":"Router","ieeeAddr":"0xa4c138c399331e03","nwkAddr":37314,"manufId":4107,"manufName":"_TZ3000_okaz9tjs","powerSource":"Mains (single phase)","modelId":"TS011F","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,3,4,5,6,10,57344,1794,2820,4096,6280],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"hwVersion":0,"manufacturerName":"_TZ3000_okaz9tjs","zclVersion":3,"appVersion":112,"modelId":"TS011F","powerSource":1}},"genOnOff":{"attributes":{"32768":0,"onOff":1,"tuyaBacklightMode":1,"moesStartUpOnOff":0,"onTime":0,"offWaitTime":0}},"haElectricalMeasurement":{"attributes":{"rmsVoltage":226,"rmsCurrent":178,"activePower":15}},"seMetering":{"attributes":{"currentSummDelivered":[0,491]}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x00124b0021cc41b2","endpointID":1},{"cluster":2820,"type":"endpoint","deviceIeeeAddress":"0x00124b0021cc41b2","endpointID":1},{"cluster":1794,"type":"endpoint","deviceIeeeAddress":"0x00124b0021cc41b2","endpointID":1}],"configuredReportings":[{"cluster":2820,"attrId":1285,"minRepIntval":5,"maxRepIntval":3600,"repChange":5,"manufacturerCode":null},{"cluster":2820,"attrId":1288,"minRepIntval":5,"maxRepIntval":3600,"repChange":50,"manufacturerCode":null}],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":112,"stackVersion":2,"hwVersion":0,"swBuildId":"0122052017","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1702319383019,"defaultSendRequestWhen":"immediate"} |
|
Could you check if the issue is fixed with the following external converter:
external_converters:
- ext_converter.js
|
|
Ok. Now energy reporting is working! The device is missing on the OTA page. |
|
We don't have an OTA for this device, to get it see https://www.zigbee2mqtt.io/advanced/more/tuya_xiaomi_ota_url.html |
|
No problem. Thanks a lot for your help and all your work. |
|
That fixes the issues for me as well, except that it's now reported as BSD29_1 with an incorrect picture. If I understand it correctly, it's now only polling the energy? But I'm curious though, why the energy messages I saw in my logs were not picked up. It seems to indicate that those plugs shouldn't require any polling. |
I can confirm these observations. But I still have empty reporting tabs for the _TZ3000_okaz9tjs plug: While it looks like this for the _TZ3000_gvn91tmx plug: Manually trying to set activePower for haElectricalMeasurement leads to the following error: |
|
I think it's much simpler. Looks to be entirely related to #19680 (comment). We're seeing the same INVALID_DATA_TYPE error there. It seems that after using the external converter linked in this thread the plugs kept reporting or getting polled for energy, even with the external converter unloaded (unless I messed up somewhere). So I removed one of the devices from the network, restarted Z2M, re-added it so it was back to the old (wrong) behaviour and verified it was again reporting current incorrectly, and no energy. I then added my own external converter, basically a copy of TS011F_plug_1 from tuya.ts, but extended the check https://github.com/Koenkk/zigbee-herdsman-converters/blob/0c21893dd438aeb2b5fb26b78ee1d5b4f6bc2684/src/devices/tuya.ts#L3294 to include this device manufacturer. This made it configure properly, after which energy became available (I guess without any polling). That also fixed the current measurement. Probably because those two were going to be set up only after that error. I could make a patch/PR but the change is basically: and I'm not sure if that's all the way up to coding style etc. It also doesn't fix OTA which will remain unavailable for this specific device until someone pulls the image (if available) and I'm unsure if showing the imagetype error is considered problematic. Edit: the one in 19680 has the same imagetype so I guess they're the same plugs and this OTA error message isn't considered important then. Also, this small extra check fixed the reporting tab too: |
|
@DataGhost Would you mind posting your converter somewhere? I am not really familiar with JavaScript and somehow always mess up the syntax :( |
|
@allthesebugsv2 I made a small change to it (removed "160, 100, 69, 68, 65, 64, " from the fingerprint map) to hopefully minimise the possible side-effects for other "unrelated" plugs (which I don't have but other people might) but otherwise this is what I'm using now: https://gist.github.com/DataGhost/572e79e08c0e7eb22773f54c1648b263 |
|
@DataGhost thank you very much, that works very well! The only thing not working (and I guess we explicitly turn that off with the converter) is setting different reporting intervals (or minimal reported changes) for activePower. Which is a shame since that is the most interesting measurement, at least for me. Anyone any idea how to get reporting settings working for activePower? |
|
I have no clue, very little experience with Z2M (in terms of code), I don't have any thing / experience to debug the protocol either. I assume if it was trivial for the plugs in the other issue, that would have been chosen instead. I personally don't use the reporting tab so I'm not sure what you'd want to change there, for me it's reporting the way I want it to report. |
|
What I am interested in is altering the minimal reported change in terms of wattage (or activePower). If I use devices with low power usage, changes in their power usage are not picked up (or rather at some fixed interval). With the _TZ3000_gvn91tmx plugs I can set the minimal reported change to 1 W, picking up even small changes in power usage. |
|
@DataGhost looks good, could you make a PR? (https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts) |
|
Sure. Just checking because I see another plug in this thread: @pjanuario @kennerblick @CoccoAndrea could either of your verify that my updated gist https://gist.github.com/DataGhost/572e79e08c0e7eb22773f54c1648b263 used as an external converter works for your _TZ3000_typdpbpg plugs? @Koenkk I assume they're affected by the same thing so I'll include those plugs in the PR as well, but you might want to wait to get confirmation obviously. |
|
Hi all, |
|
You don't need to build anything. When the PR I opened is approved, you'll be able to see that in this ticket and the fix should then appear in the next release which is generally the 1st of the month I believe. If you can live with only power and voltage reporting for now you don't need to do anything. But if you really want correct energy and current reporting right now, you'll have to use the external converter linked two comments up. |
Sorry I was traveling and with a lot of work. |
I guess this is the answer to my question right? |
|
I just did a quick try to test it, but got some errors related with dependencies. |
|
@pjanuario That should be it yes, save the gist as some .js file and reference it in the config under external_converters, just as described in #20028 (comment). It shouldn't throw any dependency errors, so something must have gone wrong there. Unless you post those errors there's no way to know what, though. In any case, it's merged now, so if you're running Z2M in docker, an alternative is to use the latest-dev docker image and see if that fixes your plugs. And afterwards obviously revert to latest or whatever you were using. |
|
Im not sure why, I also have this _TZ3000_okaz9tjs, look different and original it was _TZ3000_cehuw1lw and yes it also does not measure power it looks like, to me as I ordered the same Item looks like bake and switch thing Super happy with the original _TZ3000_cehuw1lw and I see the same for other Items, ones it sell they swap out with different models |
What happened?
I have 3 of these plugs. They are paired and they show as TS011F _TZ3000_okaz9tjs / [TS011F_plug_1].
They report Power, Current and Voltage bur no Energy (appears as "null").
Also the FW version is 0122052017 and when I check for updates I get "Failed to check if update available (No image available for imageType '524').
What did you expect to happen?
Have energy metering.
Update FW OTA.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.34.0
Adapter firmware version
20230507
Adapter
Slaesh CC2652RB
Debug log
Info 2023-12-04 22:47:40MQTT publish: topic 'zigbee2mqtt/TV plug', payload '{"child_lock":"UNLOCK","current":231,"energy":null,"indicator_mode":"off/on","linkquality":109,"power":16,"power_outage_memory":"off","state":"ON","update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null,"voltage":226}'
The text was updated successfully, but these errors were encountered: