So here it is — as mentioned in my presentation, I’m looking to initially update the rather « old-fashioned » interface offered by the eedomus home automation box.
These devices are very stable and offer a lot of possibilities, all without having to write code (or very little).
The protocols in use are varied; at the moment my components run on Z-Wave, Zigbee and Ethernet, plus some wired devices via native I/Os.
Where it falls short is that the interface is quite « rigid » and doesn’t necessarily allow you to display what you want where you want it.
Do you therefore think it would be conceivable to interface all or part of this box via HTTP requests with Gladys, and what would the technical constraints be knowing that there are already integrated:
2 eedomus boxes (one indoor & one outdoor)
29 Z-Wave components
11 wired components on native I/Os
7 Zigbee components
20 network participants (Ethernet & Wi‑Fi)
Of course, not all these components have the same refresh rates; some update every second (very few), others every minute or even every half-hour.
Current overview:
My first concern being that things might get a bit crowded, so to speak, when sending HTTP requests one by one, or two by two, to the two boxes.
My knowledge of this kind of interfacing being limited, I’d rather gather information before spending hours on installation for a final result that could be mediocre or even nonfunctional.
Thanks for your « insights »
Oh, I almost forgot,
Happy end of the year to everyone
So after a few small tests on the « basic » On/Off functions and other weather widgets, without wanting in any way to disparage the work already done, well there’s still work to be done, both graphically in appearance and capabilities, and on integrations.
As for me, I would be happy to continue by diving into Node-RED to interface my home automation box, but as things stand, I might as well do this on Home Assistant (HA) to have a nicer visual.
Be able to change the wallpaper, either for fun or for a « floor plan » mode
Be able to switch the interface to « dark » mode
Be able to rework the widgets or have access to libraries (from the web, for example)
For the « technical » side of the interface :
Be able to add columns (put 4 or 5 or even more)
Be able to arrange widgets without constraints
I understand this can be a lot and that you have to work on at least two platforms (PC & mobile) not to mention voice interfaces, but nowadays it’s somewhat what users expect if we want to « democratize » home automation.
eedomus has worked quite a bit on that, but like many pieces of software, the base being relatively old, not everything is feasible without a complete graphical overhaul that wouldn’t be backward-compatible; moreover, you need a dedicated team of graphic developers for that and that’s not something every organization can afford, especially in « open source ».
Then we can also discuss the integration part: Gladys is on the right track, but if you want to go faster, you have to search for and integrate ALL existing API providers and that’s a lot of work; again, not counting everything done over HTTP these days (a typical example is Shelly recently, which has been an up-and-coming manufacturer for some time). Going through Node-RED (or other third-party gateways) remains very tedious for the average user.
So maybe Matter will be THE solution, but that’s another very long story…
Hello to you,
So my previous post makes me smile a lot, because I didn’t know Home Assistant (HA) yet and I just set it up last night on my little server based on a ZenBook.
Well, it’s pretty impressive, both in the interface and in the integrations (instantaneous); most of my comments are already included.
I won’t, however, skip using Node-RED to interface (probably via push) my eedomus boxes, but a « cohabitation » of the two platforms might be my
@pierre-gilles will surely be more suited to answer, but in broad strokes, Gladys is meant to be a simple product for the user (very little configuration to do, no .yaml files, etc..) with a modern, streamlined interface.
Starting from this concept, customization options are very limited, precisely to avoid losing the uniformity of the interface.
