Every Monday, at 4 AM, I have a scheduled reboot of my hub, so it can start fresh. By the way, I miss the good o'days where mainframe computers could be kept running without reboot for months, even years and were not plagued by memory leaks ...
Getting back to the subject ...
In the last 3 weeks I've been facing some difficulties with Echo Speaks. On Mondays mornings, when I wake up, my voice commands are not "listened" by my hub - no error log message, no nothing. It's just ignored by the hub.
When I request the reboot, everything gets back working, as it should be.
I changed the WebCORE piston that requests the reboot to do it also at every Monday, at 5 AM to see if it's solved with a second reboot programmatically requested or not.
My setup
Hub C-7
Platform version 2.3.9.143
Command sent to the hub to reboot it:
Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help
Echo Speaks is typically used to make Text to Speech commands from the Hubitat Hub to an Amazon Echo device. Is this what is failing to work correctly?
So... are you trying to issue a voice command by speaking aloud to an Amazon Echo device, like saying aloud "Alexa, turn on bathroom lamp" or similar?
If so, this has nothing to do with Echo Speaks, which is a custom community integration to control Echo devices.... Whereas the Hubitat Alexa Skill is used to allow Alexa to control the Hubitat hub.
Which issue are you experiencing? Just want to make sure we're troubleshooting the correct issue.
One quick question for you - are you using DHCP from your home router to assign a reserved IP address to your Hubitat hub? If not, I would recommend setting up a DHCP Reservation in your router, to make sure your hub's IP address does not change every time you reboot it. This is a best practice that helps with many issues like this. It may not resolve the issue you're experiencing, but it will not hurt.
When the hub restarted it was not "listening" to any voice command I did. So, I decided to, instead of using that command, use the Rebooter app and it worked fine.
I don't know exactly what I was doing wrong, but it's not important - it's solved!
