Evidence at a glance
Based on the linked sources. The author's reported result and independent confirmation are separate checks.
- AI involvement
- Reported models: Claude Opus 4.8. Tools: Home Assistant, Modbus, TLS. The writeup below describes the work attributed to AI.
- Reported result
- Works. This is the directory's source-based outcome classification.
- Independent confirmation
- Not reported.
- Human work and limitations
- The integration was developed with assistance from Claude Opus 4.8, as documented in the commit history.
Original sources
What was done
A Home Assistant integration that replaces the FoxESS cloud by acting as a local TLS server for Wi-Fi loggers, enabling offline operation, telemetry polling, and schedule management via reverse-engineered Modbus-over-TLS tunneling.
The mcnamee/ha-foxess integration is a Home Assistant custom component designed to replace the FoxESS cloud service. It functions by running a local TLS server that intercepts traffic from the inverter's Wi-Fi logger, which is redirected via Destination NAT. The integration handles the logger's login and heartbeat, allowing the inverter to operate while its internet access is blocked. The author reports that the integration uses a proprietary framed protocol that tunnels Modbus over TLS. Telemetry is gathered by polling live Modbus holding registers, which are then exposed as native Home Assistant sensors. The integration also includes a foxess_local.force_charge service that performs template-replay of the cloud's 14-write function-10 sequence to update inverter schedules. The author notes that the scheduler write path is live-verified, and the integration provides offline read-back capabilities. While the integration is considered feature-complete, the author notes a minor limitation: users should confirm on their first real force-charge if the new schedule activates from the writes alone, as an additional enable step might be required.
Reproduce it
1. Configure a Destination NAT rule on your gateway to redirect traffic from the logger (8.209.116.72:14431) to the Home Assistant host. 2. Install the integration via HACS. 3. Restart Home Assistant to generate the required self-signed certificates. 4. Force the logger to reconnect to the local server. 5. Block the logger's WAN access at the firewall.