The integration does not connect after wifi loss or power cycle

[ranademiradafija]

The integratión works fine in the most situations, I'm very happy, congratulations for the developers. thank you so much!.

The problem is when I have a power cycle in the instesisbox device or the wifi conection fail. When de power returns or wifi conection is OK the integration show Not abailable all the time, then I restart HomeAsistant or reload de integraton to make it work again.

Please, I need help, How can I make the integration refresh automatically?

Thank You very much in advance,

[zvolgut]

+1

I confirm the same behavior described by @ranademiradafija

In my case, I have an installation of over than 100 intesis devices and sometimes a disconnection occurs, becoming in a "Not available" state.

I cannot specify if it is due to a loss of Wi-Fi signal or power supply. The tests I have done have not been conclusive. I can try leaving a device isolated for longer if necessary.

When a device enters in that state there is no way for the integration to reconnect it.

At the moment I have an automation created every 4 hours that restarts HA if any device become in "Not Available" status.

[zvolgut]

A capture of the problem,

The intesis device respon to ping:

ping 192.168.16.236 -t

Doing ping to 192.168.16.236 with 32 bytes of data:
Response from 192.168.16.236: bytes=32 time=5ms TTL=127
Response from 192.168.16.236: bytes=32 time=1ms TTL=127
Response from 192.168.16.236: bytes=32 time=30ms TTL=127
Response from 192.168.16.236: bytes=32 time=2ms TTL=127
Response from 192.168.16.236: bytes=32 time=11ms TTL=127
Response from 192.168.16.236: bytes=32 time=15ms TTL=127
Response from 192.168.16.236: bytes=32 time=23ms TTL=127
Response from 192.168.16.236: bytes=32 time=21ms TTL=127

[ranademiradafija]

Hello, OK, Let's see if the developers give us a solution. I have not automated the process to restart HA, what I do is reload the integration. This is more practical than restarting, but I don't know if the reloading of an integration can be automated [image: image.png] El sáb, 2 sept 2023 a las 13:12, zvolgut ***@***.***>) escribió:

…

A capture of the problem, [image: image] <https://user-images.githubusercontent.com/94323157/265200719-4caafb94-2783-4fef-824f-a56f95c429fa.png> The intesis device respon to ping: ping 192.168.16.236 -t Doing ping to 192.168.16.236 with 32 bytes of data: Response from 192.168.16.236: bytes=32 time=5ms TTL=127 Response from 192.168.16.236: bytes=32 time=1ms TTL=127 Response from 192.168.16.236: bytes=32 time=30ms TTL=127 Response from 192.168.16.236: bytes=32 time=2ms TTL=127 Response from 192.168.16.236: bytes=32 time=11ms TTL=127 Response from 192.168.16.236: bytes=32 time=15ms TTL=127 Response from 192.168.16.236: bytes=32 time=23ms TTL=127 Response from 192.168.16.236: bytes=32 time=21ms TTL=127 — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4QXRS2DBLPWNQTZ7TN4LBLXYMIDRANCNFSM6AAAAAA4ERZC3I> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zvolgut]

Hello,

We tried to do a reload instead of restarting and it works thank you! It takes about 1 minute to get connected again.

I've tried to do the reload on an automation and it also works (CCc01 is the entity id of the device):

[ranademiradafija]

Oh!, it's good.
I will try to do it.
thank you very much.

update:
The automation works perfectly, thank you and greetings.

[CV8R]

+1 same problem, same symptoms and the kludge work around script to reload works.