@philippe.charette Still doesn't work, Here is my complete config
Device type: Window Shade
Google Home device type: Blinds
Device Traits: Open/Close
---> Preference For Open/Close Trait
Discrete Only Open /Close: Disabled
Open/Close Attribute: level
Query Only: Disabled
Open Position Command: setLevel
does this seem ok ?
Hello,
If you want to be able to control them with your google home app you will have to use Switch type and brightness to change the level.
The way you have it will work for voice commands and would have open/Close controls on a google nest hub or hub max. But only open close.
Hopefully the google home app will add these features some day.
Hello, Will you be implementing these all at once? I'm wondering if the "InputSelector" Trait would change the inputs on my Denon AVR. I'm thinking it should.
Thanks Again for this integration!!
Sadly, yes. The app does not have UI support for the Open/Close trait.
There is no officially-documented speaker device type. It looks like there is an undocumented one though. I've been going back-and-forth deciding whether to include undocumented device types/traits. On the one hand, they're unofficial and could break at any time. On the other hand, they'll probably be fine.
In the mean time, if you're OK accepting the risk that it stops working at some point (it probably won't, Sonos is using it after all), you could add SPEAKER: "Speaker", to the GOOGLE_DEVICE_TYPES list to get a speaker device type.
I've implemented Volume and am using it with my Denon AVR. InputSelector and TransportControl are high on my todo list. The others I may get to some day.
This project is fantastic, thank you very much. The detailed documentation helped a lot to get my blinds show up as actual Blinds in Google Home!
Below are the settings/traits I used to make Bali Autoview Blinds work. Note I used a custom Z-Wave blinds driver.
@ovidiudan Everything seems to work with my Bali blinds with the driver you mentioned, but I keep getting the following error in the logs... any ideas why? Thanks!
dev:872020-05-03 10:14:34.336 pm errorZ-Wave Shade -- v1.0.2 -- Exception java.lang.NumberFormatException: For input string: "t:"
I see the same thing in the logs. Known issue, if you check the discussion for this driver.
I fixed the error messages by using this driver instead: Fibaro roller shutter 3
Everything works perfectly with my Bali blinds and Google Home integration.
I was disappointed with how some of my devices were recognized by google home. I was going to just live with it, but I am really happy that I searched.
Awesome work, easy setup and works great!
So I've looked through the instructions and the instructions and can't seem to find the answer to my question.
What do I put in the Invocation Display Name box? Is this a one time entry to create the trigger phrase in lieu of Hey Google? If so, everything I come up with is discarded when I try to save it. Any suggestions to what you guys and gals are using??
The Display Name box will be the name shown in the list of available integrations in the Google Home app as well as the name the Assistant will report if there's an error (i.e. "Sorry, I'm having trouble reaching [Display Name], please try again"). It can be anything you like (I use "Hubitat Community" for mine); you never actually say it when talking to the Assistant.
I am loving this integration! I just added my locks and added a pin to unlock. Stinking cool....
On to my question. Is Google not smart enough to differentiate between Living Room Spot, Living Room Lights, and Living Room Lamp? If I put them all in the same room in the app then if I call one by name to turn on or off, they all turn on or off. I know there are workarounds by not putting them in the same room, etc., but does that not defeat the whole purpose of rooms in the GH app?
How is everyone else dealing with this issue or is there some setting or something I am missing in this app?
Scott
I'm able to control individual lights in a room by name. I would expect "Living Room Spot" and "Living Room Lamp" to work fine, but in general "[Room Name] Lights" will control all lights in the room. Maybe try using "Living Room Overhead Lights" or something like that as the name for your main lights?
All of that is handled by Google though, so there's not really anything I can do improve it in the Hubitat integration.
This is typically what you want to do. Otherwise, it will refer to the room name. Also, if you have a light named the same as the room name it typically understands that when you say overhead it chooses the light (when it's among others) with the same name as the room.
It is best not to have the room name in the light name in general though. Sometimes it's unavoidable unless you make dumb names but you can often get away with it.
Ok I have followed the instructions and all my devices pop into Google home. As long as I leave them unconnected to a home or move them to a room they work fine. As soon as I move them to a room the entire process goes haywire. Some devices function fine and then other "cannot connect" and just die. There is no rhyme or reason. I have removed the device in your app and resynced with Hubitat, re-added it and it works fine... until I move it to a room. I have unlinked and relinked, same issue. I even deleted all my rooms and started over. No luck. It works for a while and then this issue raises it's ugly head again. Some devices work, others just die with the "cannot connect".
What devices are having problems and how do you have them configured in the app?
All of them. Bulbs, switches, , fans, locks, you name it. It seems to be some kind of left over metadata in Google Home that is looking for the old device even though it was removed. What I found that eventually worked was clicking on each device... If it threw a can't connect or offline error, I moved it's room to somewhere else and then immediately moved it back into the room it belongs. Then it would work! It seems this process would over write whatever the "ghost data" was. This shouldn't have to happen though. I don't know if this is a developer problem on the Hubitat side where commands to remove do not properly instruct Google's servers or if it is a Google problem. I never encountered it with Smart things before... This seems new to Hubitat when switching between the official Google Home App and the Community App.
@mbudnek Thank you for your incredibly helpful and on point step-by-step instructions for n00bs like me. Worked perfectly for my Graber shades! An error that I got of "Couldn't update the setting. Check your connection" was because I had not correctly entered my Hubitat ID in the fulfillment URL. Silly mistake.
A funny thing is that I can ask GH to open my blinds 50% (I have 5 in one room) and it will open all of them to 50% but respond, "OK, opening 90%" or some nonsense that doesn't correlate with my original command. Any idea why it does what I ask but responds with a different value? The open/close attribute is unset. Truly just curiousity because I'm just so happy it works!
That's probably the same issue some others have reported. When the app gets a command from Google, it sends it to the relevant devices and then waits a few seconds for their reported state to match what it told them to do. Some devices like shades and garage doors take too long to reach the desired state, and so the app ends up reporting back to Google with either the initial state before they started moving or some intermediate state. I need to do a bit or redesign to change the way that works; I just haven't had the time or motivation recently to do it.
Download the Hubitat app
