ELA

Have you turned on the battery node in the MSII? Turn on a level 3 event viewer and confirm that the MSII Query is sending the required data required to load into your variable.

Set your ISY log to level 3 and do the query both on and off grid. Save each log to a file. Compare the two files. 20 seconds for 200 devices is unbelievably efficient. Do have any battery operated RF only devices? My log shows 10 -20 seconds spent just for 1 Motion sensor ( which it cannot reach since it is sleeping).

Satwar, With the new device wired as in the New Device.pdf - 1.Put the negative of your meter on the 24V (-) power supply terminal. 2. Put the positive of your meter on the I2(-) terminal. 3) Record Meter dc voltage with the new device turned off. 4) Record Meter dc voltage with the new device turned on.

Hi Ajax, Thank you for introducing me to the Sk6812 Individually addressable LEDs. I am going to investigate a panel of these LEDs for another project. Good luck on your toe kick project.

SK6812 Individually Addressable Leds seem like fun for the right application. 300 watts to light a stairway is awfully inefficient. Pull up a chair and watch my stairs animation? Most of the LED strip lights are very inefficient. I would not be so concerned about multiple parallel #18 awg or one #8 awg wire. I would be about the fact that a lot of these LED strip lights are basically LEDs in parallel across power/distribution traces that are about the equivalent of a #26 awg conductor (5050 type string). The 18A per 5m string figure is based on no voltage drop across the string ... as in if each individual LED was fed directly by its own external supply. if the overall number of LEDs (300) is kept the same on a 5050 type string... The shorter the length of each "stair" string the more overall current demand there will be (less voltage drop across the string conductors). One 12V - 5050 5M string has about a 3 volt drop across the string conductors themselves. Looks like the SK6812 chip has a constant current source so the two types of strings may not compare very well in terms of current demand vs. length - as long as the voltage is still within their normal operating range. It also looks like the SK6812 string may have wider track widths than the 5050 type for less voltage drop ( since they are only 5V).

I had tested the reaction time of the I/O linc a while back and my notes say it will detect pulses longer than approx. 40 msec in duration. So it can detect relatively short pulses - however as others have pointed out you need to wait several seconds between "taps" to assure that all communication on the overall network have settled down. That amount of time will be variable depending upon how reliable the network communication may be ( retries take time if the network is marginal). I would wait a minimum of 2 seconds between "tap" events. Write some program/s and try it out. You can use a variable that increments when the "tap" is detected and when the second is detected act on that. Remember to reset the tap counter variable both after the double tap is detected and also after a time delay, if a first is detected but the second is not - within so many seconds. Make an attempt at writing the programs. There are lots of people here that can help if you struggle.

search for his thread: The Mysterious Motion Sensor II

I thought this thread was about MSII Battery level? I use this for MSII: The Low_bat_check compares the variable against a low battery percentage constant and alerts when exceeded.

Interesting request as I had thought about wanting the same remote DVM capability for a short term data collection. But never got serious about it. One possibility might be hacking the MSII. Connect into the circuit where the photocell measures luminance levels. Limited resolution of <=255 but may be good enough? Depending upon how much time you want to invest? A lot of low power battery devices need a trigger to wake them up so they can sleep and conserve the battery. You can query an MSII that is powered via the USB cable input any time you want. The downside is that you are not battery powered. You could consider powering with a larger external battery into the USB input via a custom cable. You would have to look at how long the battery might last if this is a long term need. Then you can poll the MSII at intervals of your choosing via a program in the ISY and load the Luminance value ( your hacked analog value) into a variable that you can operate on. Here is some info I collected on the MSII... if it might interest you to look into that idea. https://forum.universal-devices.com/topic/26579-the-mysterious-motion-sensor-ii/

Triacs definitely do have a minimum current - it is called "minimum holding current". Typical max. value for a 12A ( like used in Switchlinc) triac is 30 -50ma. LED lamps draw current in a very non linear fashion that messes with dimmers. OPs LED lamps are 4.8W each - but non-linear current demand. As mentioned try a incandescent in Parallel with the LEDs. A 4W night light load = 33ma

Search for "mysterious motion sensor II" I had detailed my experience there. Running on USB power is most important when experimenting to learn about it.

MSII Battery node &nbsp;test As posted earlier is my experience with the node

Michel, Would you kindly support that statement with just a little more detail? Jlob, Here is some limited information: https://forum.universal-devices.com/uploads/monthly_2019_06/Report5.JPG.0bffdcba5aa49eb54b6ea2b377b21c66.JPG Sorry it has been a while since I tried to link to a older post. This is just a portion of it.

Some more technical info on the MSII for those interested.

Did you experiment with the unit using usb power? While usb connected run the device links report and post.

What are your Motion settings as set at in the ISY configuration? Are you initiating motion during the time conditions at which the sensor is set to detect motion? As a test set the MS II to detect motion "always" and retest. Keep in mind that you will need to wake up the MSII to get it to accept your new settings . (which could be difficult if is not currently reporting motion ) I would recommend temporarily powering one of your devices from USB power while you debug your issue.

Very helpful ... Do you own a MS II? I do not expect UDI to make Smarthome hardware work any different than it does. Simply to explain what the settings in ISY software do or do not do.

Getting a little overdue for some information on this sensor! Several people have asked where is the wiki and I have yet to see a response from ISY folks? Please forgive if I have just missed it. I understand it was not intended to read temperature ... but what about light sensitivity settings? A higher number is more light required to see it as day? Why is there both a day and night setting? Is there some grey area inbetween? I would prefer not to have to experiment with adjusting values and then tripping the sensor to activate a write updates program too many times over several nights.

Hello Frank, Interesting problem. Have you checked your logs to be sure you are not getting unexpected activations.... since it is a float sw. How warm do you think the battery is getting? High temp. can reduce battery life. I would not use a 1.2V battery. Beyond that it may be difficult to troubleshoot without measuring the current drain.

I looked up the number of your device and it is a triggerlinc ( the old name) which they appear to have changed the name. I was thinking you might have been talking about the hidden door sensor. There is some problem with your device or setup that you should investigate. Do you have a program that lets you know if you ever miss a heartbeat ( I had said watchdog, which is another name for heartbeat). You say the sensor is never activated? Did you test activating it to see if you receive the activation's? Check it in the level 3 viewer to see how reliable it is. Do you have a program that runs when the switch is activated? Is there any chance the device is activating too often and you did not know it? It is in a waterproof box ( plastic?) and also waterproofed??. (Can you explain in more detail)? What activates the device? Do you have wires to a remote sw. connected to the device? Something appears to be going wrong with your setup or the device itself. I have 3 of these devices and the batteries last a very long time. Always greater than 1-2 years. They last so long I have not tracked when I replaced the batteries ( but I do with 9V MS sensors since they get changed at a 1-2 yr max interval).

You need to solve why the batteries are draining so fast. Do you have a program monitoring the watchdog? Are they ever not received? What is your communications reliability with that device?

Here is the current demand for a triggerlinc. I would expect it to be similar for the door open/close. As was pointed out you will not have good luck with a 1.2V cell. As I decreased the voltage to the device that can cause it to go into a state where it stays awake for 11 seconds ( while failing to communicate). That will drain the battery much faster.