tomho

Yep, I see that. Thanks.

Thanks all. I see I may have originally posted this in the wrong forum. I'll pay more attention next time.

Every time I try to access any of the WIKI stuff (wiki.universal-devices.com) I get a 404 Not found or 403 Forbidden error. I've tried 2 different computers and both chrome and firefox (in the last hour or so). Is the site just down, or moved, or something else?

Not a problem I understand, thank you for the reply. As a side note, I am just now trying an Aeotec Nano Dimmer ZW-111-A which seems to be working so far.

Thanks. Learn something every day. My isy is 994i v.5.3.0, and it's Z-wave (21100). If that doesn't answer your question, let me know.

IPapp, did you have any success with this? I am looking for an alternate for the 2442 Micro Dimmer Module since they have been unavailable for a year or so (and I'm guessing won't be ever again).

It's the standard isy, and the two 6 button keypads are the ones that need to write updates, and yes they show the green icon. I'm not to concerned about that, I just do the writes. However, I might have figured out something else as to why the "PLM" stops communicating some time after the power cycle. When I logged onto the admin console I used the event viewer to see what is trying to talk. Twice, maybe 3 times, during those 2 or 3 weeks I have had this issue, I have had a continuous flood of "X10 Status Request" events. It didn't happen every time, so I didn't think much about it. Yesterday it came up again so I tracked down what appears to be causing those. I still had an old Radio Shack plug'n power Remote Controller (shows my age, does anybody even remember Radio Shack?) plugged in to occasionally command some X10 devices. Anyway, unplugging that thing stopped the Status Requests, and so far (fingers still crossed) the PLM failures. I'm guessing here, but perhaps the constant X10 requests some how overloaded or confused the PLM and it just gave up until a reboot cleared it. I'm assuming the X10 thing is random and I don't know what starts it. I do have some X10 devices under ISY control, but those are very rarely used. Anyway, time will tell.

For 2 or 3 weeks now I have been seeing a similar problem; "Can't communicate with..." insteon devices, sometimes all of them. A power cycle (meaning unplug isy & plm, then plug in plm then isy) temporarily fixes the problem (often with a need to 'Write updates' to some devices). So 5 days ago I did the cap replacement, but that didn't fix it. It still works for a few hours, and one time 2 days, but usually by next morning the same thing (can't communicate). My plm is 2413S rev 2.4.

Thanks, I'll give that a try.

Thanks Techman. I'm actually well aware of the discharge characteristics of LI batteries. The problem is that the ISY is not reporting anything about it, it's simply stuck at 100%.

Having solved my wakeup problem, I'll move on to what really started my work on this (and other battery powered Z-wave motion sensors). This is a 4-in-1 Sensor ver 2.0, and I am using v 5.3.0 ISY994i. I see a 'Battery Level' on the 'Notify Sensor' node, but it always reads 100% (sometimes, and on other sensors, it is just blank). Anyway, I substituted a DC variable power supply for the battery, but I could never get any reading other than 100% for the battery level. I adjusted the supply down, incrementally, to about 2.1V at which point the sensor stopped working (ie, sensing motion). I tried normal wakeup interval, manually waking it up, and disconnecting the power and powering it back up (at the lower voltage). I suspect that this feature is just not working here, but thought I would ask anyway.

Thank you for the response Techman, I figured it out. The buttons and data entry for setting the Wakeup interval do work. There apparently is no "parameter #" to set this. I checked Zooz support site and even contacted them. The problem was not paying quite enough attention to the event log. I was experimenting by trying to set either 300 or 900 seconds, not realizing 600 is the minimum and 600 is the step size. So either of those just changed the 'command' to 600. Setting it to 1200 sec works, here is the log. Fri 10/29/2021 10:19:57 AM : [ZWAVE-WAKE 5] Assigning Wakeup Interval 1200 seconds when device wakes up Fri 10/29/2021 10:19:57 AM : [ZWAVE-BATCH 5.000] Write Device Changes pending for ZW005_1 Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Awake with pending work ZW005_1 Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Awake with pending work ZW005_1 Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Wakeup Default Interval 43200 seconds Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Wakeup Minimum Interval 600 seconds Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Wakeup Maximum Interval 604800 seconds Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Wakeup Interval Step 600 seconds Fri 10/29/2021 10:23:30 AM : [ZWAVE-WAKEUP 5] Assigning Wakeup to 1, Interval 1200 seconds

I'm using this 4-in-one Sensor VER 2.0 on the 994i, v 5.3.0. I see from the event log it is waking up every 10 minutes. The manual says it's supposed to be 12 hrs. I have no idea how it got reset or changed (assuming it was ever 12 hr), nor have I found out a way to change it. There is a node (or whatever you call it) called "Notify Sensor" which has some buttons and time setting options for wakeup interval, but those appear to not work. I've tried manually waking the sensor up to write the changes. Is there a parameter # that will change this? I am able to change the parameters, at least the one I tried ("parameter 5").

Thanks again ELA. You are correct, the MSll does update the battery level on about 24 hrs intervals, apparently from the last power cycle. For my original objective, this will work and wrote a program like the one you posted. In the interest of obtaining maximum battery life, I would like to share some additional information I have discovered. If this is repeating other data, please forgive me as I have not been aware of it. When in the 'sleep' mode (meaning just waiting for a motion event), the battery current is about 70uA at 3.0V supply and increases to about 100uA at 2.4V. With no Query, the motion ON event pulls about 35mA for about 0.1 to 0.2 second, and then 20mA for 5 to 6 sec. It then goes back into the sleep mode for the Motion Timeout period (I set it to 40 sec). Then there is another 20mA for 5 to 6 sec activity to send the OFF command. This means a single motion ON & OFF event takes as much power as about 50 min of sleep. With the "Query when Motion is Switched ON" is enabled, it almost doubles the ON event power, 20 mA for 9 to 11 sec. Of course no change to the OFF event. My Wait delay is 1 sec rather than the 2 sec in ELA's program above - don't know if it makes any difference. It does suggest however that to extend battery life, some kind of event counter could be set up to run the Query only after some number of motion events, depending on how much activity one is expecting. Another life extender is possible by changing the "Motion Condition" to something other than "Always". I tested the "Only At Night" mode. When motion is detected in this mode when it is 'daytime' (probably determined by the the Day or Night Threshold values - didn't try adjusting), there is only the 35mA current lasting for 0.4 to 0.9 sec. It does not use either the ON or OFF 20mA current. Of course it reverts to the above when it is night.

Thank you ELA for the information. On my ISY, the "Battery Level" is part of node 1 (as is also Temperature and Luminance), and reads out directly in xx %. I had to add the node for Low Battery Status, I think it's node 3. I also tried playing with the 'threshold' but still never got it to report anything (always blank). I'll try the "...24 hrs.." idea. I did let it run (without cycling) overnight with no update, but never went 24 hrs without a subsequent power cycle. I too found that it would report motion down to as low as 0.76V with a low impedance supply. But by using as little as 5 ohms in series it would not work below somewhere around 2.5V - it would 'lock up' and not recover unless I raised voltage to about 3V.