BoomerangThree

Hi All, I have an Insteon question and thought the experienced folks here could assist. I have successfully upgraded my ISY to the Polisy, now running just the Polisy. 1. The question relates to the Insteon MS II. I have the MS II successfully turning on a Insteon Light Bulb, by linking the MS II directly to the Bulb. It won't turn off then the MS II stops detecting motion. I believe I have read that in order to do both, turn on and off, it will require a scene. Is this correct or am I missing something thru the direct linking process? Thanks for the support.

Holy crap! What a difference between my Verizon SMS and Pushover. With Pushover it's basically immediate to my iPad, iPhone, and Apple Watch, whereas SMS via Verizon takes on average 12-15 secs. Thanks everyone, what a world of difference...

Will be installing pushover soon. Thanks all...

Thanks MrBill, I'll have to give it a try. I have a few alerts coming from programs attached to motion sensors and would like to get the alerts as fast as I can. Right now with Verizon SMS it can take 10-15 secs.

Thanks asbril, I was looking for faster, but if it's not that much faster I can get by with my normal SMS.

I'm looking for a quicker way to send SMS alerts from ISY and came across this thread / Pushover. Looking for any additional recommendations / issues I may run into. I run the BETA versions of MacOS, iOS, iPadOS, in addition to released versions so wondering if anyone else is using Pushover in a BETA environment as well as any other recs / issues. Thanks!

Teken, Powering the MS II with USB definitely makes a difference. As soon as I hooked up power to USB instead of battery, updates from ISY to the MS II were executed the "waiting to write changes icon" changed, I'm able to update even the temperature calibration. Changes are almost immediate where before it would take a minute and appear not to take the changes. The MS II even beeps now to indicate changes were made to it. Thanks everyone, especially Teken and larryllix. Jeff...

All, I have two (2) scenes (Office and Family Room Light) both of which have one (1) LIFX Color Bulb and one (1) Insteon Bulb. The Office scene works with both the Insteon bulb and LIFX bulb coming on via MobiLinc and Alexa. The other scene Family Room Light scene is just a single bulb light with a LIFX Color Bulb in it. 1. The Office scene controls a two bulb lamp, one LIFX Color Bulb and the other a Insteon bulb works just fine. 2. The Family Room light scene controls a one bulb lamp with LIFX Color Bulb and another Insteon bulb. 3. The Office scene works great, the Family Room Light scene turns on the Insteon Light, BUT NOT the LIFX. 4. Any suggestions as to how to fix this. Jeff... UPDATE 1 ========================= I deleted the scene Family Room Light and recreated it, but the issue remains. UPDATE 2 ========================= Restarting Polisy fixed this issue.

Thanks larryllix, 1. Can you point me in the right direction for how to “disable those caching functions”?

Verification of the following? Just wanted to verify based on others experiences. 1. A factory reset is safe with the backup and restore capability? My ISY has experienced a couple slow downs / freezes and if it continues I may try a reset. This might also clear up my “empty slots” on my Polisy also, which UDI is looking into. Sent from my iPad using Tapatalk

Out of curiosity, how do you “turn off writes” and “execute the pending writes via a program”? Always trying to learn.

KISS - Looking good for the following approach. 1. 1st, like others, I had the binary icon associated with my MS II for the longest time indicating that the ISY was having trouble communicating to the MS II. I believe the MS II options were getting updated, but the icon associated with it was indicating that changes were still to be written to the MS II. Well, when I added the 2nd node for both On / Off signals coming from the MS II, the icon changed from binary to communicating or written. Hmmmmm. 2. Then I took a very simple approach, and have a separate program for On and another one for Off. The MS II is configured for a 90 sec timeout and as long as the MS II is sensing motion, it doesn't send a Off signal and I believe the internal 90 sec timeout gets reset every time it senses motion. 3. I'm stress testing now, but so far so good.

So I know see the restriction, thanks to you. When the MS II senses motion, it kicks off its own internal timer, like you said, so nothing is reported or sent to the ISY. If no motion during this MS II internal timer, ISY get's notified of additional motion, but if it's within the MS II timer interval, nothing gets reported to ISY. So, I'm going to try and work with both on / off coming from the MS II and use it's internal timeout. I will set for two nodes, one for on and one for off and work with that. I have seen where this might not reliable, but I'll try anyway. That way, the MS II will do what it's suppose to do and as long as there is motion, it won't report off to the ISY. We shall see.

Hi Teken, Thanks for the reply, support, and experience. So, here is where I'm at; UPDATE: Just for kicks I took the battery out of the Sensor II and back in to reboot it. I don't think this really did the trick, I thought perhaps a reboot would allow ISY to update the timeout parm of the Sensor II. In addition, I increased my counter and now I seem to be getting updates every so many seconds that resets my timer to the timeout duration. Still playing with it, will update again, but I may be close. The MS II has a 15 second timer like you stated. I'm thinking about a similar function as the "tap up on the switch", but with a Alexa voice command that will disable the timer like you recommended. I already have another program that executes every 15 mins to see if it can turn things off after a certain period of time when no motion is detected.

Hi everyone, I'm trying to work with the Sensor II and write a program that will continuously monitor the sensor so that as long as there is motion in the room, the lights stay on. The issue is that the Sensor II will not continuously "report" it's status. I have / or think of I have set the Sensor II to "Never" timeout, thinking that as long as it detects motion it will trigger my program and a counter variable will get reset so that the counter gets reset to the timeout value as long as there is motion. What happens is that the Sensor II reports it's initial motion, the program kicks off, but the Sensor II will not report any additional motion. Seems like it's still on a timeout because when it finishes what I think is it's timeout then it reports motion or no motion again. So the counter gets updated, after a No Motion is reported and so the lights go back on because of the "delayed" motion detection. Make sense? Any ideas how to fix or work around this? Jeff