Google home device initialisation is ok but no alarm/timer sensor #231
Comments
|
Try to reboot that device. |
|
Same issue here, logs below |
|
Restarting the google home and home assistant managed to resolve this issue for me. I had to reinstall the integration as well |
Yep. Didn't change a thing for me. Timers and alarms still won't work. |
|
@S-Starvey it's hard to say anything without logs. |
Going to a higher level of logging as soon as I come home. Plus I currently don't have access to the RPi :-D |
|
Well, that's gonna be helpful... Anyway. I'll leave the logging level to debug for a while in case it happens again. |
Hey, thanks, it actually solved the problem. Steps i did:
|
|
yep that's exactly what I did pretty much. Can take a few min for alarms to appear after that |
ArnyminerZ
added a commit
that referenced
this issue
Jun 6, 2021
Added new section "Devices found and initialized, but no alarms/timers sensor" to the Troubleshooting guide for reference of issue #231
|
Closing issue since the issue has been solved and added to the troubleshooting guide. |
KapJI
pushed a commit
that referenced
this issue
Jun 7, 2021
Added new section "Devices found and initialized, but no alarms/timers sensor" to the Troubleshooting guide for reference of issue #231
|
@ArnyminerZ I'm also running into this issue sporadically, but across a number of my Google Homes. I can make it go away temporarily by following the troubleshooting steps, but it usually comes back after a week or two. This part of the logs stuck out: Might it be worth changing that to a warning? Then at the very least there's a way to see that something went wrong without needing to switch logging to full debug. These are a mix of Google Home Minis, 1 Google Home Max (Office Speaker), 1 Chromecast Ultra (Office TV), a couple Google Wifi points (the newer ones with Google Homes built-in), and a couple of the Google display things whose name escapes me at the moment. When the issue happens, I can see this spammed in the logs as well: It generally seems to be "all-or-nothing" in my experience. If Obviously the devices must have an IP for them to be found on the network, so seeing an IP of "None" should presumably raise an error of some kind. EDIT: When it does work, I get a bunch of timeouts on the first boot: But then after a few minutes it tries again with more success: That again leads me to think that maybe requests are just being made before things are ready somehow? And that's why when things work properly it takes a couple minutes for the alarm to appear. |
|
@Jay2645, can you please open a new issue where you can state the version of the integration you are using.
|
|
@leikoilja I went ahead and created #390. Thanks for the help! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have a fist generation google home speaker as well as a nest hub and a home mini. The last 2 works fine but for the original google home i not see alarm/timer sensor.
Version of the integration
Logs
Provided later this day
The text was updated successfully, but these errors were encountered: