Replies: 5 comments 2 replies
-
The legit api just greatly lowers the barrier to entry for many folks as installing the fauxapi can be difficult and carries a certain amount of risk (not that the xml rpc api doesn’t have risks also). My skills with python are also pretty minimal but I helped quite a bit with the opensprinkler integration. |
Beta Was this translation helpful? Give feedback.
-
I know this is quite delayed but here a crude sample to give an idea..
|
Beta Was this translation helpful? Give feedback.
-
I've gone ahead and implemented a ton of this (have a bunch of sensor available already, gonna wrap those up and then begin on services and switches (for enabling/disabling firewall rules, daemons, etc). Let me know if you have some interest in trying it out. |
Beta Was this translation helpful? Give feedback.
-
More than interested in trying it out! I have not had very much time to work on this project myself. |
Beta Was this translation helpful? Give feedback.
-
OK, got an initial stab at it. Still some stuff to clean up but it's a decent first step. https://github.com/travisghansen/hass-pfsense Give it a try and let me know how it goes. |
Beta Was this translation helpful? Give feedback.
-
#14 - moved to discussion
@travisghansen: pfSense does indeed have a legit xmlrpc api. Would you have any interest in migrating this to use that instead of fauxapi? I have fairly extensive experience using it as I’ve built other integrations (ie: https://github.com/travisghansen/kubernetes-pfsense-controller and other non public tools) leveraging it.
@JOHLC Is there something this does better?
Would it support the same functions?
Any experience with creating components for Home Assistant?
In the end, my vision would be for this to be a real component in Home Assistant with config flows and automatic setup etc. but my python skills are non-existent.
Going to close this as it isn't so much a bug or feature request but a discussion. Moved here:
Beta Was this translation helpful? Give feedback.
All reactions