How to solve "unavailable"

Configuration
1

Hi
I have home assistant green and solar panels. I do not have a lot of experience with home assistant.. It was quite easy to get the solar panels on my dashboard but unfortunately the HA had to be off power for about ten minutes. Since then, I frequently get in the dashboard behind the sensors the word "unavailabe" (I have the dutch version so in reality it says "niet bereikbaar"). But not always, say approximately half the time. Is there a way to solve this?
greetings, Anjo

2

First thing I would try is go to Settings -> Integrations then click on the integration and then in the upper left of that new page are three dots and click "Enable debug logging".

Watch the entity change from a value to unavailable and then you can click Disable to disable the debug logging and look at that file. It might be large, so note the time the entity reported unavailable and look around that time. Hopefully the integration will tell you what the issue is.

3

Hi,

Which sensor? Does the sensor go "unavailable" when the sun is up and the inverter is on?

4

The sensors for the solar panels..And they are not unavailable because the solar panels aren't working. they are somtimes unavailable when they are working (other app)

5

I enabled debug logging. So now the waiting game starts... at this moment they are unavailable but that will change somewhere between now and tomorrow. in the meantime I can search on how to read and find the log file...

6

Then you can take the debug tour like busman described :wink:
Anything in the home assistant logs?
The inverter should be on right now, is it pingable? Does it have a static IP and a strong WiFi connection?

7

You can also search/grep through the logs you have. The integrations typically would log issues with an error where you wouldn't need to enable debug logging first.

That said, "unavailable" might be just considered normal. Which integration are you using?

8

I did not have any problems monitoring the sensors via the dashboard previously. The problems started after the loss of power

9

I do not quite understand your remarks. The integration is an envoy converter. I do have ann error message in the logs concerning this one.:I dont have any idea what it is saying...

the log for this one gives me

Logger: homeassistant.components.enphase_envoy.coordinator
Bron: helpers/update_coordinator.py:424
integratie: Enphase Envoy (documentatie, problemen)
Eerst voorgekomen: 8 mei 2026 om 23:01:56 (49 gebeurtenissen)
Laatst gelogd: 19:24:38

  • Error fetching Envoy 122322060457 data: Error communicating with Envoy API on 192.168.178.40: aiohttp ClientError Connection timeout to host https://192.168.178.40/production.json?details=1
  • Error fetching Envoy 122322060457 data: Error communicating with Envoy API on 192.168.178.71: aiohttp ClientError Cannot connect to host 192.168.178.71:443 ssl:default [Connect call failed ('192.168.178.71', 443)]
  • Error fetching Envoy 122322060457 data: Error communicating with Envoy API on 192.168.178.71: Timeout
  • Error fetching Envoy 122322060457 data: Error communicating with Envoy API on 192.168.178.71: aiohttp ClientError Connection timeout to host https://192.168.178.71/production.json?details=1
  • Error fetching Envoy 122322060457 data: Error communicating with Envoy API on 192.168.178.71: aiohttp ClientError Timeout on reading data from socket
10

stupid idea: can I just remove the sensors from the dasboard and later put them on the dashboard again? would that perhaps solve it?

11

No, that's not related to the dashboard.

Did you try pining those IP addresses?

Did you configure the "hubs" in the integration using IP address or host names?

Is it possible after a power failure they have new IP addresses? Did you do a DNS reservation in your router so they are always assigned the same IP?

12

If I ping the first IP adress I get four times: Destination host unreachable.
Ping statistics for 192.168.178.40:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I am so sorry but I do not now how to do the rest of those things. The power was only off for the home assistant and the router. Due to work in the house they had to be disconnected from the power temporarily. i really do not understand it: the power has been completely off in the house a few months ago which did not cause any problems. That is why I thought it could be solved by removing ang adding again.

13

First I would go to that integration page again and click a different three dots -- this time the one listed on the right as a "hubs" or "devices" and look for "reload" and try that.

The reload option tells the integration to reconnect.

The host name should have been auto-discovered when first configured if you didn't manually enter it (according to the integration docs), so if "reload" doesn't work you could also remove the "hub" or "device" from that same menu and try setting it up again and hope that it finds the Enphase again.

Probably helpful to have a second window open and watch the logs when you try and restart or delete/add the integration again.

Oh, also look at this option: "Always use a new connection when requesting data from the Envoy"

1 Like
14

Your IP Address has changed to 192.168.178.71 for the sensors and the app is looking for them at 192.168.178.40

Have you considered allocating a Static IP address in your router DHCP Configuration for troubleshooting and consistency? Do the same for your HomeAssistant server.

15

if I look in the settings for this inegration it says the host is 192.168.178.71

16

I dit, to no avail

also done, but did not make a difference

17

How is it then possible that it gets results half of the time? If it has the wrong IP adress, it should always be unavailable of am I wrong about that?

18

Dynamic vs Static IP Addressing is often a difficult concept to grasp but you will find it useful in your network troubleshooting endeavours, which you appear to be experiencing.

If your device IP Address allocated by the router is consistent and not changing at random each time it connects, surely the chances of finding something at that address increases remarkedly?

19

that makes of course sense but I still do not understand why it sometimes is available if the IP adresses keep changing? do they cycle trhough the same adresses (meaning sometimes it has the correct adress)?

20

No, an IP cycle is not normal in a house-garden-kitchen network :stuck_out_tongue: due the DHCP lease time. A router reboot or cutting the power on the other hand do break this lease.

Maybe it is something silly. Your router was powerless as well, maybe it started up on a different Wi-Fi channel (auto) and it interfere with a neighbour for example.