Watercop zwave valve driver wrong state display in the app

Hi
@nayelyz
@Mariano_Colmenarejo if you can do somethings?
@AlejandroPadilla

I have a problem with the smartthings zwave valve driver.

The valve show open when it’s closed or closed when open , sometimes showing the right state .

I’m trying to automate something’s and can’t use it now and I have 2 of those valve …
Here the fingerprint of my valves.

Thank you

Hi @Sylvain

Your valve works in reverse because the stock driver for manufacturer 0x0084 and 0x0027 reverses the operation by running the “inverse_valve” subdriver.

 can_handle = function(opts, driver, device, ...)
    return device.zwave_manufacturer_id == 0x0084 or device.zwave_manufacturer_id == 0x027A
  end
}

return inverse_valve

May not all models of that manufacturer work in reverse and need to modify?

Could the device have some configuration parameter that reverses the operation?

Hi thank you to take a look @Mariano_Colmenarejo

Here is what I found , don’t know it can help me !!
Thank you

Screenshot_20230617_143633_Drive|253x500

Or maybe I can remove the reverse operation in the smartthings driver and publish that on my channel ?

Sorry @Sylvain, I can’t, I don’t have access to the cli, I’m really sorry since changes in samrtthing are slow and I understand your problem.

Maybe one of the developers, who also know how to do it, can help you fix it temporarily.

It is a change that takes 1 minute to make.

If they don’t, when I can I will.

@Mariano_Colmenarejo I can do it if it’s only to remove the reverse action
I will try
Thank you

1 Like

@Sylvain

I already have access to the CLI, do you need me to modify the driver or have you already fixed it?

UPDATE:
I publish the corrected version in case you need it.
I’m going to sleep, it’s already very late here

───────────────────────────────────────────────────
 Name         Z-Wave Valve-Sylvain
 Version      2023-06-17T22:49:14.724159466
───────────────────────────────────────────────────
1 Like

@Mariano_Colmenarejo

Was running your driver and both valve switch itself.

I will run cli logs and see what happen when they do that

Hi @Mariano_Colmenarejo.

I was wrong .With your driver it stay at the reverse state . At least I will work .

I think the fix that you remove was ok but for some reason it will reverse at some times .

I’m trying to have log …

There some log

at 2023-06-19T07:45:05 the valve lost connection , that is a problem since the dth and nobody solved it . Forget this since i dont think there a solution .

connecting… connected
2023-06-19T02:47:00.140874400+00:00 TRACE Z-Wave Valve Received event with handler capability
2023-06-19T02:47:00.141822192+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received command: {“component”:“main”,“command”:“refresh”,“capability”:“refresh”,“positional_args”:{},“args”:{}}
2023-06-19T02:47:00.176283692+00:00 TRACE Z-Wave Valve Found CapabilityCommandDispatcher handler in zwave_valve
2023-06-19T02:47:00.240212817+00:00 TRACE Z-Wave Valve Z-Wave command(9a817115) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-06-19T02:47:00.240746817+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-06-19T02:47:00.245272525+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T02:47:00.360641025+00:00 TRACE Z-Wave Valve Z-Wave command(9a817115) transmit status: TRANSMIT_COMPLETE_OK
2023-06-19T02:47:00.376739817+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T02:47:00.378641150+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T02:47:00.386482692+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve → Inverse Valve
2023-06-19T02:47:00.387337858+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“closed”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T02:47:00.389146650+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T03:00:00.533065782+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T03:00:00.540656490+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T03:00:00.593429074+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T03:00:00.594235907+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T03:00:00.614287115+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T03:00:00.773145407+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T03:00:00.773734240+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T03:00:00.852109199+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T03:00:00.898520782+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T03:00:00.907393324+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T05:04:59.726713200+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T05:04:59.727385950+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T05:04:59.750891617+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T05:04:59.755216992+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T05:04:59.756086658+00:00 DEBUG Z-Wave Valve Hose de Jardin device thread event handled
2023-06-19T07:38:25.719635431+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:38:25.720213806+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T07:38:25.735266889+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T07:38:25.735999473+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T07:38:25.737931056+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T07:38:25.989743806+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:38:25.990295931+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T07:38:26.002549223+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T07:38:26.004318514+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T07:38:26.005699556+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T07:41:44.596603985+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:41:44.598755068+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T07:41:44.619472526+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T07:41:44.619991401+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T07:41:44.626325651+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T07:41:45.223923359+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:41:45.226252109+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T07:41:45.240675068+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T07:41:45.241330484+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T07:41:45.247982984+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T07:41:45.540823776+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:41:45.541403443+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T07:41:45.606672984+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T07:41:45.607130609+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T07:41:45.617231859+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T07:45:05.311402313+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T07:45:05.315379979+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {cmd_class=“METER”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, err=“\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x62\x75\x66\x2E\x6C\x75\x61\x22\x5D\x3A\x37\x33\x34\x3A\x20\x62\x75\x66\x66\x65\x72\x20\x74\x6F\x6F\x20\x73\x68\x6F\x72\x74\x0A\x73\x74\x61\x63\x6B\x20\x74\x72\x61\x63\x65\x62\x61\x63\x6B\x3A\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x34\x37\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x3C\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x34\x35\x3E\x0A\x09\x5B\x43\x5D\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x27\x61\x73\x73\x65\x72\x74\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x62\x75\x66\x2E\x6C\x75\x61\x22\x5D\x3A\x37\x33\x34\x3A\x20\x69\x6E\x20\x75\x70\x76\x61\x6C\x75\x65\x20\x27\x64\x65\x73\x65\x72\x69\x61\x6C\x69\x7A\x65\x5F\x62\x69\x74\x73\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x62\x75\x66\x2E\x6C\x75\x61\x22\x5D\x3A\x37\x37\x33\x3A\x20\x69\x6E\x20\x6D\x65\x74\x68\x6F\x64\x20\x27\x72\x65\x61\x64\x5F\x62\x69\x74\x73\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x67\x65\x6E\x65\x72\x61\x74\x65\x64\x2F\x4D\x65\x74\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x34\x35\x3A\x20\x69\x6E\x20\x6D\x65\x74\x68\x6F\x64\x20\x27\x64\x65\x73\x65\x72\x69\x61\x6C\x69\x7A\x65\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x34\x37\x36\x3A\x20\x69\x6E\x20\x66\x69\x65\x6C\x64\x20\x27\x5F\x70\x61\x72\x73\x65\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x67\x65\x6E\x65\x72\x61\x74\x65\x64\x2F\x4D\x65\x74\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x32\x32\x3A\x20\x69\x6E\x20\x6D\x65\x74\x68\x6F\x64\x20\x27\x69\x6E\x69\x74\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x67\x65\x6E\x65\x72\x61\x74\x65\x64\x2F\x4D\x65\x74\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x31\x32\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x3C\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x67\x65\x6E\x65\x72\x61\x74\x65\x64\x2F\x4D\x65\x74\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x31\x39\x39\x3E\x0A\x09\x5B\x43\x5D\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x27\x63\x6F\x78\x70\x63\x61\x6C\x6C\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x37\x31\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x3C\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x36\x37\x3E\x0A\x09\x28\x2E\x2E\x2E\x74\x61\x69\x6C\x20\x63\x61\x6C\x6C\x73\x2E\x2E\x2E\x29\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x64\x72\x69\x76\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x34\x39\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x3C\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x7A\x77\x61\x76\x65\x2F\x64\x72\x69\x76\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x34\x35\x3E\x0A\x09\x5B\x43\x5D\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x27\x63\x6F\x70\x63\x61\x6C\x6C\x27\x0A\x09\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x64\x72\x69\x76\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x37\x36\x39\x3A\x20\x69\x6E\x20\x66\x75\x6E\x63\x74\x69\x6F\x6E\x20\x3C\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x64\x72\x69\x76\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x37\x34\x34\x3E”, payload=“!”, src_channel=0}
2023-06-19T07:45:05.329543354+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T08:20:02.084924974+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T08:20:02.087103557+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T08:20:02.098794765+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T08:20:02.100505057+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T08:20:02.104879474+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T11:55:41.407441296+00:00 TRACE Z-Wave Valve Received event with handler capability
2023-06-19T11:55:41.408429837+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> received command: {“component”:“main”,“command”:“refresh”,“capability”:“refresh”,“positional_args”:{},“args”:{}}
2023-06-19T11:55:41.409555671+00:00 TRACE Z-Wave Valve Found CapabilityCommandDispatcher handler in zwave_valve
2023-06-19T11:55:41.445839921+00:00 TRACE Z-Wave Valve Z-Wave command(4f78f3c2) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-06-19T11:55:41.500571421+00:00 INFO Z-Wave Valve <ZwaveDevice: ee235176-3061-48b1-96b7-82dd9e13db7b [3F] (Valve a Eau Piscine)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-06-19T11:55:41.504807171+00:00 DEBUG Z-Wave Valve Valve a Eau Piscine device thread event handled
2023-06-19T11:55:41.560510129+00:00 TRACE Z-Wave Valve Z-Wave command(4f78f3c2) transmit status: TRANSMIT_COMPLETE_OK
2023-06-19T14:20:01.686654636+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-19T14:20:01.687304594+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-19T14:20:01.741934969+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-19T14:20:01.742606178+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-19T14:20:01.745362969+00:00 DEBUG Z-Wave Valve Hose de Jardin device thread event handled
2023-06-20T03:18:29.547551352+00:00 TRACE Z-Wave Valve Received event with handler unnamed
2023-06-20T03:18:29.548575769+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-06-20T03:18:29.549580519+00:00 TRACE Z-Wave Valve Found ZwaveDispatcher handler in zwave_valve
2023-06-20T03:18:29.562971644+00:00 INFO Z-Wave Valve <ZwaveDevice: 06b1a9f1-b9f6-4bd8-9971-7ffbfdfcc8a9 [3B] (Hose de Jardin)> emitting event: {“capability_id”:“valve”,“state”:{“value”:“open”},“attribute_id”:“valve”,“component_id”:“main”}
2023-06-20T03:18:29.563982561+00:00 DEBUG Z-Wave Valve Hose de Jardin device thread event handled

1 Like

I see in the logs of stock driver Zwave Valve:

  • According to the captures of the manual that you put, the c.c. Binary_switch and Basic value 0xFF => Closed and 0x00 => Open.
  • It need to invert the state refer to defualt libraries, just like the stock driver does, but the Driver only handles the C.C. Binary_Switch and the device is also replying with C.C. Basic and therefore outputs the reverse state to the Binary_Switch.

I am going to leave the can_handle as it was in the stock driver and I am also going to handle the C.C. BASIC.

When I have it I post it

@Sylvain

Try this driver version

───────────────────────────────────────────────────
 Name         Z-Wave Valve-Sylvain
 Version      2023-06-20T10:48:48.938471358        
───────────────────────────────────────────────────
1 Like

Hi @Mariano_Colmenarejo

So far so good :+1:t2:. Can you just take a look at the disconnection . It happen one time with the logs that I post here .
Don’t waste time on that but if you see something that can be a quick fix .

I put those 2 valve on switch and trigger on off a midnight to patch this fault.

Big Thank you again !!!

I see this message from the c.c. METER, which according to the screenshots of documentation posted of this device should not have implemented.
The message contains an error report, I don’t think it has anything to do with your disconnection problem, but I don’t know.

According to the default libraries, the online offline status of the zwave, zigbee and matter devices is automatically marked by the values of the radio signal level.

--- Mark device as being offline and unavailable
---
--- Only useable on LAN type devices, calls to this API for ZIGBEE, ZWAVE, or MATTER type
--- devices are ignored as their online/offline status are automatically determined at the
--- radio level.
---
--- @return status boolean Status of whether the call was successful or not
--- @return error string The error that occured if status was falsey
function Device:offline()
    return self.device_api.device_offline(self)
end

In zigbee device messages are received periodically according to the installation configuration.

In this Zwave device I am not clear which radio messages are received periodically, since nothing is configured in the installation.

In the devices with battery, the wakeUp is received periodically, but in those powered by an external source, I don’t know how the hub is informed periodically or if the hub interrogates the devices on its network periodically.

If you provide me with the complete documentation I can try to see if there is something.

I had an experience with a zwave button, it worked perfectly and in one of the debug tests of a driver I was changing the wakeUp intervals and when I finished I left it as it was originally, but from that moment the button was marked offline after being passed about 25 minutes from the last pulsation. the button went back online as soon as I pressed any button and went back offline after 25 minutes or so.

The solution was to exclude it from the network and pair it again. Everything worked perfectly again and it has never been marked offline again and I never see periodic messages in the logcat of the driver for that button, in which the only this device is paired. So I think there must be something that analyzes the zwave network and marks it offline and online.

I would try to install it from scratch near the Hub to see if it is solved.

Sylvain, I have been struggling with the problem of the FortrezZ Z-Wave Valve reporting status incorrectly for months, and worked with SmartThngs support for 6-7 weeks to find a solution. While a newer driver was released since the problem appeared, it did not correct the problem.

This thread gives me hope! Do you feel that your latest modification has solved the reporting status problem, and would you be willing to share your modified driver with those of us with these FortrezZ valves? Would be most appreciated.

It’s not me , big thanks to @Mariano_Colmenarejo .

Still testing . It only happen one time , but I’m not shure that the driver fault .
Mine is a watercop , maybe the fingerprint match you have to try.
So far so good try in that channel
The driver as my name on it .

@Mariano_Colmenarejo Did you ever publish the Z-Wave valve driver that supports the WaterCop valve?