Replies: 5 comments 1 reply
-
|
Find the most similar device that is already supported and use that as a starting point. You can trick Z2M into thinking you have a different device:
|
Beta Was this translation helpful? Give feedback.
-
|
I got it to work pretty decently. I followed the docs until I managed to add an external converter that did nothing but assign a name to my device. Then because it is tuya, I guess it was easier, just to assign data points... fiddle with the device and reverse engineer what they do. Unfortunately some settings are from the device only, and changing them on device did not generate zigbee events: like language setting, or hour format, and some other settings. |
Beta Was this translation helpful? Give feedback.
-
|
the thermostat is tedious to use in HA. I think it must return a climate (thermostat) entity, or? |
Beta Was this translation helpful? Give feedback.
-
|
This is a second interaction of the converter, in which presents a thermostat interface (climate). The device state (ON/OFF) is also mapped into a system mode, which seems to be the preferred UI approach |
Beta Was this translation helpful? Give feedback.
-
|
@andrei-lazarov here is the pull request CI is giving me an TS typing error, that is not happening in the development console, any ideas what this is about? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I got this Tuya Smart Zigbee Thermostat for Fan Coil 2 or 4 Pipes Fan Control 0–10V + ON/OFF Valves
Its generated external definition is:
export default {
zigbeeModel: ['TS0601'],
model: 'TS0601',
vendor: '_TZE284_4vbj3fxh',
description: 'Automatically generated definition',
extend: [],
};
Its a Tuya device, so according to documentation should be easier...
I have never done this before, but will try to add support myself. Of course, tips are welcome.
Beta Was this translation helpful? Give feedback.
All reactions