I see that I haven’t gone through this section yet.
I have been interested in home automation for a while now, and I haven’t tested anything before Gladys. My server runs on a pi 3, I did the installation from the « ready-to-use » image 
I now have all kinds of connected hardware, compatible or not with Gladys… We have become fond of voice commands from the Google Assistant at home, and it’s true that my dream would be to get rid of it so that everything is managed by voice, but locally.
I have a bridge and Philips lamps, I tested the integration via the bridge and it works perfectly.
I also have a Xiaomi vacuum cleaner, a Worx lawnmower, Reolink cameras, Iotty shutter switches, a Panasonic heat pump with a CZ-TACG1 module, a Bosch oven…
My dream would be to:
- remove the hue bridge (I would recover an electrical outlet and a bit of accessory consumption), but this remains subject to the implementation of an alternative voice solution,
- be able to control the shutters and the heat pump (which have really bad Android apps that work via the manufacturers’ clouds),
- control the cameras (not just view the images, which I already do today in Gladys): program changes in orientation depending on the time / brightness, navigate between « favorite » positions, trigger or stop a recording, manage motion detections…
- control the vacuum cleaner and the lawnmower (start/stop manually or on programming).
In short, all this seems a bit complicated given the heterogeneous nature of the park, and above all the functioning of certain devices, not necessarily very open.
I saw that work exists on certain families of devices:
For Panasonic heat pumps/air conditioners:
GitHub - heishamon/HeishaMon: Panasonic Aquarea air-water H, J, K, L and M series MQTT gateway · GitHub
GitHub - lsochanowski/Aquarea2mqtt: Wrapper for Panasonic Aquarea Service Cloud to MQTT for a smart home integration like Home-Assistant (or for some machine learning) · GitHub
For Reolink cameras:
GitHub - berfenger/cam2mqtt: Control IP cameras through MQTT reliably. Supports ONVIF (motion) and HTTP (reolink) control APIs. · GitHub
and there are surely many others.
I tinker more than I develop, so I don’t think I can contribute much on that side, on the other hand if there is a need for tests or other on the hardware I have, no problem.
By the way, a small question about the integration of new equipment models: in the absence of an open API and manufacturer documentation, what is the method? APK dissection?
To conclude, I have already said it in another topic but it can never be repeated enough: congratulations and thank you for all the work already accomplished.