search

priknr1 / me.zwave

app for Athom's Homey for the zwave.me devices
0 stars 4 forks source link

Slow response for WALLC-S devices and fast battery drain #4

Open bm480 opened 7 years ago

bm480 commented 7 years ago

I have Homey 1.3.1 and ZWave.ME 0.1.1 installed and since release 1.3.1 of Homey experiencing the following issues:

  1. Switches are directly associated with Fibaro dimmers, but after a few (10-20) days not functioning any more. That is, when someone presses one of the buttons nothing happens.
  2. There is no low battery report in Homey.
  3. Sometimes, when pressing a switch it takes a while (2-10 seconds) before the dimmers respond.
  4. Also, sometimes the dimmers respond the first time a switch is pressed but don't respond to any presses after the first time it was presses.
  5. After replacing the battery I'm able to make the switches operate normally again.
  6. Some switches (either close or far away from Homey) do not display this behaviour.

My guess is that Z-Wave message handling is currently not being handled very efficiently. In the Homey "Network Graph" it is shown that nodes which are relatively far away from Homey communicate with Homey directly while it would be more efficient to communicate via another node. But this may not be the root cause, since some switches that are located in close vicinity of Homey (only 3 meters away) also display the same behaviour.

I'm not sure wheter this effect should be contributed to Homey version 1.3.1 and its changed Z-Wave implementation or the ZWave.ME app in particular. However, I'm currently only experiencing issues with the WALLC-S and WALLC-S v2 switches while my Fibaro and Aotec multisensors (also battery operated devices) are working without problems at this moment (knock on wood).

I think this may require much more investigating to find the cause of the problem. Any suggestions on how to proceed are very much welcome!

bm480 commented 7 years ago

After returning from holidays last week, I discovered that the batteries of all my WALLC-S v2 (with the exception of 2) were almost depleted (which is also visible in the battery status graphs of Homey) and the switches did not function anymore. After replacing the batteries normal operation was restored. I found out that the wakeup time of most devices was set to a value of 1800 (probably by default), which is quite often. However, I also found out that the value of 1800 is not an allowed value because upon changing the value I got a warning saying that the nearest allowable value was 1920. So it may be possible that 1800 was rounded internally to a value less than 1800. Could this be a problem in the ZWave.ME application? Maybe implement a warning for values lower than say 3600? Is the wakeup time limited to certain values in any way?

Once a day should be enough for reporting battery status and I've changed all wakeup times to a value of 86400. Now let's wait and see if this helps.

bm480 commented 7 years ago

Looking at the Insights for Battery levels, it seems that by the end of May levels are dropping rapidly:

chart

bm480 commented 7 years ago

At 4th of August I've replaced all batteries and configured the wakeup-times to 84600. So I'm a little bit surprised that Insights is giving me multiple battery level reports per day:

chart 1

knipsel

bm480 commented 6 years ago

The changed Wakeup interval setting might not have been activated (see #7).