Closed albinpopote closed 3 years ago
Hello,
I have 4 new MOES HY368 which is recognized as TS0601_thermostat (manufacturerName: '_TZE200_ywdxldoj'), but when I try to get or set property I have errors:
and I don't understand i set "zigbee_shepherd_devices: true" in Home Assistant Add-on: Zigbee2mqtt When set, the add-on will scan your data_path for a devices.js file, and will run zigbee2mqtt using this custom file. my zigbee2mqtt does not start . so I leave it to you to integrate the model HY368. thank you!
warn 2021-01-31 21:02:48: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:02:48: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. debug 2021-01-31 21:02:48: Received Zigbee message from '0x847127fffe0ebccf', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,0,230],"type":"Buffer"},"datatype":2,"dp":3,"fn":0,"status":0,"transid":210}' from endpoint 1 with groupID 0 warn 2021-01-31 21:02:48: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:02:48: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. debug 2021-01-31 21:02:48: Received Zigbee message from '0x847127fffe0ebccf', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,0,20],"type":"Buffer"},"datatype":2,"dp":109,"fn":0,"status":0,"transid":211}' from endpoint 1 with groupID 0 warn 2021-01-31 21:02:48: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:02:48: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. debug 2021-01-31 21:03:07: Received Zigbee message from '0x847127fffe0d1d33', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,0,240],"type":"Buffer"},"datatype":2,"dp":3,"fn":0,"status":0,"transid":221}' from endpoint 1 with groupID 0 warn 2021-01-31 21:03:07: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:03:07: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. debug 2021-01-31 21:03:07: Received Zigbee message from '0x847127fffe0d1d33', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[0,0,0,240],"type":"Buffer"},"datatype":2,"dp":3,"fn":0,"status":0,"transid":222}' from endpoint 1 with groupID 0 warn 2021-01-31 21:03:07: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:03:07: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. debug 2021-01-31 21:03:07: Received Zigbee message from '0x847127fffe0d1d33', type 'commandSetTimeRequest', cluster 'manuSpecificTuya', data '{"payload":[],"payloadSize":0}' from endpoint 1 with groupID 0 warn 2021-01-31 21:03:07: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE200_ywdxldoj' warn 2021-01-31 21:03:07: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Hello,
I have a new MOES HY368 which is recognized as TS0601_thermostat (manufacturerName: '_TZE200_ckud7u2l'), but when I try to get or set property I have errors:
Setting child_lock to UNLOCK:
debug 2021-01-31 09:26:34: Received MQTT message on 'zigbee2mqtt/0x5c0272fffec04031/set' with data '{"child_lock": "UNLOCK"}' debug 2021-01-31 09:26:34: Publishing 'set' 'child_lock' to '0x5c0272fffec04031' error 2021-01-31 09:26:34: Publish 'set' 'child_lock' to '0x5c0272fffec04031' failed: 'TypeError: Command 0x5c0272fffec04031/1 manuSpecificTuya.setData({"status":0,"transid":0,"dp":7,"datatype":1,"length_hi":0,"length_lo":1,"data":[0]}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Cannot read property 'length' of undefined)' debug 2021-01-31 09:26:34: TypeError: Command 0x5c0272fffec04031/1 manuSpecificTuya.setData({"status":0,"transid":0,"dp":7,"datatype":1,"length_hi":0,"length_lo":1,"data":[0]}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Cannot read property 'length' of undefined) at Function.fromBuffer (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/zcl/zclFrame.js:151:20) at ZiGateAdapter.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/zigate/adapter/zigateAdapter.js:524:50) at Generator.next (<anonymous>) at fulfilled (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/zigate/adapter/zigateAdapter.js:24:58) info 2021-01-31 09:26:34: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'child_lock' to '0x5c0272fffec04031' failed: 'TypeError: Command 0x5c0272fffec04031/1 manuSpecificTuya.setData({\"status\":0,\"transid\":0,\"dp\":7,\"datatype\":1,\"length_hi\":0,\"length_lo\":1,\"data\":[0]}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Cannot read property 'length' of undefined)'","meta":{"friendly_name":"0x5c0272fffec04031"},"type":"zigbee_publish_error"}' debug 2021-01-31 09:26:35: Received Zigbee message from '0x5c0272fffec04031', type 'commandSetDataResponse', cluster 'manuSpecificTuya', data '{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":7,"fn":0,"status":7,"transid":19}' from endpoint 1 with groupID null info 2021-01-31 09:26:35: MQTT publish: topic 'zigbee2mqtt/0x5c0272fffec04031', payload '{"auto_lock":"MANUAL","away_mode":"OFF","away_preset_days":1,"away_preset_temperature":15,"battery_low":false,"boost_time":300,"child_lock":"UNLOCKED","comfort_temperature":20,"current_heating_setpoint":22.5,"eco_temperature":15,"force":"normal","holidays":[{"hour":6,"minute":0,"temperature":20},{"hour":8,"minute":0,"temperature":15},{"hour":11,"minute":30,"temperature":15},{"hour":12,"minute":30,"temperature":15},{"hour":17,"minute":30,"temperature":20},{"hour":22,"minute":0,"temperature":15}],"last_seen":1612081595879,"linkquality":117,"local_temperature":20.5,"local_temperature_calibration":-1,"max_temperature":35,"min_temperature":5,"position":100,"preset":"manual","system_mode":"auto","week":"5+2","window_detection":"OFF","window_detection_params":{"minutes":10,"temperature":5},"workdays":[{"hour":6,"minute":0,"temperature":20},{"hour":8,"minute":0,"temperature":15},{"hour":11,"minute":30,"temperature":15},{"hour":12,"minute":30,"temperature":15},{"hour":17,"minute":30,"temperature":20},{"hour":22,"minute":0,"temperature":15}]}'
Also tryied with confort_temperature. All publishing raise the same error but command is applied to zigbee device.
Getting any property:
debug 2021-01-31 10:44:56: Received MQTT message on 'zigbee2mqtt/0x5c0272fffec04031/get' with data '{"system_mode": ""}' error 2021-01-31 10:44:56: No converter available for 'get' 'system_mode' () debug 2021-01-31 10:45:08: Received MQTT message on 'zigbee2mqtt/0x5c0272fffec04031/get' with data '{"local_temperature": ""}' error 2021-01-31 10:45:08: No converter available for 'local_temperature' ()
I don't know if it can help but I have sometime the following messages on logs:
debug 2021-01-31 09:20:27: Received Zigbee message from '0x5c0272fffec04031', type 'raw', cluster 'manuSpecificTuya', data '{"data":[25,117,36,0,122],"type":"Buffer"}' from endpoint 1 with groupID null debug 2021-01-31 09:20:27: No converter available for 'TS0601_thermostat' with cluster 'manuSpecificTuya' and type 'raw' and data '{"data":[25,117,36,0,122],"type":"Buffer"}'
Can you post the entire message you are trying to publish? It works fine for me with the same device on the latest stable version 1.17.1
topic: zigbee2mqtt/radiator1/set/child_lock Payload: LOCK or UNLOCK
@deusyv
I don’t use the add on but from what it says, like here https://awesomeopensource.com/project/danielwelch/hassio-zigbee2mqtt you need to download the devices.js file , you can then amend it putting the finger print of your device _TZE200_ywdxldoj in place of _TZE200_ckud7u21
I have also a small improvement proposition about the integration of TS0601 thermostat valves with Home Assistant.
Missing hvac_action
The HA climate entity has a state attribute called hvac_action
(https://www.home-assistant.io/integrations/climate/#attributes).
It should get the value heating
when the valve is opened and idle
when the valve is closed. Based on this attribute a few nice thermostat UI controls are rendering the state and you can also do standard automation (blueprints) based on hvac_action
.
I know that TS0601 thermostats expose a position
sensor (% of valve opening), which can be used for the same purpose, but hvac_action
is a standardized way of reporting the current activity of climate entities. Therefore I think the new attribute hvac_action
should be added and set to heating
when position
is greater than 0.
BTW. There is a workaround.... I have configured currently automation in HA setting hvac_action
based on position
but I think this should be done internally in Zigbee2MQTT. Don't you think?
Besides this small issue, I think the integration of Zigbee2MQTT of TS0601 thermostat valves is brilliant!
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Hello,
I have a new MOES HY368 which is recognized as TS0601_thermostat (manufacturerName: '_TZE200_ckud7u2l'), but when I try to get or set property I have errors:
Setting child_lock to UNLOCK:
Also tryied with confort_temperature. All publishing raise the same error but command is applied to zigbee device.
Getting any property:
I don't know if it can help but I have sometime the following messages on logs: