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 am currently considering distributing my HAOS system across various dedicated sub-servers. The HAOS-main-server would then no longer be responsible for central data storage. It would subscribe to predefined views for display and receive MQTT commands for further processing between device groups.
Mission Statement: Enable Maximum resilience
Basic idea: Every device stores its own data and has its own WebUI OR connects to a specific sub-server for storage and generation of views.
Example 1: The ESP-based weather station (DIY) has its own SD-Card for historical data and brings its own webUI. In addition, the data can be subscribed to via JSON. And if necessary the ESP generates MQTT Messages for the HAOS-main-server.
Example 2: All sockets, switches, and measuring devices are managed on a sub-server. Here, too, the principle applies: The HAOS-main-server subscribes to views, receives MQTT messages, and can query JSON.
In principle, HAOS could also be used on most sub-servers (Raspberry Pi), but there is an issue: The HAOS-main-server can only subscribe to complete dashboards with "website card" – not individual elements (i.e., a single card on a dashboard on a sub-server). To transfer individual elements, I would have to create several dashboards (tabs) for every device connected to the sub-server with one card for every view on one page (tab). What a hell of work ...
Is there a workaround for this issuw, or would this be an idea for further development of HAOS?
Guys, this sounds like overkill first hand – just think of it as proof-of-concept. And honestly, you can ask for a Pi Zero for Christmas and try it out.
Why is this exciting?
According to gpt research, the topic appears to be under discussion, but not in the HAOS community.
It's ahead of its time, it's new, it's awesome.
Potential use cases
It's necessary to have a solution if one uses more then one HAOS-servers and likes to share views (single cards, not complete dashboards) between the servers.
Anything else?
GPT could't find anything inside the HAOS community (except my own posts).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Describe your idea
I am currently considering distributing my HAOS system across various dedicated sub-servers. The HAOS-main-server would then no longer be responsible for central data storage. It would subscribe to predefined views for display and receive MQTT commands for further processing between device groups.
Mission Statement: Enable Maximum resilience
Basic idea: Every device stores its own data and has its own WebUI OR connects to a specific sub-server for storage and generation of views.
Example 1: The ESP-based weather station (DIY) has its own SD-Card for historical data and brings its own webUI. In addition, the data can be subscribed to via JSON. And if necessary the ESP generates MQTT Messages for the HAOS-main-server.
Example 2: All sockets, switches, and measuring devices are managed on a sub-server. Here, too, the principle applies: The HAOS-main-server subscribes to views, receives MQTT messages, and can query JSON.
In principle, HAOS could also be used on most sub-servers (Raspberry Pi), but there is an issue: The HAOS-main-server can only subscribe to complete dashboards with "website card" – not individual elements (i.e., a single card on a dashboard on a sub-server). To transfer individual elements, I would have to create several dashboards (tabs) for every device connected to the sub-server with one card for every view on one page (tab). What a hell of work ...
Is there a workaround for this issuw, or would this be an idea for further development of HAOS?
Guys, this sounds like overkill first hand – just think of it as proof-of-concept. And honestly, you can ask for a Pi Zero for Christmas and try it out.
Why is this exciting?
According to gpt research, the topic appears to be under discussion, but not in the HAOS community.
It's ahead of its time, it's new, it's awesome.
Potential use cases
It's necessary to have a solution if one uses more then one HAOS-servers and likes to share views (single cards, not complete dashboards) between the servers.
Anything else?
GPT could't find anything inside the HAOS community (except my own posts).
Beta Was this translation helpful? Give feedback.
All reactions