Google Home <-> Hubitat and "Generic Z-Wave Valve"

šŸ›Žļø Get Help Integrations
1

I have installed both the Google Home and the Google Home Community Apps, and have a consistent issue no matter which app is used - on the Google end, it cannot seem to see the correct status of the "Generic Z-Wave Valve" device - it always reports the status as "closed".

Hubitat has never had a problem with differing between "open" and "closed". The physical device is a "WaterCop", which has worked well for several years. It is correctly represented and properly controlled on the Hubitat device page, 2 different dashboards, etc.

From the Google Home cellphone app, the status is shown as "closed", and I CAN open the valve by pressing "open" from the cellphone app, but the status as shown on the app then reverts to "closed" again when one exits to the device list page. The valve is actually open, verified at the device itself, and the Hubitat device status and dashboards.

The cellphone app will not close the valve (as pressing close does nothing when the status is already shown as closed), unless I first "open" the valve on the "button page" within the app. The valve status (temporarily) shows "open", and then I can close it and get the valve to close.

The cellphone app "button page" will stay in "open" when one pressed "open", and the valve really does open, but exiting out to the device list shows it as "closed".'

So, the bug is clearly on Google's side - is there another "google home device" that I can define this as, and avoid this problem in status reporting?

All I am trying to do here is to get a Google Home speaker set up to verbally report the status of these devices when it is told "Everyone's Away", for example, "Please lock back door as you leave, all other locks are locked, water is shut down, thermostat in away mode". The idea here is to have a single toggle for a non-technical house-sitter that puts the relevant devices into "home" or "away" status. It may be that I need to do everything in Hubitat rules, and simply get a TTS running to spit voice out to the Google Home speaker once it has toggled the "home" vs "away" setting for the Hubitat. Perhaps I am being foolish expecting to leverage the "home" vs "away" features of Google Home.

2

Did you ever figure this out? I just installed one using the generic zwave valve driver and Iā€™m running into exactly this

@mbudnek is there a trick to getting open and closed to report correctly for a valve in your app?

3

There's not really anything special about a valve. I would use an "Open/Close" trait. Exactly what commands to use really depend on the device. There's a valve capability in Hubitat, so assuming the valve implements that you would use valve as the open/close attribute with open and closed as the and open and close as the open and close commands.

In general, my app uses the term "attribute" to mean one of the state attributes under the "current states" section of a device page, "value" to mean the value of one of those attributes, and "command" to mean one of the commands on the device page. The new UI makes it a bit less clear, since it capitalizes everything. You can turn on the "Show raw names" toggle for attributes, but there's no matching toggle for commands.

4

got it, the open/close attribute defaults to "state" and I didn't change it. The device page label is "valve" for the generic Z Wave valve Driver.

@james.fischer changing from state to valve fixed this issue for me, give it a try

5

Changing WHAT from "state" to "valve"? The new interface is too much eye candy, and not enough clarity, so I am completely flummoxed on this. I got this far on the device page within hubitat - is this all one need do?

Screenshot 2025-07-05 100606
Screenshot 2025-07-05 1006061484Ɨ318 21.3 KB