Check out my new program at GitHub - SoundOfMind/configuration_engine: Deterministic configuration management for home automation devices. Capture known-good device configurations as profiles and apply them to similar devices. · GitHub . If you have devices with a lot of configuration parameters like Inovelli, it allows you to capture and save a profile from your device with all it’s settable parameters. Then you can apply that profile to clone another device. It has features to help manage your library of profiles and analyze your devices. The more complicated your devices are, the more you will enjoy this.
Currently requires a windows computer and Home Assistant with Mosquitto and Zigbee2MQTT. All are invited to use it and it would be great if it could be tested with Mac or Linux, as it is designed to be portable. It could be expanded to use Matter or ZWave if folks have the capability and time.
This is really cool!
I’ve been looking for something like this for a while. I mean really the problem is that Zigbee2MQTT lets you configure things on the “About,” “Settings,” and “Settings (specific)” tabs of a device, but it doesn’t let you configure things on the “Exposes,” “Bind,” “Reporting,” or “Scene” tabs of a device, for some reason. Right now, I’m using Inovelli Bulk Configuration (Zigbee2MQTT), which works great for Inovelli Blue devices, but it only works for Inovelli Blue devices. It’d be great to have something a little more generic for other devices (or to replace that Blueprint, for consistency).
The core architecture seems to be similar to a k8s Controller (which is really just a specific type of control loop). Dunno if you’re familiar with that.
Something that’s a little unclear is whether you can apply multiple different profiles to a single device. From this line here: configuration_engine/README.md at 7e28051987d4055536715ac0274b55bd44c64bd0 · SoundOfMind/configuration_engine · GitHub, it sort of seems like you can. But it’s not explicitly called out anywhere. Some examples of where I find that useful:
- Every switch should have the same “double tap is maximum brightness/speed” behavior.
- Every switch should have the same button press delay.
- Every mmWave switch should have the same z values (since all of my switches are at the same height).
- Etc.
I’d imagine that each of those could be a profile, and then you apply them to multiple devices. Is that how it works?
In any case, if you could provide an image for it, I’d be down to give it a try.