Any consequences to NOT writing updates to wireless devices?

[sorka]

I'm doing my yearly replacement of my PLM...actually in this case it was last replaced in March.

The last few times I've done this I've just simply not written updates to motion sensors. They continue to work fine. I tried it on the open close sensors and leak sensors and same thing. Everything works fine.

Obviously this won't work on devices that the PLM needs to change the state on as the addresses would be different. The only consequence I can think of is if the PLM receives a message and then tries to respond. The response will go unheard.

 

What's worse, one of my most recent water sensors is BEHIND a built in refrigerator IN a wall sitting on the wood stem on the floor of the wall interior. I recently had a frig water valve leak and it caused quite a mess because the water went where there wasn't a sensor. This was the ONLY water supply in the entire house that didn't have a leak sensor and is the ONE place where I needed it.

It's a two hour job to pull the built 48" refrigerator back out just so I can hold the button for 3 seconds. I should have been smart and soldered leads on the board where the switch hooks up to create remotely located switch that I could get to.

 

[sorka]

Oh, and none of these devices are part of any scenes. Just realized the scenes wouldn't work properly if you didn't update wireless devices part of scenes.

[kclenden]

I'm running v5 of the firmware, and under Action->Your Devices there is a "Write Changes" option.  I'm not sure if this is available in V4.

I think the only reason you need to press the SET button on wireless devices is to wake them up so that they can receive the updates.  Whenever a motion sensor senses motion it wakes itself up to send an "On" command.  It remains awake for a little bit of time after that.  So all you have to do is look for the motion sensor to switch on and then write updates.  Something like:

If
     'Motion Sensor' is switched On
Then
     Set 'Motion Sensor' Write Changes
Else

You could do something similar for your leak sensors, but instead of looking for it to switch on, you could look for the heartbeat, though I'm only guessing that a leak sensor wakes itself up to send a heartbeat.

[sorka]

If it was possible to do such a thing on Insteon devices without having to hold the button for 3 seconds, why wouldn't the ISY just do it automatically? It already knows when it needs to and for which devices so why not just have it do it as soon as a device reports in with a state change or heartbeat?

[Techman]

17 minutes ago, sorka said:

If it was possible to do such a thing on Insteon devices without having to hold the button for 3 seconds, why wouldn't the ISY just do it automatically? It already knows when it needs to and for which devices so why not just have it do it as soon as a device reports in with a state change or heartbeat?

 

You can use this simple program to write updates to your motion sensor without having to press the set button. 

 

If
        Control ' Motion Sensor' is switched On
 
Then
        Set 'Motion Sensor' Write Device Updates
 
Else
   - No Actions - (To add one, press 'Action')
 

 

[larryllix]

11 hours ago, Techman said:

 

You can use this simple program to write updates to your motion sensor without having to press the set button. 

 

If
        Control ' Motion Sensor' is switched On
 
Then
        Set 'Motion Sensor' Write Device Updates
 
Else
   - No Actions - (To add one, press 'Action')
 

 

If your battery devices don't support that (my 12 MSes don't) you will end up with an ISY with a flooded to do list, that will bog down your system so badly that a simple MS to light scene will take over 30 seconds to get a simple light on.
These features can be a dangerous ones and the explanations are not good in the admin console.

[Techman]

3 hours ago, larryllix said:

If your battery devices don't support that (my 12 MSes don't) you will end up with an ISY with a flooded to do list, that will bog down your system so badly that a simple MS to light scene will take over 30 seconds to get a simple light on.
These features can be a dangerous ones and the explanations are not good in the admin console.

They made some hardware changes on the MS a few years ago. Some of the older MS will support the write update program. The only way to find out is to give it a try on a MS that has pending writes.