I'm sorry it seems like [the device] is currently unavailable

#1

Whenever I ask my Google Home to control a group. The Google home reports the following back. Surprisingly, the command I select does get passed along to the group device. Then, if I issue a similar command to the device in the next few minutes, that command does not return this error.

When I open the Google Home app on my phone before I issues these kinds of commands, the device doesn't correctly report back its current status, e.g. the dim level of the bulb. (The same is true when I look at its status in HomeKit on my iPhone through HomeBridge.) After issuing the command, I can see a current status.

I'd also note that both Google Home and HomeKit believe that my bulbs have the ability to change hue and color temperature, which they do not.

Any input on what to adjust so that:

  1. I do no receive this error message from Google Home
  2. These devices report back status to Google Home or HomeKit
  3. These devices don't report things like hue and color temperature to Google Home or HomeKit

Thanks so much!

#2

I have the same issue with HomeKit. I got used to just waiting upwards of 20 seconds for HomeKit to detect devices. I think the issue is with HomeBridge or MakerAPI.

I do not, however have any issues with GH communicating with any devices. Most of my devices are exposed from Hubitat To GH via the Google Home app. Some are integrated via GH cloud. Neither has any noticeable delay or inconsistent behavior. Is yours integrated directly with Hubitat?

#3

The only devices I have issues with are three groups of bulbs, all in Hubitat. These bulbs (some Cree and some Sengled) are paired with Hubitat over Zigbee, grouped together, and then connected to Google through the Hubitat Google Home integration. Using the Google Home, the groups are having issues, but the individual bulbs, also exposed through Hubitat, work just fine.

#4

Bump.