So what changed? Is it the Google end or openHAB? It seems strange that a lot of people (including me) have had the same problem at the same time.
I’ve been running for over 3 years with { 'switchable" } tags, etc and, on Saturday, Google lost everything.
I thought the OpenHab connector went down again since yesterday, so I waited, and waited, restarted my OpenHAB VM, still nothing showing up under Google Home, went into the Google Home App attempting to re-link, and it gave the error “no devices were found in your openHAB account”, so I googled that and found this thread.
Now I’m a little confused at how to convert my current items to this new format as I too have been using the [“Switchable”] tag without issues.
If anyone might be able to confirm how to re-format?
Before:
Switch Light_UL_BedroomBedSwitch "Bedroom Bed Light" (UL_Bedroom, Lights, UL_Bedroom_Lights) ["Switchable"] {channel="tplinksmarthome:hs105:UL_Bedroom_Bed_Light:switch"}
After:
Switch Light_UL_BedroomBedSwitch "Bedroom Bed Light" (UL_Bedroom, Lights, UL_Bedroom_Lights) { ga="Switch" channel="tplinksmarthome:hs105:UL_Bedroom_Bed_Light:switch"}
Doesn’t seem to make a difference, forced a refresh and tried re-linking through Google Home, still says “no devices were found in your openHAB account”
Giving up for the evening and will attempt to tackle this again tomorrow, hopefully someone can chime in with suggestions. 
Thanks!
I think you need to separate the ga from the channel brackets but I’ve only managed to get some of the key items to work by editing the metadata in the devices in the OH3 UI.
If I get something to work I’ll report back
Right, the ga=“Light”, etc needs to be separated by a , from the rest of the channel
{ channel=“tplinksmarthome:hs105:UL_Bedroom_Bed_Light:switch”, ga=“Light”}
1 Like
While you are doing it adding roomHint puts the device directly into the room
{ channel=“tplinksmarthome:hs105:UL_Bedroom_Bed_Light:switch”, ga=“Light” [roomHint="Bedroom] }
1 Like
Thank you so very much!
It seems the roomHint doesn’t do anything in the Google Home app, although I did as you said (plus a missing quote at the end), then re-linked OpenHAB and it said it found 1 device
Switch Light_UL_BedroomBedSwitch "Bedroom Bed Light" (UL_Bedroom, Lights, UL_Bedroom_Lights) { channel="tplinksmarthome:hs105:UL_Bedroom_Bed_Light:switch", ga="Light" [roomHint="Bedroom"] }
Woo! Now to go through and do that with everything else.
I really appreciate your help, will be nice to have Google integration back again.
It inserted the items into the Rooms in Google for me (but you need to have created the rooms obviously)
That’s strange, I used all the exact room names that I previously did, but yeah, I had to re-add them to each room individually. Maybe because somehow my OpenHAB became unlinked when I tried to re-link it. (It didn’t show up under “Linked Services” under Works with Google, probably because there were no items, when I went to try to link it again before checking the forums here, maybe it cleared things.)
None the less, I really appreciate your help, all 54 devices are now back in the Google Home app and working correctly again. Took awhile to edit all my items files and add them back to their appropriate rooms and such.
I unlinked too. I ended up using search and replace but, because I followed the advice to use multiple items files, I had to do it 12 times for my 60+ devices.
Just wish I knew what had changed
You need to have strucureHint too (and a ‘,’ which I missed
{ ga=“Light” [structureHint=“Home”, roomHint=“Bedroom 1”] }
Hi, so I got the same problem of google unkinking from my home some week or so ago2 , and I just sat down to fix it. Of course as I setup that years ago I still have the old format of tags like [“Switchable”]. Are those now retired and not coming back? Am I forced to upgrade to metadata descriptors in the channel?
Since I rely on one very old binding I still run on on OH 2.4 (and partialy due to the golden rule “if it ain’t broken don’t fix”)
Does anyone knows if the new format is available to OH 2.4 installs or the GA integration is now only for the OH3 users?
Yes, you need to update to metadata.
It should work in 2.4 just fine.
FYI, if you upgrade to OH3, you can use the remote binding to connect to a second server running OH2, so that you can keep your old binding running.
1 Like
Thanks, indeed it works with just a simple update to the items file, and “sync my devices” magic sentence. I was somehow over pesimistic about that.
1 Like
Hi,
Thanks for the information - it really helped to reuse google home.
However, some of the switches appear in google home application but they are offline.
I am using “virtual switches” to open shutters by voice command, each Switch triggers a rule that open/close the shutters that I want to open/close.
for some reason only the first virtual switch is working - all the rest appear offline in the google home app.
Originally it was defined with [“Switchable”]:
Switch g1F_SHUTTER_VOICE_CTRL “1F shutters” (gStam) [“Switchable”]
Switch gKITCHEN_SHUTTER_VOICE_CTRL “kitchen shutters” (gStam) [“Switchable”]
Switch gLIVING_ROOM_SHUTTER_VOICE_CTRL “Living room shutters” (gStam) [“Switchable”]
I updated the definitions according to the suggested in the topic:
Switch g1F_SHUTTER_VOICE_CTRL “1F shutters” (gStam) { ga=“Light”}
Switch gKITCHEN_SHUTTER_VOICE_CTRL “kitchen shutters” (gStam) { ga=“Light”}
Switch gLIVING_ROOM_SHUTTER_VOICE_CTRL “Living room shutters” (gStam) { ga=“Light”}
The only thing I can think of is that if the switches don’t have an on/off state, Google might not know what to do with them. Try toggling them in openHAB and then see if they show up.
Thanks,
I don’t use these switches in the sitemap. These switches are only controlled by voice using the google assist and perform some real shutters action accordingly. I have noticed that if I try to press the “virtual switch” quickly after it appears on the google assist, I can toggle it, although the switches are offline in the google home app. I managed to control the shutters by voice. It also worked after RP3 reset.
I would also second what was said already. Having items with no state can lead to unexpected behaviors in Google home. As it tries to query the state of the item and interpret the value, a NULL (default for new items) will end up in an error. Still, I am unsure if this would end up in an offline state. So it not has to be the reason.
As I wrote, it worked well before with the “switchable” tags and it seems to work again.
1 Like
it just happened to my. Gonna edit my configuration now to use metadata.
It did work 
Still on openhab2.4, need to upgrade, but so many things to doo…
Full example:
Location: /etc/openhab2/items$
File name: Google.items
Dimmer ZW_DI_Slaapkamer_Dimmer1 "Masterbedroom light" { ga="Light" [ roomHint="Masterbedroom" ] }
Switch ZW_SW_Overloop_Switch1 "Halway light" { ga="Light" [ roomHint="Halway" ] }
Dimmer ZW_DI_Entryway_Dimmer1 "Entryway light" { ga="Light" [ roomHint="Entryway" ] }
Dimmer ZW_DI_LivingRoom_Dimmer1 "living room light" { ga="Light" [ roomHint="living Room" ] }
Dimmer ZW_DI_DiningRoom_Dimmer1 "Dining room light" { ga="Light" [ roomHint="Dining Room" ] }
Dimmer KitchenLight_Dimmer1 "Kitchen light" { ga="Light" [ roomHint="Kitchen" ] }
Dimmer ZW_DI_Office_Dimmer1 "Office light" { ga="Light" [ roomHint="Office" ] }
Dimmer ZW_DI_GardenSP_Dimmer1 "Garden spots" { ga="Light" [ roomHint="Back Garden" ] }
Dimmer ZW_DI_Scullery_Dimmer1 "Scullery Light" { ga="Light" [ roomHint="Kitchen" ] }