FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. With FUXA you can create modern process visualizations with individual designs for your machines and real-time data display.
Would be nice if it could get the entities like nodered does. I never was a fan of mqtt. For this i will bite down and start using mqtt.
I assume to get sensor data here I would have to manually publish those values using something like an automation to publish every second or so.
If there is another way to get the values Iâd love to hear about it.
Hi, thanks for your feedback! That was my first thought as well. However, I do not have the skills yet to use the Home Assistant API or similar to get the entity states directly into FUXA. Here are two examples of how I currently do it:
Thatâs exactly what I did. I have some sensors with Open/Close and On/Off states. Had to convert in template to 1/0.
Iâve been looking for something like this for a long time. I already have a couple of stuff running. The one thing I am missing is the Gauge background. The background setting changes the bar background, but square card itself is always white.
What I want to do, is use a dark grey background for the main page, so that color stands out more and the tablet is less bright at night.
Do yo perhaps have advise on that?
Is there a possibility that you can embed the FUXA HMI SCADA webpage (http) onto a HA which can be reached externally on a https site ?
Now I have the following setup:
HA which runs only http (so no https & certificates setup)
if you embed Fuxa http page in an iframe, itâs only visible locally on http, not remotely on https.
I donât want to use external port forwarding or add another duckdns https reverse proxy site.
What I did see is there is an option to use âIngressâ, this gives an extra âOpen WEB UIâ and âShow in sidebarâ in a HA Addon.
Ingress also takes care of authentication tokens etc⌠internally HA.
There are several HA Addons using Ingress and allowing to reach an Addonâs webpage also externally.
You can specifiy the WEB UI url in a Addon config.yaml, but I could not get it to redirect to my local http webserver for a Addon I made myself.
Does the docker addon has to be adapted somehow to allow Ingress to work ? The webserver I tried it on is a .NET compiled webserver application (so no nginx webserver).
Can the Ingress option be added to the FUXA HA Addon ?
I see lot of great opportunities to have FUXA add-on fully developed and integrated in HA! This project needs a boost!
Unfortunately the install process fails with recent HA release (Core2024.9.3 / Supervisor2024.09.1 / Operating System13.1). Error is âThe command â/bin/sh -c npm installâ returned a non-zero code: 1â
In addition the native integration of entities as suggested from @Badprop instead of MQTT would significantly improve this tool!
@SmartLiving.Rocks How about rise up the project and get help from the community?
Iâm trying to get Ingress working so you can use FUXA native from inside HA anywhere (internal or external).
Struggling now to get nginx proxy working into Fuxa container.
Map sharing is already working so you can have a persistant config for ex. inside Home Assistant Addon folder.
Fantastic idea! Itâs Hacktober - so everybody feel free to boost that great project!
A few months ago I have had a talk with Umberto the founder of the original FUXA project.
As I am not so familiar with Docker and Home Assistant, I was hoping that he can take over and I introduced him to the Home Assistant project.
So everybody, feel free to get this thing working!
I finally managed to get the FUXA addon working with HA-Ingress HACS addon. (GitHub - lovelylain/hass_ingress: Home Assistant ingress feature, add additional ingress panels to your Home Assistant frontend.)
This way you can add a FUXA shortcut for example in the HA side bar, but most important it is also visible externally (both on http or https) because the Ingress addon reverse proxies all Fuxa webserver traffic internally on the HA host.
Since the Fuxa docker does not contain a NGINX webserver which you can natively enable Ingress, I had to use some search & replace rewriting on FUXAâs relative URL paths.
This is my first rewrite attempt of a custom HA addon Ingress, I learned a lot from it.
I hope itâs usefull for other Fuxaâs enthousiasts.
Addon config below:
ingress:
fuxa:
title: FUXA
work_mode: ingress
url: http://localhost:1881
index: /
icon: mdi:monitor-dashboard
disable_stream: True
rewrite:
# 1. Rewrite the <base> tag in the body section
- mode: body
match: >-
<base href="\/">
replace: >-
<base href="$http_x_ingress_path/">
# 2. Rewrite for API calls (e.g., /api/project)
- mode: body
match: >-
(/api/projectData|/api/project|/api/screen|/api/settings|/api/screen|/api/resources|/api/heartbeat)
replace: >-
$http_x_ingress_path\1
# 3. Rewrite for socket.io requests
- mode: body
match: >-
/socket\.io
replace: >-
$http_x_ingress_path/socket\.io
Hi Guys, I have a project where I urgently need this. I am assuming it is still broken (as addon) after the recent HASS update?
Does anyone have any advice on how to get this working? I am quite comfortable with the MQTT limitation as I am using Node-Red extensively, integrating this will be easyâŚ
Thanks a stack for your feedback. I am running HASS on RPi4 and then there is a PLU outputting MQTT to Mosquitto/Node Red on HASS. One of the reasons I have chosen HASS is to consolidate, with the front-end being the most important. Most IOT frontends are ridiculously expensive or no good.
I can run my Node-Red and and broker on the HASS instance, to run docker on second server seems a waste⌠Maybe a RPi Zero?
Actually, I totally agree! I would also love to see that great feature fully compatible with Home Assistant as an Add-On. Someday, someone with the right skills will do that