Aminorjourney/local-fcsp
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions
8 releases 10 tags
  • v0.3.2 b889220618

    No-longer making 'fake' entities! Stable

    aminorjourney released this 2025-09-14 21:45:01 -07:00 | 1 commits to main since this release

    [v0.3.2] - 2025-09-14

    Added

    • New Binary Sensor for Online Status
      Thanks to an update to the original API (Eric Pullen’s fcsp-api), we can now poll for online status directly, with logging recording any errors during connections.

    • Logic to Eliminate 'Fake' Entity Data
      If an FCSP is connected to a Home Integration System, it will properly represent the system's unique information. In stand-alone installations without a Home Integration System, the FCSP produces 'dummy' data for the Home Integration System, which previously created 'fake' sensors. New logic now strips these out, ensuring the integration only creates sensors for real devices.

    • Refuse Collection Logic to Remove Pre-Existing 'Fake' Sensors
      Given the new logic, we also remove any sensors created with previous versions of this integration that may not exist. This includes removing the old Binary Sensor for Power Cut detection, replaced by the new Power Cut Detection sensor.

    Changed

    • Replaced Binary Power Cut Sensor with Quasi-Binary Sensor
      The Binary Sensor for power cut detection couldn't conditionally appear if a Home Integration System was attached. It’s now replaced with a quasi-binary sensor, allowing "create only if it exists" logic for Home Integration System sensors, and should prevent creation of sensors not paired with a real device.
    Downloads
  • v0.3.1 3ea70aca33

    Refactoring, Simplifying Binary Sensor, Improving Reliability Stable

    aminorjourney released this 2025-08-16 21:15:53 -07:00 | 2 commits to main since this release

    The previous binary_sensor.py for power cut detection wasn't reliably working, so it's now been refactored to push most of the detection logic into coordinator.py, reducing code complexity in binary_sensor.py and (at least in testing) far more reliably detecting a power cut. Since this is only important if you have a Home Integration System installed, it might not be a big deal for you - but it was for me ;)

    Downloads
  • v0.3.0 fd42f25a63

    ajor changes to underlying code, improving stability. Stable

    aminorjourney released this 2025-08-04 17:25:55 -07:00 | 3 commits to main since this release

    Changelog

    All notable changes to this project will be documented in this file.

    [v0.3.0] - 2025-08-04

    Added

    • User-configurable date stamps
      Last updated timestamps now display in a human-readable format. Users can select between 12-hour or 24-hour clocks via the integration config.

    • New binary sensor logic for power cut detection
      Previous versions failed to reliably populate this sensor due to vague polling logic. This version introduces more explicit handling and correct data sourcing.

    • Version reporting for Home Integration System
      Inverter firmware/software revision is now parsed from its hex string and displayed in Major.Minor.Patch format (e.g., 1.1.36).
      This version string appears in Home Integration System > Info > Firmware, while the original cleaned hex string remains in Home Integration System > Raw Data > Firmware (Hex).

    Changed

    • Raw info.json reporting renamed
      Sensors for raw inverter and charger data now use the label Raw Data for clarity and consistency.

    • V2H attached flag renamed
      In Charger Info, the Home Integration Attached flag is now labeled V2H Attached.

    Fixed

    • Fallback status handling for older FCSP firmware
      Older FCSP builds use text-based inverter status rather than numerical codes, breaking compatibility with power cut and status sensors.
      coordinator.py now includes a fallback to support both data formats. This improves compatibility with owners that receive FCSP replacements running outdated software awaiting OTA updates.

    Still In Progress / Known Issues

    • Standalone FCSP (no Home Integration System) setup
      Dummy values may still appear for Home Integration sensors on systems without an inverter attached.
      Future updates will include logic to detect and suppress known placeholder values or restructure the setup flow accordingly.

    Installation Instructions

    • Sensor cleanup required after update
      Updating from earlier versions may leave orphaned or renamed sensors in Home Assistant.
      To resolve:
      1. Manually remove affected entities from the UI; or
      2. Remove and re-add the integration via the UI (recommended, especially when using new config options).

    [v0.2.4] - 2025-07-19

    Added

    • Power Cut Detection Binary Sensor (Home Integration System only):
      A new binary sensor detects grid power outages via the Home Integration System.
      Reports True/False for power cut status, enabling automations such as graceful shutdowns when UPS notifications are absent.
      Future updates will add features like V2G capabilities.

    • Cached Data Support for Faster Startup:
      Uses cached data on startup to avoid blocking Home Assistant while waiting for fresh data.
      Greatly improves startup speed and robustness during network interruptions.

    Fixed

    • HACS Integration Bug:
      Fixed a critical bug causing HACS to fail loading the integration.
      Stability has improved significantly; users are encouraged to report any issues.

    This is an early version (v0.2.4) — please test thoroughly and provide feedback!

    Nikki. x

    Downloads
  • v0.2.4 885052ff8a

    Fixes, enforced minimum scan limits, add power cut binary sensor. Stable

    aminorjourney released this 2025-07-19 22:20:06 -07:00 | 5 commits to main since this release

    Changelog

    All notable changes to this project will be documented in this file.

    [v0.2.4] - 2025-07-19

    Added

    • Power Cut Detection Binary Sensor (Home Integration System only):
      A new binary sensor detects grid power outages via the Home Integration System.
      Reports True/False for power cut status, enabling automations such as graceful shutdowns when UPS notifications are absent.
      Future updates will add features like V2G capabilities.

    • Cached Data Support for Faster Startup:
      Uses cached data on startup to avoid blocking Home Assistant while waiting for fresh data.
      Greatly improves startup speed and robustness during network interruptions.

    Fixed

    • HACS Integration Bug:
      Fixed a critical bug causing HACS to fail loading the integration.
      Stability has improved significantly; users are encouraged to report any issues.

    This is an early version (v0.2.4) — please test thoroughly and provide feedback!

    Nikki. x

    Downloads
  • v0.2.3 98ad5d53a4

    Fixing a Bug with HACS.json Stable

    aminorjourney released this 2025-07-16 18:09:03 -07:00 | 10 commits to main since this release

    It looks like I may have written something in HACS.json which was causing HACS to misbehave. The offending line has been removed

    Downloads
  • v0.2.2 432aa35bec

    BugFixes for API timeout Stable

    aminorjourney released this 2025-07-13 10:36:51 -07:00 | 17 commits to main since this release

    Version 0.2.2 Release Notes

    In my previous version, I'd hard-coded a timeout of 10 seconds which (while you could change it during setup) would inevitably fail before any data was received _if_you didn't change the timeout to something longer.

    I've tested this locally, and it seems to be working quite happily. If you're struggling with this integration and having issues, here's what to do:

    1. Head to Settings>> Devices And Services>> Local Ford Charge Station Pro
    2. Click on the three dots to the right of the device list where either says Local Ford Charge Station Pro
    3. Click Delete to remove your existing integrations.
    4. (Optional) Restart Your Home Assistant . While this isn't essential, I sometimes find it helps integrations reset.
    5. Re-Add the Charge Station Pro again and you should see that the timeout interval has been changed to default to 60

    A note on timeouts and overloading the API

    It's worth noting that the network capabilities of the Ford Charge Station Pro are a bit weak - and you can quite easily overload the station if you try to have too short a refresh interval. The same is true for API polling and initial setup. By initially setting these to 60 seconds, you'll be fine. I've tested with values down to about 20 seconds with mixed success.

    Downloads
  • v0.2.0 31f50400cc

    The First STABLE release. Stable

    aminorjourney released this 2025-07-07 12:33:25 -07:00 | 19 commits to main since this release

    🚦 Release v0.2.0 — First Stable(ish) Version!

    I’m no professional coder, but I think we’ve got our first stable release ready for you to try out! 🎉

    What’s in this release?

    • ⏰ Sensible time handling — your “last refresh” and “last update” actually tell you something useful
    • 🕵️‍♂️ Clearer sensors — showing exactly how recent your data is (no stale surprises!)
    • 🧹 No alpha tags — because that’s... not what we do in release versions?
    • 🔧 Improved device info and debugging — so you can see what’s going on under the hood
    • ⚡ Reliable local polling — no cloud, no fuss, just your Ford Charge Station Pro talking locally

    Try it out, play around, and please send me your feedback. But please, don't send me nastygrams.

    Oh, and if you'd like to watch what I do during the day, head on over to Transport Evolved YouTube. We also have a Patreon: Transport Evolved Patreon

    Downloads
  • v0.1.7 214b33b81b

    v0.1.7 Pre-release Pre-release

    aminorjourney released this 2025-07-01 18:52:08 -07:00 | 21 commits to main since this release

    Fixes and cleanup

    Downloads