Skip to content

Releases: dacarson/homebridge-rainforest-eagle3

Release list

v1.1.0

v1.1.0 Latest
Latest

Choose a tag to compare

View all tags
@dacarson dacarson released this 14 Sep 18:35
v1.1.0
056cdc7

Full Changelog: v1.0.0...v1.1.0

Assets 2
Loading

Release Notes — v1.0.0

Release Notes — v1.0.0

Choose a tag to compare

View all tags
@dacarson dacarson released this 05 Jun 02:55
v1.0.0
118744f

Release Notes — v1.0.0

Initial release of homebridge-rainforest-eagle3, a Homebridge plugin that exposes a Rainforest EAGLE-200 smart meter gateway as an Eve Energy accessory in Apple HomeKit.

Features

  • Real-time grid demand — current power draw in Watts, updated every poll cycle (default 15 s)
  • Lifetime energy imported — cumulative kWh delivered from the grid (CurrentSummationDelivered)
  • Export meter accessory (optional) — a second Eve Energy accessory for homes with solar net metering, showing real-time export watts and lifetime energy sent to the grid (CurrentSummationReceived)
  • Eve app history — up to 7 days of native consumption/export history via fakegato-history
  • Local-only polling — communicates directly with the EAGLE-200 over the local network; no cloud account or internet access required at runtime
  • mDNS auto-discovery — the host field is optional; when omitted the plugin defaults to eagle-<cloudId>.local
  • Homebridge UI config — full config.schema.json with form layout, including conditional display of the export meter name field

Requirements

  • Homebridge 2.0 or later
  • Node.js 18 or later
  • Rainforest EAGLE-200 (RFA-Z114) on the same local network as the Homebridge host

Known Compatibility

Device Status
Rainforest EAGLE-3 Tested
Rainforest EAGLE-200 (RFA-Z114) Expected compatible — uses the same local API; unverified
Original EAGLE (Z109) Not supported

Technical Notes

  • The EAGLE-200's embedded HTTP server requires HTTP/1.0. Standard HTTP libraries (axios, fetch) negotiate HTTP/1.1 and are incompatible. The plugin uses raw TCP sockets for all device communication.
  • ZigBee disconnection, socket timeouts, XML parse errors, and HTTP 5xx responses are treated as transient — poll cycles are skipped rather than crashing.
  • HTTP 401 triggers a 60-second backoff to avoid hammering the device with bad credentials.
  • If no electric meter device is found at startup, discovery retries every 60 seconds. All other discovery failures retry every 30 seconds.
Loading