Problema Zigbee2mqtt

Dúvidas
#1

Bom dia.
Estou a tentar adicionar sensores tuya com protocolo zigbee ao zigbee2mqtt edge (edge porque me reconheceu mais sensores que a versão normal). Tenho um sensor de qualidade de ar e tenho alguns sensores magnéticos de porta, ambos tuya e descritos como compatíveis com zigbee2mqtt no site blakadder (daí os ter comprado). Consigo adicioná-los, mas dá-me erro de não suportado. Entretanto vi que é possível adicionar novos aparelhos não suportados, através de ficheiros “zigbee-herdsman-converters”.
O meu sistema é o seguinte:
Sistema instalado em box android h96 como descrito aqui no fórum,
Home Assistant Core version core-2021.9.7
Supervisor version supervisor-2021.10.6
Operating System Debian GNU/Linux 11 (bullseye)
Docker Version: 20.10.8

Após usar ficheiro de dispositivo tuya (colocado em ‘config/zigbee2mqtt’) presente em repositório git https://github.com/Koenkk/zigbee-herdsman-converters, tenho o seguinte log de erro no zigbee2mqtt:

[zigbee2mqtt@1.21.0-dev](mailto:zigbee2mqtt@1.21.0-dev) start

> node index.js
> (node:52781) UnhandledPromiseRejectionWarning: internal/modules/cjs/loader.js:892
> throw err;
> ^
> Error: Cannot find module '../lib/exposes'
> Require stack:

* /app/dist/util/utils.js
* /app/dist/util/settings.js
* /app/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
at Function.Module._load (internal/modules/cjs/loader.js:745:27)
at Module.require (internal/modules/cjs/loader.js:961:19)
at require (internal/modules/cjs/helpers.js:92:18)
at /app/dist/util/externally-loaded.js:1:17
at Script.runInContext (vm.js:144:12)
at Script.runInNewContext (vm.js:149:17)
at Object.runInNewContext (vm.js:303:38)
at loadModuleFromText (/app/lib/util/utils.js:163:8)
at loadModuleFromFile (/app/lib/util/utils.js:169:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:52781) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:52781) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[13:05:26] INFO: Handing over control to Zigbee2mqtt Core ...

> [zigbee2mqtt@1.21.0-dev](mailto:zigbee2mqtt@1.21.0-dev) start
> node index.js`

Tenho a seguinte config no zigbee2mqtt:

data_path: /config/zigbee2mqtt
external_converters:
 - tuya.js
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
base_topic: zigbee2mqtt
include_device_information: true
serial:
port: /dev/ttyACM0
adapter: deconz
advanced:
log_level: debug
pan_id: 6754
channel: 11
network_key:
  * 1
  * 3
  * 5
  * 7
  * 9
  * 11
  * 13
  * 15
  * 0
  * 2
  * 4
  * 6
  * 8
  * 10
  * 12
  * 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental: {}
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: '-d -d'
log: false

Alguém me pode ajudar sobre onde colocar o ficheiro com a informação dos dispositivos tuya e/ou onde/como colocar os restantes ficheiros presentes no repositório?

Obrigado pela ajuda.

#2

Boas, os sensores podem ser os mesmos, mas os módulos internos estão sempre a mudar (problema dos chineses)
Podes dizer-me quais são os sensores, e o log do z2m ao tentares emparelhar? Eu com os dados corretos consigo fazer o deploy dos novos modulos no z2m, mas depois tens de esperar pela atualização da parte da equipa da z2m

#3

btw: instala a versão edge do z2m

#4

Boas. Eu já uso a versão edge, a versão normal não me reconhecia parte das coisas que tenho.
Então cá vai:
Smart Air Box Model RSH-AirBox01 manufactured by Tuya https://zigbee.blakadder.com/Tuya_RSH-AirBox01.html
Log:

Zigbee2MQTT:debug 2021-10-28 12:56:40: Received Zigbee message from '0xa4c13813eb9e0b14', type 'commandSetDataResponse', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,1,224],"type":"Buffer"},"datatype":2,"dp":19,"fn":0,"status":0,"transid":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 12:56:40: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ryfmq5rl'
Zigbee2MQTT:warn  2021-10-28 12:56:40: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 12:56:40: Received Zigbee message from '0xa4c13813eb9e0b14', type 'commandSetDataResponse', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,1,4],"type":"Buffer"},"datatype":2,"dp":18,"fn":0,"status":0,"transid":2}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 12:56:40: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ryfmq5rl'
Zigbee2MQTT:warn  2021-10-28 12:56:40: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 12:56:41: Received Zigbee message from '0xa4c13813eb9e0b14', type 'attributeReport', cluster 'genBasic', data '{"65506":32,"65508":1,"appVersion":64}' from endpoint 1 with groupID null

Está constantemente a dar esta mensagem. Até tenho que reiniciar o HA porque fica mais lento.

Motion Sensor ZB3.0 Model ZM-35ZH-Q https://zigbee.blakadder.com/zigbee2mqtt.html
Log:

Zigbee2MQTT:info  2021-10-28 13:05:39: Starting interview of '0x00124b0015de8c39'
Zigbee2MQTT:info  2021-10-28 13:05:39: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0015de8c39","ieee_address":"0x00124b0015de8c39","status":"started"},"type":"device_interview"}'
Zigbee2MQTT:info  2021-10-28 13:05:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b0015de8c39"},"type":"pairing"}'
Zigbee2MQTT:debug 2021-10-28 13:05:39: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":30}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 13:05:39: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 13:05:39: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":160}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 13:05:39: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 13:05:39: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":30}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 13:05:39: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":160}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 13:05:39: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 13:05:39: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 13:05:42: Received MQTT message on 'zigbee2mqtt/Luz Gabinete/set' with data 'OFF'
Zigbee2MQTT:debug 2021-10-28 13:05:42: Publishing 'set' 'state' to 'Luz Gabinete'
Zigbee2MQTT:info  2021-10-28 13:05:42: MQTT publish: topic 'zigbee2mqtt/Luz Gabinete', payload '{"device":{"applicationVersion":64,"dateCode":"","friendlyName":"Luz Gabinete","hardwareVersion":1,"ieeeAddr":"0x847127fffe0c877b","manufacturerID":4098,"manufacturerName":"_TZ3000_hktqahrq","model":"WHD02","networkAddress":30270,"powerSource":"Mains (single phase)","stackVersion":0,"type":"Router","zclVersion":3},"linkquality":255,"power_on_behavior":null,"state":"OFF"}'o
Zigbee2MQTT:debug 2021-10-28 14:37:29: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:37:29: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:37:29: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 14:37:44: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:37:44: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:37:44: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

Contact Sensor Model TS0203 https://zigbee.blakadder.com/Tuya_TS0203.html
Log:

Zigbee2MQTT:info  2021-10-28 14:41:48: Starting interview of '0x00124b000adec9b8'
Zigbee2MQTT:info  2021-10-28 14:41:48: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b000adec9b8","ieee_address":"0x00124b000adec9b8","status":"started"},"type":"device_interview"}'
Zigbee2MQTT:info  2021-10-28 14:41:48: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b000adec9b8"},"type":"pairing"}'
Zigbee2MQTT:debug 2021-10-28 14:41:48: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:41:48: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:41:48: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 14:41:49: Received Zigbee message from '0x00124b000adec9b8', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":30}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 14:41:49: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 14:41:49: Received Zigbee message from '0x00124b000adec9b8', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200}' from endpoint 1 with groupID null
Zigbee2MQTT:debug 2021-10-28 14:41:49: Skipping message, definition is undefined and still interviewing
Zigbee2MQTT:debug 2021-10-28 14:42:04: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:42:04: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:42:04: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 14:42:14: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:42:14: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:42:14: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:debug 2021-10-28 14:42:14: Saving state to file /config/zigbee2mqtt/state.json
Zigbee2MQTT:debug 2021-10-28 14:42:32: Received Zigbee message from '0x00124b0015de8c39', type 'attributeReport', cluster 'ssIasZone', data '{"zoneStatus":1}' from endpoint 1 with groupID null
Zigbee2MQTT:warn  2021-10-28 14:42:32: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-28 14:42:32: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

Não sei se interessa para o caso, mas estou a usar uma conbee II

Obrigado desde já.

#5

z2m não me interessa o dispositivo que usas :stuck_out_tongue:

o último dispositivo, falta-me a info do model name

Smart Air Box Model RSH-AirBox01 manufactured by Tuya https://zigbee.blakadder.com/Tuya_RSH-AirBox01.html
TS0601
_TZE200_ryfmq5rl

Motion Sensor ZB3.0 Model ZM-35ZH-Q https://zigbee.blakadder.com/Tuya_ZM-35ZH-Q.html
“model”:“WHD02”
_TZ3000_hktqahrq

Contact Sensor Model TS0203 https://zigbee.blakadder.com/Tuya_TS0203.html
TS0203
???

#6

O primeiro device, já existe lá, já alguém colocou, tens de esperar pela release do proximo mês
Entretanto adicionei-te o segundo device

#7

Boa noite. Eu tinha adquirido estes dispositivos porque dizia no blakadder que eram compatíveis com z2m. Entretanto esta tarde tive tempo e substitui a conbee por um stick slaesh CC2652RB https://slae.sh/projects/cc2652/, que aceitou todos os dispositivos sem problemas. Reconhece todos como deve ser.
O sensor de contacto aparece-me no z2m como _TYZB01_xph99wvr.
Obrigado pela ajuda!

Copyright © 2017-2021. Todos os direitos reservados
CPHA.pt - info@cpha.pt

FAQ | Termos de Serviço/Regras | Política de Privacidade