Unable to control valve from Dashboard 2.0

Firmware 2.0.8.107, Firefox on Windows 10.

Tried to open the valve from the dashboard, the hourglass came up and never went away (at least not within a few minutes) so I refreshed the browser and the valve never opened.

Went to the device page and opened the valve there, the dashboard updated to reflect the valve was open. Went to the dashboard and closed the valve, it worked. Again tried to open the valve from the dashboard, and experienced the above problem.

All this was from the local dashboard. At work today I used the cloud dashboard to try to open the valve and experienced the same issue, but wanted to test at home with the local dashboard to verify.

Can you screenshot the device details for the device and tell me what driver? Does it support the open and close commands?

It is the built-in Orbit Hose Water Timer, it does support open/close and I can do the open/close from the device page and the dashboard shows the status.


Odd has two opens. Does open from dashboard work or close or neither?

I stumbled across this thread and I appear to be having issues with my Watercop Water Shutoff valve as well. It appears to have started with version 2.0.8 as well (although I haven't tried in some time).

If I click the device in Dashboard 2.0 to manually shut the valve, it gives me the Are you sure prompt. If I select Yes, the valve closes. The icon changes. If I click the tile again to open it and click Yes on the prompt, the tile changes to the hourglass and does nothing.

To get it to open back up, I have to go into the Device details page and click open. It opens and the Dashboard tile updates accordingly.

It is assigned with the Generic Z-Wave Valve driver.

Just thought I would add my 2 cents as well.

Open from the dashboard doesn't work, close from the dashboard does work.

Chuck said in a different post:

With our driver you can tell it to turn on for a specific amount of time and you can also schedule it for even days or odd days or every X days. From what I saw with that other DTH, you could only turn it on for 10 minutes at a time, which seemed kinda pointless.

So one "open" has no parameters and the other has length of time to stay open.

Can you go into the device and set a defaultWaterTime value to say, 10 or whatever and click save.

Test that dashboard now sends the open command properly.

Think the issue is in the driver, but this would confirm it.

Thanks,

Patrick

@patrick,

I am having a similar but a tad different issue with my valve and dashboard as outlined in this post above:

Is this using the built in driver or something else? And any errors in logging or f12 javascript console?

Built-in generic Z-wave valve driver.

Didn't see anything in the logs, but I will double check that and the F12 console. Using Chrome browser too.

Also, can you confirm that when you click open (in the device details) that is shows valve: open or valve: closed and nothing else? Is it possibly showing valve:opening or valve:closing or even valve: unknown?

Wanted to add that the Dome Valve has the same issue. Can close it with dashboard but will not open with dashboard. Have to go to the device page to open it.

Ok, in device details when I click open or close, it performs correctly. It shows the following:

switch:on
valve: open

or

switch: off
valve: closes

Don't see anything in the logs at all. In F12 console there are no console errors but I do find the following in the Network tab:

http://192.168.86.5/apps/api/705/dashboard/709/command

Response is:

{"result" : "unknown or unauthorized command"}

BTW, I don't ever recall seeing the Switch state or command in the driver before. (Although I could have overlooked it)

That's the clue. Does it ever change to closed?

Typo lol. It says closed. Never shows opening or closing. It only displays open or closed.

Thanks for testing, ok, so we need to then look at what dashboard is seeing. Open the gear top right, go to advanced, click devices and scroll down to the valve device. Can you screenshot the attributes / states and any history please.

Looking to make sure dashboard sees the same thing for valve: open and closed. That history isn't showing other events somehow.

I turned on debug logging for the valve. The following is what shows when I close the valve from the Dashboard.

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:42.082 pm [info](http://192.168.86.5/device/edit/97)Water Heater Valve is off

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:42.068 pm [debug](http://192.168.86.5/device/edit/97)BasicReport value: 255

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:42.066 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2003, payload: FF

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.891 pm [info](http://192.168.86.5/device/edit/97)Water Heater Valve was turned off

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.885 pm [debug](http://192.168.86.5/device/edit/97)SwitchBinaryReport value: 255

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.882 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2503, payload: FF

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.835 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.832 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.635 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.633 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.438 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.436 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.120 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:41.116 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.916 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.913 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.716 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.713 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.509 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.508 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.309 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.308 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.132 pm [debug](http://192.168.86.5/device/edit/97)skip: ApplicationBusy(status:0, waitTime:0)

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:40.115 pm [debug](http://192.168.86.5/device/edit/97)parse description: zw device: 03, command: 2201, payload: 00 00

[dev:97](http://192.168.86.5/logs#dev97)2019-03-29 12:43:39.189 pm [debug](http://192.168.86.5/device/edit/97)close() was called

I'll try the gear thing and get back to ya.

@patrick, is this what you need?

1 Like

I already had a default of 20 minutes set, changed it to 30 minutes but still same dashboard behavior.

@patrick,

Here is something else I found using the F12 console. It may help you track down the issue. It appears the command is not being passed from the Dashboard tile to open the valve.

When I click the tile to Close the valve, the payload being sent is: {"id":97,"cmd":"close","secondary":""}

But when I click the tile again to open the valve, this is what is sent: {"id":97,"cmd":"","secondary":""}

As you can see, the cmd is blank. It returns {"result" : "unknown or unauthorized command"}

Scott

1 Like