Hi everyone, I wanted to share my recent success in setting up an automation to handle a connectivity issue with Nabu Casa. I recently faced a situation where my HA instance at my summer home lost its cloud connection, leaving me unable to access it remotely. The issue was perplexing since the HA instance itself was still operational, as confirmed by Google Home interactions and a functioning internet connection. After some troubleshooting, I managed to resolve the issue by physically rebooting the Raspberry Pi, but I knew this wasn’t a sustainable solution for the long term.Determined to find a more reliable fix, I decided to create an automation that would monitor the Nabu Casa connection and reboot the Raspberry Pi if it detected a loss of connectivity. This involved setting up a script that pings the Nabu Casa remote access address at regular intervals. If the script detects no response after a set period, it triggers a reboot of the RPi.The process wasn’t without its challenges. I had to research the correct commands and intervals to ensure the automation wouldn’t interfere with normal operations or cause unnecessary reboots. I also looked into potential security concerns, ensuring that the script was secure and wouldn’t expose my system to vulnerabilities.After several iterations and testing, the automation is now up and running smoothly. It has already proven its worth by detecting and resolving a connectivity issue without any manual intervention. This has given me peace of mind, knowing that my HA instance is more resilient and reliable now.I’d like to thank the community for the wealth of resources and advice that helped me achieve this. If anyone has questions or needs assistance with similar automations, feel free to reach out—I’d be happy to share more details or troubleshoot together.It’s incredible how a bit of problem-solving and the right tools can transform a potential frustration into a seamless solution. Happy automating everyone! 