If only the HWINFO integration with Home Assistant is needed, then NO Flight Instrument Panel needs to be connected and no drivers need to be installed and no HA token is required.
If only the Now Playing Display / Sensor History is required, then no HWINFO or MQTT server needs to be set-up or running (in that case, remove mqtt.config).
HWINFO Sensor Entities will be AUTOMATICALLY added to Home Assistant via the MQTT Discovery process.
First, you need to have MQTT installed and working in Home Assistant.
You know⌠every morning I check both the MSFS2020 Forums and the HA Forums for new posts⌠Seeing this one here, and having just come from the Flight Sim Forum, really threw me for a spin.
I thought my browser had gone all wonky and was mixing posts.
It looks like I canât get it to run properly.
I would like to just use the mqtt part.
I filled out appsettings.config with the correct HA configuration and Token,
I changed the HWINFO.inc with HWiNFOSharedMemoryViewer.exe and completed the mqtt.config file.
But after starting fipha.exe nothing happens and I donât reveive any MQTT information on my MQTT Broker.
Also I looks like the hwinfo.json doesnât get updated.
There is still information about an ASUS device in it.
The Log Files just states the following:
INFO 2022-08-09 22:38:17,944 MoveNext - fipha started
INFO 2022-08-09 22:38:17,958 MoveNext - HA task started
INFO 2022-08-09 22:38:18,063 MoveNext - HWInfo task started
Maybe you can point me in the right direction, what could I be missing?
The appsettings ha configuration stuff and token is only for the flight instrument panel now playing display.
It is not used for MQTT.
For MQTT, you only need to set up mqtt.config AND hwinfo.inc.
If data\hwinfo.json is not updated, each time the application is started, then it canât communicate with hwinfo and then the MQTT stuff also wonât work.
You need to enable the âShared Memory Supportâ setting in HWInfo.
And you need a recent version of HWInfo.
Note that the free version of HWInfo turns this âShared Memory Supportâ function off after 12 hours of use!
You can also try the HWInfo tool, to check if the shared memory functionality works :
Thanks for taking time!
I configured mqtt.config and hwinfo.inc.
Also HWInfo is running and the HWInfo tool detects it and I updated the hwinfo.inc with it.
auto reconnect to hwinfo
new field added to mqtt.config with user definable polling interval (in ms)
Added MQTT auto reconnect and added retained flag and QOS1 to MQTT items
media player is now selected via pop-up menu and configured via mediaplayers.json
Hi, Iâm not sure if this is actively being developed or used at this point, but I tried to set up and get the following in my logs:
ERROR 2024-11-06 09:07:41,257 MoveNext - No Home Assistant Connection for Flight Instrument Panels
INFO 2024-11-06 09:07:41,273 MoveNext - fipha started
INFO 2024-11-06 09:07:41,381 MoveNext - HWInfo task started, polling interval 5000 ms
INFO 2024-11-06 09:07:41,421 MoveNext - HWINFO Sensors found, Writing all HWINFO Sensors to hwinfo.json
INFO 2024-11-06 09:07:41,445 MqttOnConnected - MQTT Client: Connected with result: Success
It sounds like a driver issue, but installing the linked-to drivers I get the Saitek era splash screens, so I think drivers are being recognized. Any idea what I could try?
to display something on the Flight Instrument Panels, you need to set up the home assistant connection using a Long-Lived Access Token
This does NOT use MQTT.
Please see github for more information.
The information on the displays comes from home assistant, not from HWINFO.
