My 12 Hank door sensors work perfectly integrated in my Domoticz V4.9700 network on Raspberry Pi with an Aeotec Gen 5 controller except that ...
the updating of the Wake-up interval: parameter 2000 doesn't work (even when the device is well awaken) when I try to put it to a value different from the default 0 value (I would like to put it to 86400 seconds meaning every 24 hours)
Has someone experienced a similar problem ? Tested this Domoticz function ? A solution to propose ?
All advice will be very welcome.
Wake-up interval updating on Hank HKZW-DWS01
Moderator: leecollings
-
- Posts: 1
- Joined: Wednesday 30 January 2019 21:44
- Target OS: Linux
- Domoticz version:
- Contact:
Re: Wake-up interval updating on Hank HKZW-DWS01
I have exactly the same problem and over 10 "Hanks".
I started with HA+OZW, then thinking it was open source issues, moved to HomeSeer and now using the official PC Controller 5 from the Z-Wave SDK.
The sensor will not respect the seconds payload of the WAKEUP_SET command. I can see this in the official PC Controller utility. It responds with OK but subsequent WAKEUP_GET gives your a WAKE_RESPONSE with the seconds as all zeroes. What's interesting is that the NodeID payload is stored so responses can be rerouted to another node but the seconds reported is always zero. MonoPrice here in the US is ignoring me (It's their NoName Door/Window sensor) but I did get a response from HankTech asking for a Zniffer log. I'm ordering a fresh Z-Controller so I don't brick my current one since Zniffer requires you to reflash the controller firmware. Really frustrating.
Anyway, it looks like a bug in the sensor firmware to me. I'm in the process of trying to return them all to MonoPrice since their specification that say you can change the wakeup interval is a lie
Hey what is your firmware on the Hank. I'm getting v1.05 and wondering if there is a newer firmware. I did find a file labelled 2.0.otz (Compressed OTA firmware) that matches the hardware ID of the Hank but flashing the 2300+ blocks with a success (0xFF) in the end doesn't change the v1.05 repted.
Had anyone ever been able to change the wakeup interval on any HKZW-DWS01 (i.e MonoPrice Z-Wave Plus Door and Window Sensor, No Logo)?
I started with HA+OZW, then thinking it was open source issues, moved to HomeSeer and now using the official PC Controller 5 from the Z-Wave SDK.
The sensor will not respect the seconds payload of the WAKEUP_SET command. I can see this in the official PC Controller utility. It responds with OK but subsequent WAKEUP_GET gives your a WAKE_RESPONSE with the seconds as all zeroes. What's interesting is that the NodeID payload is stored so responses can be rerouted to another node but the seconds reported is always zero. MonoPrice here in the US is ignoring me (It's their NoName Door/Window sensor) but I did get a response from HankTech asking for a Zniffer log. I'm ordering a fresh Z-Controller so I don't brick my current one since Zniffer requires you to reflash the controller firmware. Really frustrating.
Anyway, it looks like a bug in the sensor firmware to me. I'm in the process of trying to return them all to MonoPrice since their specification that say you can change the wakeup interval is a lie

Hey what is your firmware on the Hank. I'm getting v1.05 and wondering if there is a newer firmware. I did find a file labelled 2.0.otz (Compressed OTA firmware) that matches the hardware ID of the Hank but flashing the 2300+ blocks with a success (0xFF) in the end doesn't change the v1.05 repted.
Had anyone ever been able to change the wakeup interval on any HKZW-DWS01 (i.e MonoPrice Z-Wave Plus Door and Window Sensor, No Logo)?
-
- Posts: 12
- Joined: Saturday 07 November 2015 17:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Wake-up interval updating on Hank HKZW-DWS01
Thank you Mattias.
I am also going to contact the seller (Domotique Store in France in my case)
If they provide a solution I will tell you on this thread.
If anybody else had an idea it will be very welcome.
For the rest the device seem to work well until now (do its job). I only have a battery too rapid discharge problem on one of the 12.
I am also going to contact the seller (Domotique Store in France in my case)
If they provide a solution I will tell you on this thread.
If anybody else had an idea it will be very welcome.
For the rest the device seem to work well until now (do its job). I only have a battery too rapid discharge problem on one of the 12.
-
- Posts: 12
- Joined: Saturday 07 November 2015 17:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Wake-up interval updating on Hank HKZW-DWS01
Hi Mattias,
I interrogated my seller (Domotique Store in France) on the subject.
They told me that it's Hank themselves who decided to drop this capability of imputing a customized Wake-up interval value. They want to keep it at 0.
Therefore noway to change it, parameter 2000 is inactive.
Apart from that they are replacing the one device with failing battery. I am quite happy with that as long as the other ones work well.
I interrogated my seller (Domotique Store in France) on the subject.
They told me that it's Hank themselves who decided to drop this capability of imputing a customized Wake-up interval value. They want to keep it at 0.
Therefore noway to change it, parameter 2000 is inactive.
Apart from that they are replacing the one device with failing battery. I am quite happy with that as long as the other ones work well.
Who is online
Users browsing this forum: No registered users and 1 guest