Replies: 1 comment 3 replies
-
|
@deimi yes, that's something on my TODO list. I'm happy to review the PR. Some pointers of the implementation I have in mind:
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, sounds good. |
Beta Was this translation helpful? Give feedback.
-
|
That's a good question. Our custom converter b-parasite.js "sets up" all sensors. I actually don't know what would happen if we only had clusters for some of them on the device. I'd guess they would be set up in HA but be unavailable/unknown. We can always disable them manually. I can't find it now, but a while ago I read somewhere that z2m introduced something more automatic for the converters, which would let us get rid of the custom converter, and then I would expect it to work automatically with a subset of sensors. EDIT: found it:
It would be cool if we got this to work (I haven't tested it). With ZHA I expect it to work out of the box, as long as we flag-gate the cluster definitions in the zigbee sample, because it automatically detects the exposed clusters and turn them into HA entities. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I will take a look |
Beta Was this translation helpful? Give feedback.
-
Today I ordered a bunch of PCBs without the ambient light and Sensirion chip as I don't need this features and it makes the hardware cheaper.
In order to have a clean firmware without any errors, I will disable those sensors in the firmware as well. Either completely remove the parts or make it configurable via Kconfig.
@rbaron are you interested in such a upstream contribution? I'm asking to know if it makes sense to make in a clean way and submit a PR or just make dirty workaround in my personal fork.
Beta Was this translation helpful? Give feedback.
All reactions