Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.03k stars 1.67k forks source link

[Wrong device]: TS011F_wall_outlet turned into TS011F_plug_3 after the update zigbee2mqtt 1.35.2-1 #21193

Open AlexzeyK opened 8 months ago

AlexzeyK commented 8 months ago

Link

https://www.zigbee2mqtt.io/devices/TS011F_wall_outlet.html

Model

BSEED Zigbee Socket

Description

Zigbee EU Wall Socket

Vendor

BSEED (TuYa)

Picture (link)

https://ae01.alicdn.com/kf/H8fddddf2e4974dbcaf1de394e9e99452t.jpg

Database entry

"id":4,"type":"Router","ieeeAddr":"0xa4c138fb9c8d1217","nwkAddr":28733,"manufId":4417,"manufName":"_TZ3000_o1jzcxou","powerSource":"Mains (single phase)","modelId":"TS011F","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":266,"inClusterList":[3,4,5,6,57344,57345,0],"outClusterList":[25,10],"clusters":{"genOnOff":{"attributes":{"32768":0,"onOff":0,"onTime":0,"offWaitTime":0,"tuyaBacklightMode":1,"moesStartUpOnOff":2,"tuyaBacklightSwitch":1}},"genBasic":{"attributes":{"65534":0,"stackVersion":0,"dateCode":"","manufacturerName":"_TZ3000_o1jzcxou","zclVersion":3,"appVersion":64,"modelId":"TS011F","powerSource":1}},"manuSpecificTuya_3":{"attributes":{"powerOnBehavior":2,"switchType":0}},"haElectricalMeasurement":{"attributes":{"acCurrentDivisor":1000,"acCurrentMultiplier":1}},"seMetering":{"attributes":{"divisor":100,"multiplier":1}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2123427102},"lastSeen":1706971135418

Notes

In the previous version zigbee2mqtt 1.35.1-1 the outlet was detected correctly and worked (controlled) correctly. outlet

After the update 1.35.2-1 the socket appeared as a plug with energy monitoring. outlet_n

now the control doesn't work. Only the signal level is correctly displayed.

"child_lock": null,
"current": null,
"energy": null,
"indicator_mode": null,
"linkquality": 124,
"power": null,
"power_outage_memory": null,
"state": null,
"update": {
    "installed_version": -1,
    "latest_version": -1,
    "state": null

"update_available": null,
"voltage": null,
"last_seen": "2024-02-03T17:33:29+02:00"

is automatically mapped to the wrong converter.

Koenkk commented 8 months ago

This is because of https://github.com/Koenkk/zigbee2mqtt/issues/20702 (@franele), does your device work correctly in 1.35.2?

AlexzeyK commented 8 months ago

i ignored version 1.35.2 and upgraded from 1.35.1-1 to 135.2-1. I don't have a backup from 1.35.2 to check. i installed 1.35.2 on a separate server. 1PNG

i received the wrong device as in 1.35.2-1 image

but! in this version the switch works! there are no errors in the logs.

https://github.com/Koenkk/zigbee2mqtt/assets/77577796/660e583a-cb1b-46b6-ac41-109bb4f32568

the data/database.db entry in 1.35.2: "id":2,"type":"Router","ieeeAddr":"0xa4c138fb9c8d1217","nwkAddr":38317,"manufId":4417,"manufName":"_TZ3000_o1jzcxou","powerSource":"Mains (single phase)","modelId":"TS011F","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":266,"inClusterList":[3,4,5,6,57344,57345,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65534":0,"modelId":"TS011F","manufacturerName":"_TZ3000_o1jzcxou","powerSource":1,"zclVersion":3,"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":""}},"haElectricalMeasurement":{"attributes":{"acCurrentDivisor":1000,"acCurrentMultiplier":1}},"seMetering":{"attributes":{"divisor":100,"multiplier":1}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2123427102},"lastSeen":1707051397830}

AlexzeyK commented 8 months ago

this is a record of a working outlet from the version 1.35.1-1 database: "id":3,"type":"Router","ieeeAddr":"0xa4c138fb9c8d1217","nwkAddr":58137,"manufId":4417,"manufName":"_TZ3000_o1jzcxou","powerSource":"Mains (single phase)","modelId":"TS011F","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":266,"inClusterList":[3,4,5,6,57344,57345,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS011F","manufacturerName":"_TZ3000_o1jzcxou","powerSource":1,"zclVersion":3,"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":""}},"genOnOff":{"attributes":{"32768":0,"onOff":0,"onTime":0,"offWaitTime":0,"tuyaBacklightMode":1,"moesStartUpOnOff":2,"tuyaBacklightSwitch":1}},"manuSpecificTuya_3":{"attributes":{"powerOnBehavior":2,"switchType":0}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1707043545757,"defaultSendRequestWhen":"immediate"

I see that 2 different devices have the same registration details. so the problem is with the converter.

franele commented 8 months ago

This is because of #20702 (@franele), does your device work correctly in 1.35.2?

Hello, the devices work correctly. I have tested the on/off function and it works correctly. The energy monitoring still does not work, until today I have not been able to test it. I'm pairing the devices again...

s482dcaw commented 7 months ago

Adding here that one side effect from this change is that now devices show a new firmware is available. The firmware cannot be installed and fails, which is probably expected as it is a different device. image image

rosicenko commented 7 months ago

I have same device and it shows as TS011F_plug_1. Controlling functions well but metering was firstly showing only N/A and after OTA update I receive constant 0 for all parameters. image

rosicenko commented 7 months ago

So I just contacted BSEED and regarding to them they have 2 different sockets. One is with metering and another without any metering. They told me this specific one is without metering capabilities. That means it works in Z2MQTT just fine.

derkorte commented 6 months ago

I've had a similar device as in wall socket without energy monitoring. Since updating it's also configured as plug with energy monitoring. Repair was no success. Here my log error:

Failed to configure 'Steckdose 4', attempt 1 (Error: Bind 0xa4c1380f62782395/1 haElectricalMeasurement from '0x00124b001cdcaac9/1' failed (Error: status: 130) at DeconzAdapter.bind (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:776:19) at Endpoint.bind (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:469:13) at Object.bind (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:43:9) at configure (/app/node_modules/zigbee-herdsman-converters/src/devices/tuya.ts:3771:13) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:162:21) at Configure.configure (/app/lib/extension/configure.ts:122:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))

Anyone knows how to fix?

github-actions[bot] commented 2 weeks ago

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days