Monatsrückblick Januar/Februar 2026 ist online!

[Ein ehemaliger Benutzer]

Hi
nutze einen Avatto Zigbee Türsensor (Tuya) und mit Adapterversion 1.5.6 wurde er als TS0203_TZ3000_402jjyro angelernt.

Er funktionierte nicht perfekt (Batteriefüllstand) aber die wichtigsten Dinge wie der Kontakt war nutzbar:

Durch ein Thermostatventil brauchte ich die aktuellste GithubVersion des Adapters und dies funktionierte (Ohne neues Pairen des Türsensors) auch bis zur GithubVersion von ca. vor einer Woche. Aber mit aktuellen Versionen liefert der Türsensor keinen DP mehr für den Kontakt. Löschen&Pairen brachte nichts, einzig ein Adapter auf 1.5.6 brachte ihn wieder in Funktion:

2021-12-05 13:45:22.333 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":84}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:45:22.336 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '84' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:45:22.345 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"contact":true,"tamper":false,"battery_low":false}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:45:22.348 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated 'true' from device b4e3f9fffe0e53cd for 'Contact event'
2021-12-05 13:45:22.349 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated 'false' from device b4e3f9fffe0e53cd for 'Is open'

Jetzt wieder den Adapter auf 1.6.7 aktualisiert und die wichtigen DPs vom Türsensor sind weg:

2021-12-04 11:28:18.940 - info: zigbee.0 (2115) debug devices set to ["b4e3f9fffe0e53cd"]
2021-12-04 11:28:19.513 - warn: zigbee.0 (2115) ELEVATED publishToState: message received '{"available":true}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-04 11:28:19.516 - warn: zigbee.0 (2115) ELEVATED publishToState: value generated 'true' from device b4e3f9fffe0e53cd for 'Available'
2021-12-04 11:28:19.519 - warn: zigbee.0 (2115) ELEVATED publishToState: message received '{"linkquality":10}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-04 11:28:19.521 - warn: zigbee.0 (2115) ELEVATED publishToState: value generated '10' from device b4e3f9fffe0e53cd for 'Link quality'

Woran liegt es? Im Code (Tuya.js) findet sich zum TS0203 (Einzig enthaltener TS0203) keine Änderung und auch der Changelog sagt dazu nichts:

{
        zigbeeModel: ['TS0203'],
        model: 'TS0203',
        vendor: 'TuYa',
        description: 'Door sensor',
        fromZigbee: [fz.ias_contact_alarm_1, fz.battery, fz.ignore_basic_report, fz.ias_contact_alarm_1_report],
        toZigbee: [],
        exposes: [e.contact(), e.battery_low(), e.tamper(), e.battery()],
        whiteLabel: [{vendor: 'CR Smart Home', model: 'TS0203'}],
        configure: async (device, coordinatorEndpoint, logger) => {
            try {
                const endpoint = device.getEndpoint(1);
                await reporting.bind(endpoint, coordinatorEndpoint, ['genPowerCfg']);
                await reporting.batteryPercentageRemaining(endpoint);
            } catch (error) {/* Fails for some*/}
        },
    },

Lt. Protokoll wird er dem Vendor: CR Smart Home also diesem Eintrag zugeordnet unter Adapterversion 1.5.6, oder?:

2021-12-05 13:42:50.424 - info: zigbee.0 (30223) Zigbee: allowing new devices to join.
2021-12-05 13:43:23.777 - info: zigbee.0 (30223) Starting interview of '0xb4e3f9fffe0e53cd'
2021-12-05 13:43:23.917 - warn: zigbee.0 (30223) Device '0xb4e3f9fffe0e53cd' announced itself
2021-12-05 13:43:39.403 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"available":true}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:39.406 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated 'true' from device b4e3f9fffe0e53cd for 'Available'
2021-12-05 13:43:39.407 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":10}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:39.409 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '10' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:39.441 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:39.444 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:40.157 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":75}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:40.160 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '75' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:40.917 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:40.919 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:41.668 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":75}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:41.670 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '75' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:42.500 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:42.502 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:43.191 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":75}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:43.193 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '75' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:43.954 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:43.957 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:45.514 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":57}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:45.517 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '57' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:46.227 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:46.229 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:47.006 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"linkquality":78}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:47.009 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated '78' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 13:43:47.019 - warn: zigbee.0 (30223) ELEVATED publishToState: message received '{"contact":true,"tamper":false,"battery_low":false}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 13:43:47.021 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated 'true' from device b4e3f9fffe0e53cd for 'Contact event'
2021-12-05 13:43:47.024 - warn: zigbee.0 (30223) ELEVATED publishToState: value generated 'false' from device b4e3f9fffe0e53cd for 'Is open'
2021-12-05 13:43:49.116 - info: zigbee.0 (30223) Successfully interviewed '0xb4e3f9fffe0e53cd', device has succesfully been paired
2021-12-05 13:43:49.118 - info: zigbee.0 (30223) Device '0xb4e3f9fffe0e53cd' is supported, identified as: CR Smart Home Door sensor (TS0203)

Zum Device TZ3000_402jjyro finde ich leider nichts, wird also offiziell nicht unterstützt, oder doch? Ist also als neues Gerät erst anzufragen/zu implementieren und alles vorher war ..... mehr oder weniger "Zufall"?

Thx!

[Ein ehemaliger Benutzer]

mit der aktuellen 1.6.8 von heute Nachmittag und dem herdsmann converter 14.0.339 funktioniert der Kontakt wieder:

2021-12-05 20:04:42.679 - warn: zigbee.0 (4994) ELEVATED publishToState: message received '{"linkquality":135}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 20:04:42.682 - warn: zigbee.0 (4994) ELEVATED publishToState: value generated '135' from device b4e3f9fffe0e53cd for 'Link quality'
2021-12-05 20:04:42.684 - warn: zigbee.0 (4994) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandStatusChangeNotification\",\"data\":{\"zonestatus\":0,\"extendedstatus\":0},\"linkquality\":135,\"groupID\":0,\"cluster\":\"ssIasZone\",\"meta\":{\"zclTransactionSequenceNumber\":101,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 20:04:42.685 - warn: zigbee.0 (4994) ELEVATED publishToState: value generated '"{\"type\":\"commandStatusChangeNotification\",\"data\":{\"zonestatus\":0,\"extendedstatus\":0},\"linkquality\":135,\"groupID\":0,\"cluster\":\"ssIasZone\",\"meta\":{\"zclTransactionSequenceNumber\":101,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"' from device b4e3f9fffe0e53cd for 'Message from Zigbee'
2021-12-05 20:04:42.691 - warn: zigbee.0 (4994) ELEVATED publishToState: message received '{"contact":true,"tamper":false,"battery_low":false}' from device b4e3f9fffe0e53cd type 'TS0203'
2021-12-05 20:04:42.693 - warn: zigbee.0 (4994) ELEVATED publishToState: value generated 'true' from device b4e3f9fffe0e53cd for 'Contact event'
2021-12-05 20:04:42.694 - warn: zigbee.0 (4994) ELEVATED publishToState: value generated 'false' from device b4e3f9fffe0e53cd for 'Is open'

Was wie warum wird mich natürlich trotzdem sehr interessieren.