maniac-semal
commented
1 week ago I have the same issue. Only that a restart of the docker container does not always help. Often enough it stays the same. Additionally in my case it is sporadic. Sometimes the connectivity is ON, then it is off for a while and then ON again. I do not see any errors in the container logs. Unaffected by this are all the Disk and Share sensors. They are always available, but the rest of the sensors dissapear together with the connectivity.
Here is the status of the connectivity in Home Assistant for the last 24 Hours where you can see it (Yellow is ON).
Both my unraid servers show disconnected connectivity while other sensors are still working. I have to restart the container to change it back to connected. Then a few hours later back to disconnected while still up and running.
Update: i was able to re-create the issue, if you reload the mqtt integration the connectivity gets set to disconnected even tho its up and running or if you enable or disable a hass-unraid entity. It might do the same after HA reboot.
I use Fahrenheit for temp in unraid, i believe the container takes Celsius for the disk temps and Fahrenheit for MB and CPU temps. So in HA when it converts i get correct temp for disks but wrong for MB & CPU it tries to convert Fahrenheit to Fahrenheit so i get a ridiculous temp reading
i updated one of my servers to 7.0.0 beta 1 and both network throughputs start showing unavailable.