Closed gericho closed 6 months ago
If you look at the current documentation, you will see that it has already been updated. 😉
https://github.com/leiweibau/Pi.Alert/blob/main/docs/API-USAGE.md
Depending on the system configuration, it may be necessary to specify the path "/pialert" (e.g. http://192.168.0.10 or http://192.168.0.10/pialert/) in the URL in addition to the IP or host name.
Whether "http" or "https" is used depends on the web server configuration.
The documentary you linked to is over a year old.
Thank you for linking the new version, I'm sure I wasted your time but I hope it will help someone
YES, it works!
So now the API resides in /pialert/api/ and all the sensor must be updated to:
command: "curl -k -X POST -F 'api-key=yourApi-Key' -F 'get=system-status' https://[URL]/pialert/api/"
Do you plan to build a Home Assistant Addon/integration to include Pihole and PiAlert? I'm sure it will help spread this wonderful tool! THANK YOU
I'm sure I wasted your
No
Do you plan to build a Home Assistant Addon/integration
I have thought about this, but am not able to implement it at the moment (lack of knowledge).
After adding the sensor via the command line platform as the notes found here
I realized running Home Assistant 2023.12.4, the platform must be configured differently to match the new format in particular from this:
to this (so maybe the manual needs some changes)
BTW now all the sensors report UNKNOWN and this is what I found in the HA core log:
and the /api/ file reposts 404
Besides generating and including the current API key and server local HTTP IP address in the sensor definition, I really don't know how to check if the API is rendering the correct JSON values. May I have some help? Thank you!