You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used this guide to flash my ZBBridge as a router. Pairing this device has Z2M picking it up but with an "unsupported device" flag. For that very reason, they also recommend a custom external converter:
Zigbee2MQTT Users will need to download this silabs.js file from Github, add it to their Z2M config folder, and add the custom converter to the configuration either via the GUI or YAML file. This will not be necessary after the device is added into Z2M builds.
Give the insinuation in a 2022 blog post that this will eventually make it into Z2M builds, I was surprised to find out that I still (in late 2024) needed to manually include the silabs.js custom external converter, especially when I had been using it in ZHA for a few years now, and only very recently - when I decided to migrate to Z2M - ran into this issue.
What's the best way for me to get caught up to speed on making a PR to include this logic?
The file from the blog post contains two devices: UT-01 and UT-02. I was a bit surprised to see the latter already included in this repo. Not totally sure why someone would choose to include one but not the other, when presumably they took the logic from the file in the repo referenced in the blog post.
There are minute differences in the model and description of UT-02 in this repo and the other. I guess it matches on zigbeeModel so these other fields are modifiable?
Given that I'm new to this, I'm not totally sure I follow the logic here re: exposes, fz, tz, reporting, and e. Also not sure why extend is commented out.
Using this manual external converter shows the device power icon as a question mark. Any way to update that via this config to flag it as a powered device?
I appreciate any advice or direction on this!
The text was updated successfully, but these errors were encountered:
I used this guide to flash my ZBBridge as a router. Pairing this device has Z2M picking it up but with an "unsupported device" flag. For that very reason, they also recommend a custom external converter:
Give the insinuation in a 2022 blog post that this will eventually make it into Z2M builds, I was surprised to find out that I still (in late 2024) needed to manually include the
silabs.js
custom external converter, especially when I had been using it in ZHA for a few years now, and only very recently - when I decided to migrate to Z2M - ran into this issue.UT-01
andUT-02
. I was a bit surprised to see the latter already included in this repo. Not totally sure why someone would choose to include one but not the other, when presumably they took the logic from the file in the repo referenced in the blog post.UT-02
in this repo and the other. I guess it matches onzigbeeModel
so these other fields are modifiable?exposes
,fz
,tz
,reporting
, ande
. Also not sure whyextend
is commented out.I appreciate any advice or direction on this!
The text was updated successfully, but these errors were encountered: