Finally got time to give this a try, but hasn’t helped, still can’t connect OpenHab account to Google Home. I should have noted that I’m in Australia. I can see in some posts that localisation has caused some problems at times. I’m beginning to wonder if perhaps that is contributing. Otherwise I’m completely stumped.
Okay, I’ve made some progress. Deleting item files and re-adding shows my lights item file (which just contains all my Hue item definitions) is preventing the linking. Presumably why the link died last week. Weird thing is nothing has changed in that file for many months and was previously working the Google Home just fine. Will investigate further.
One other oddity I’ve discovered - I have an item called “Color” that gets imported into Google Home even with all my .item files removed. There is also no corresponding entry in myOpenHab or the exposure tags of the OpenHab cloud connector… It wasn’t there when I previously had my link working either. Anyone else seeing this or has a clue what it is? Doesn’t appear to be causing any problems itself, just seems very odd.
So you managed to link to Google Assistant now?
No, I havn´t seen such thing. It shouldn´t be possible if you´re sure all your items are no longer tagged.
I finally solved my problems with Danish by a factory reset of my Google Home device. I found out it was important that the language on the phone was Danish when I set up the Home device. Now the device shows Danish as language when I select the Home device and view the settings. After that Danish commands have worked on the Home and on the phone.
Good to know.
I’ve made a service to check if your item configuration is valid using Google Assistant.
You can found it here.
I’ve tried to catch the most common issue’s.
If you still have trouble to connect Google Assistant to OpenHAB after running this test please contact me.
It would be great if you posted this to a new thread so it will be much easier to find and link to as opposed to posting #628 in this massive and growing thread.
This is a great idea and I’m sure lots of people will find it useful. Thanks for posting!
I will make a new thread for this test tool.
I’m also looking for implementing tests for Alexa.
In the mean time, feel free to test your item configuration and let me now if there are any issues.
I also have some “ghost” items, that is not taged in my items file. To be spescific two items named “color” and two items called “brightness”. After some investigation i found out they are linked with my two xiaomi mi gateways from the xiaomi mi smart home binding. Any suggestions on how they can be removed would be greatly appriciated.
Thank you @aart . I was able to find out my thermostat group didn’t have a label.
Hi is there already a way to control volumes (dimmer items)? I know there is the [“Lighting”] tag but this requires a specific wording for light i suppose.
Same question for contact items: Can i ask for the the state of a window? What tag must be used?
In answer to your first question I think the answer is you need to use a Dimmer Item and the Lighting tag.
The answer to your seconds question is no, I don’t think you can ask for the state of Contact items. But you should be able to use a Switch Item with the “Switchable” tag and ask Google Assistant whether the Switch is ON or OFF.
i am trying to unlink openhab from google assistant.I unlink the account allright from assistant’s settings but when i try to sync my other services i get this : “OK,syncing devices for MiHome,Harmony,and Nest.An error occurred while syncing openHAB.”
I dont have an Openhab account connected and i get this?Anyone know whats going on?
It ought not to do that… but it may still see that there is an application remaining that was granted access. Log into your myopenhab.org account. Hover over your User ID (upper right) and click on ‘Applications’. Delete any instances of ‘Google Voice Assistant Control’.
There is a bug in the heatcool mode. The status heatcool is take correctly but the targettemperature is not taken by google home, target temperature is 0 in Google Home app.
For modes heat and cool the target temperature is captured correctly.
@MARZIMA any idea? See my question above.
Let me clarify this for you.
The integration between Google Assistant and OpenHAB is a true Smart-Home integration. Google provides a couple of formats for devices eg: lights, thermostats. Each device has 1 or more traits eg: target temperature, current temperature. All specified by Google.
Thew only thing OpenHAB does is exposing devices to Google.
All the logic, voice to text, interpretation etc is done by Google.
When you say: “Hey Google, turn lights on” Google makes a decision to turn on some lights.
The command received by OpenHAB is nothing more than: “light 1: ON, light 2: ON, light 3: ON”.
If you have roller shutters/curtains exposed as light, you would have a weird behavior when you turn all lights off, because Google doesn’t know that some light is not a light but a roller shutter.
Back to your question: Is there any way to have more control in case of the commands “turn on/off all lights?”
For OpenHAB, No.
In the Google Home app, you can make some custom routines to overwrite some default behavior.
If you make a custom routine with the voice command “turn lights on” you can specify which actions should be taken.
That is what I was afraid of.
I was using custom routines as a workaround but keep finding different commands that also close all lights. I guess I could maybe proxy the items and check if many of them get switched in quick succession but that would add a delay and the calls may not always come as quick.
The roller shutter was on the Google roadmap for 2018, but it is still not implemented.