TS0222 - Githubissues

poand commented 3 years ago

Hello, the following device does not provide me with any data:

model:TS0222 description:Light intensity sensor modelZigbee:TS0222 type:EndDevice nwk:9611 manuf id:4098 manufacturer:_TYZB01_4mdqxxnn power:Battery app version:70 hard version:1 zcl version:3 stack version:0 date code: interviewed:true configured:false

endpoint:1 profile:260 input clusters:genBasic (0) msIlluminanceMeasurement (1024) genPowerCfg (1) ssIasZone (1280) output clusters:genOta (25) genTime (10) Screenshot 2021-07-12 23 48 08 Screenshot 2021-07-12 23 48 26

asgothian commented 3 years ago

Please enter 84fd27fffcc8f4fe (the name of the device in the object tree) to the state zigbee.0.info.debugmessages and check the log for warn messages containing the keyword ELEVATED. (no adapter restart required)

Also check the log if from adapter startup if the device is listed as needing configuration.

If the device has a button which you can press to "wake" the device please do. This should lead to messages in the log file.

Lastly, please post an image of your zigbee map (after it has fully generated).

A.

poand commented 3 years ago

After entering 84fd27fffcc8f4fe nothing happens: Screenshot 2021-07-13 08 50 44

After the restart: Screenshot 2021-07-13 08 44 49

TS0222 has a button, but nothing happens when you press it.

Here is the ZigBee map: Screenshot 2021-07-13 08 45 38

asgothian commented 3 years ago

Why do you post text logs as screenshot ?
Please modify the entry in debugmessages to 84fd27fffec8f4fa A.

poand commented 3 years ago

After restarting the adapter: `

2021-07-13 10:59:12.298 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true) -- 2021-07-13 10:59:12.315 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal 2021-07-13 10:59:12.314 - info: zigbee.0 (3852) Got terminate signal TERMINATE_YOURSELF 2021-07-13 10:59:12.318 - info: zigbee.0 (3852) cleaned everything up... 2021-07-13 10:59:12.323 - info: zigbee.0 (3852) Zigbee: disabling joining new devices. 2021-07-13 10:59:12.346 - warn: zigbee.0 (3852) ELEVATED publishToState: message received '{"available":false}' from device 84fd27fffec8f4fa type 'TS0222' 2021-07-13 10:59:12.347 - warn: zigbee.0 (3852) ELEVATED publishToState: value generated 'false' from device 84fd27fffec8f4fa for 'Available' 2021-07-13 10:59:12.348 - warn: zigbee.0 (3852) ELEVATED publishToState: message received '{"linkquality":0}' from device 84fd27fffec8f4fa type 'TS0222' 2021-07-13 10:59:12.348 - warn: zigbee.0 (3852) ELEVATED publishToState: value generated '0' from device 84fd27fffec8f4fa for 'Link quality' 2021-07-13 10:59:12.820 - info: zigbee.0 (3852) terminating 2021-07-13 10:59:12.821 - info: zigbee.0 (3852) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-07-13 10:59:13.321 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 killing pid 3852 2021-07-13 10:59:13.439 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-07-13 10:59:15.380 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 4017 2021-07-13 10:59:17.905 - info: zigbee.0 (4017) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16 2021-07-13 10:59:18.000 - info: zigbee.0 (4017) Starting Zigbee npm ... 2021-07-13 10:59:18.281 - info: zigbee.0 (4017) Installed Version: iobroker.zigbee@1.5.6 2021-07-13 10:59:20.039 - warn: zigbee.0 (4017) Extended PAN ID is reversed (expected=ae20c11c004b1200, actual=00124b001cc120ae) 2021-07-13 10:59:20.170 - info: zigbee.0 (4017) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210120}} 2021-07-13 10:59:20.178 - info: zigbee.0 (4017) Unable to disable LED, unsupported function. 2021-07-13 10:59:20.178 - info: zigbee.0 (4017) --> transmitPower : high 2021-07-13 10:59:20.187 - info: zigbee.0 (4017) Currently 2 devices are joined: 2021-07-13 10:59:20.209 - info: zigbee.0 (4017) 0x84fd27fffec8f4fa (addr 9611): TS0222 - TuYa Light intensity sensor (EndDevice) 2021-07-13 10:59:20.212 - info: zigbee.0 (4017) 0x847127fffe761959 (addr 58161): SEA801-Zigbee/SEA802-Zigbee - Saswell Thermostatic radiator valve (EndDevice) 2021-07-13 10:59:20.214 - info: zigbee.0 (4017) Zigbee started 2021-07-13 10:59:20.225 - info: zigbee.0 (4017) debug devices set to ["84fd27fffec8f4fa"] 2021-07-13 10:59:21.214 - warn: zigbee.0 (4017) ELEVATED publishToState: message received '{"available":true}' from device 84fd27fffec8f4fa type 'TS0222' 2021-07-13 10:59:21.215 - warn: zigbee.0 (4017) ELEVATED publishToState: value generated 'true' from device 84fd27fffec8f4fa for 'Available' 2021-07-13 10:59:21.216 - warn: zigbee.0 (4017) ELEVATED publishToState: message received '{"linkquality":10}' from device 84fd27fffec8f4fa type 'TS0222' 2021-07-13 10:59:21.217 - warn: zigbee.0 (4017) ELEVATED publishToState: value generated '10' from device 84fd27fffec8f4fa for 'Link quality' 2021-07-13 11:00:44.227 - warn: zigbee.0 (4017) Device '0x847127fffe761959' announced itself 2021-07-13 11:00:44.247 - warn: zigbee.0 (4017) Device '0x847127fffe761959' announced itself 2021-07-13 11:00:44.309 - warn: zigbee.0 (4017) Device '0x847127fffe761959' announced itself `

asgothian commented 3 years ago

Keep the adapter running, and try to trigger the device to send a message (by pressing its button if it has one, or shining a light straight at the device or putting it in a dark box.

A.

poand commented 3 years ago

Nothing happens. It doesn't matter whether I press the button or illuminate or darken it.

poand commented 3 years ago

The device worked before with the sonoff adapter with Tasmota zbBridge.

poand commented 3 years ago

Here with Sonoff ZigBee Bridge Tasmota and sonoff adapter: Screenshot 2021-07-13 12 37 07

asgothian commented 3 years ago

Unfortunately, there is little to nothing we can do. If no messages are printed in the log, the messages the device sends (if any) do not reach the zigbee-herdsman. It is possible that the implementation in the zigbee-herdsman-converters for this device is incorrect.

A.

poand commented 3 years ago

https://github.com/ioBroker/ioBroker.zigbee/wiki/Supported-devices

The TS0222 is listed as supported under this link.

asgothian commented 3 years ago

https://github.com/ioBroker/ioBroker.zigbee/wiki/Supported-devices

The TS0222 is listed as supported under this link.

Which means there is a set of converters which should work with the device. I cannot attest to how thoroughly this has been tested, and if the device you have actually behaves the same as the device the developer had when implementing it. We are talking about a TuYa device after all.

Things you can try now:

Verify the zigbee network (what channels are you using, what wifi 2.4gHz channels are in use)
pair the device again and record the communication. The device must provide link quality messages after pairing. If it does not, it does not send the messages towards the coordinator and may need a configuration
open an issue at zigbee-herdsman-converters. Maybe a developer there knows how to get the device to act again.

A.

ioBroker / ioBroker.zigbee

TS0222 #1156