Entities going unavailable when unpowered

[chicagoandy]

First, I wanted to say thanks for putting this together. I really do appreciate it, and it works great. I wish more people could use it, it's sad that so many people can't access their own data, but also fortunate that this still works!

My one "complaint" is how entities go unavailable overnight. Sometimes they are slow to come back, but I think this is the unreliability of the Tigo Mesh...

Could we keep the entities alive, but instead have a sensor showing connectivity status?

I have also noticed sometimes in the morning, all my panels are unavailable even after the sun has come up. There is nothing in the logs, but if I restart the integration they come back.

[nblount]

I think instead of unavailable it should just log all the values as 0 unless the tigo/panel really is no longer registered on the CCA. I have one panel which due to position may not get enough sun to come online for half the day.

I have had at least one occasion where data has not been collected until the add-on was restarted in the morning.

[nblount]

I have put an automation on HA to restart the integration after sunrise. You will need the Config entry ID which you can find in /config/.storage/core.config_entries.

The YAML for the automation is (replace with the Config entry ID from the file above:
alias: Reload Tigo Integration at Sunrise
description: >-
Reload Tigo Integration 5 minutes after sunrise as it gets stuck after a
period of time.
triggers:

• trigger: sun
  event: sunrise
  offset: "00:05:00"
  conditions: []
  actions:
• action: homeassistant.reload_config_entry
  metadata: {}
  data:
  entry_id:
  mode: single