I tried to hook this up today with the new google setup. When I get to the test phase, I find it in the google home app, I then try and login to hubitat oauth site and get the error,
"The parameter "state" must be set in the query string."
Is this a hubitat login issue? Or did I mess up somewhere?
edit: I missed the scope part, that fixed this issue if anyone else gets it.
Where did you find the 'on device testing' setting? I folowed the guidelines but it doesnt work. I find the integration in Google Home, find my Hub and my devices, but then get an error that it couldn't be reached. Was there anything else you did?
My error was here
I didn't have a scope defined. After that I hit Next: test, and followed the directions as they are listed, I only have my garage doors, selected those and I can open them in google home.
Thanks for responding. I saw that in your post and added "app" as a scope, but I still get this error when trying to test
And when trying to add it from Google Home it says the service couldnt be reached
This app has worked wonderfully for many years. All of the sudden this evening the speakers and my phone Assistant can't seem to control anything. I can query about light state or temperatures, but no control whatsoever works. The same thing happens in the Google Home app. I can see status of everything but cannot control. Am I the only lucky one?
That's very strange. Can you enable debug logging in he Hubitat app and then watch the log for Google Home Community in Hubitat while you turn on a light or something from the Google Home app? If there are no obvious errors, you can post the log here and I can look at it.
I've rebooted smart speakers and the hubitat hub just to be on the safe side. I enabled debugging on the app. Watching the live logs after issuing a simple on/off command for a light displays nothing in the logs and the speaker responds with "Sorry, I didn't understand."
The Google Home app itself now appears to be working, I can refresh everything and control everything I've tested.
I tried again to test this morning and I'm even more confused! If I ask an Asst to turn something on off, I get the above "Sorry I didn't understand." However, if I ask to set basement lamp to 0%, it works. Same if I ask to set to 100%, it works. I can set temps on devices but it seems simple on off commands throws everything for a loop. I can't make sense out of any of it.
Maybe I've stumbled upon this?
It wouldn't surprise me. Google has always had issues with on/off commands for me. Over the past 5 years, about 20% of the time I would get: "I'm sorry, power controls have not been set up for that device" or "I'm sorry, I didn't understand"
It REALLY has issues with multiple devices in a room containing that same room's name. So, if you have the device named "Bedroom Light" you might just rename it to something like "Master Room Light"
The workaround for me was just saying "Turn off Lights" while in the room instead of saying "Turn off Bedroom Lights". Seems like it stopped listening at Bedroom and thought I was saying turn off the Google device that had that name in it as well.
The other workaround was just saying "Turn off Bedroom" which turned off all the lights and switches in the room.
If I said both "Bedroom" and "lights" in the same request for off/on, that seems to trigger the error WAaaaay more often.
It appears from the Reddit, that it is a bit more widespread today (which again, doesn't surprise me - Glad I am not cloud dependant and just use that part as a convenience)
It appears the issues were pretty widespread by the looks of reddit. Then poof everything just started working again. Apologies for the noise.
I am having an issue in which Google home does not seem to be requesting the status of my Yale Z-Wave locks, after they are added to a home. I have used this exact configuration previously about 8 months ago, and it worked fine. It seems Google may have changed something to do with the lock protocol, or I am missing a setting somewhere.
If I add the lock, but do not add it to a home, it works fine. For example, the lock will initially show up in Google home like this:
However, when I add the lock to my Home, it no longer seems to get an update on the status of the lock, and so appears to hang waiting for a response. It also asks for a PIN, and the lock/unlock screen looks a little different in Google Home.
Here is what the screen looks like when the lock is added to my Home.
It asks for a PIN the first time I go to use it.
If I try to lock the door, the lock command is sent to Hubitat to lock the door, and the door will be locked. However, the app continues waiting for a response with the spinning timer icon waiting for a response saying "Locking" and never changes state.
If I "pull down" on the device list in Google Home, it doesn't seem to request the status for the lock from Hubitat any more (as it did when it was not added to my Home). This is the log:
When I set up locks at another house about 8 months ago, the lock interface was the same in both "Linked to You" and the home, and didn't ask for the PIN or show the type of lock screen as shown above.
Any idea what is going on? Is there some setting in my Google Home that is causing this behavior? Or did Google change the behavior of locks recently?
I was getting a message in Google Home that indicated the service could not be reached and I found the problem to be that I had incorrectly entered the Fulfillment URL.
I just noticed recently, when I try controlling the Monoprice 6 zone controller, I've been getting error in the Google Home App. Looking at the Hubitat logs, below is an example I get with turning it on or off:
That error seems to indicate that your device doesn't have an On/Off trait. Did you maybe remove it and never re-sync with Google Home?
Have not changed a thing in the settings. It just started happening. I checked my location and my parents and it's doing the same thing at both so it's not specific to the location.
Additionally, when I increase the volume through the Home App, the numbers jump all around when looking at the keypad display. Then GH will give an error and say it can't connect to the device.
Try opening the device type in the Hubitat app and saving it as-is. That error is pretty clear that the device doesn't have an On/Off trait associated with it, so maybe some state got lost somehow? If that doesn't work, can you post a screenshot of your On/Off trait configuration?
As for the volume issue, what devices are involved, and can you send a log from when you try to adjust the volume?
Download the Hubitat app
