Fallback to GiveEnergy Cloud if GivTCP stops responding after x minutes #3141
Description
Is your feature request related to a problem? Please describe.
GivTCP frequently stops working and restarting the addon, network switch does nothing however rebooting the inverter does.
2025-12-29 20:13:00,595 - GivTCP - read - [INFO ] - Starting watch_plant loop...
2025-12-29 20:13:00,595 - GivTCP - GivLUT - [CRITICAL] - Opening Modbus Connection to
2025-12-29 20:13:00,595 - GivTCP - GivLUT - [WARNING ] - Modbus connect attempt 1/2 failed: Error connecting to 192.168.251.83:8899
2025-12-29 20:13:01,096 - GivTCP - GivLUT - [WARNING ] - Modbus connect attempt 2/2 failed: Error connecting to 192.168.251.83:8899
2025-12-29 20:13:01,097 - GivTCP - GivLUT - [ERROR ] - Failed to establish Modbus connection after 2 attempts
2025-12-29 20:13:01,097 - GivTCP - read - [ERROR ] - Unable to connect to inverter on:
2025-12-29 20:13:01,097 - GivTCP - read - [INFO ] - Starting watch_plant loop...
Describe the solution you'd like
A fallback position to use GivEnergy Cloud API if GivTCP stops working after a duration of time specified by the user? This may not fix my scenario but adds more resilience to PredBat to ensure it can continue functioning outside of GivTCP.
Describe alternatives you've considered
Tried automated methods to restart GivTCP, Unifi swtiches / APs Home Assistant is connected too and started exploring ways to reboot the inverter.
Additional context
Add any other context or screenshots about the feature request here.