Write Device Update - Remote Battery Updating

[Teken]

I wanted to create a tracking poll to see how many people have been using the remote write device update feature in the 994 Series Controller.

 

For those not familiar, Smartlabs introduced this feature in House Linc 2 long ago. When this feature is enabled any pending updates in the system will be pushed to the battery operated device most commonly the motion sensor.

 

Since 4.2.X.X the 994 Series Controller has included this remote update feature in the programs section. As with the HL2 software, it required that the motion sensor be awaken by simply walking past the field of view of the sensor.

 

Once this was done any pending writes would be pushed to the MS. This fantastic feature removed the need for the person to remove the MS, unscrew the back plate, and then push and hold the black set button.

 

For those areas where the MS is mounted high up this is a God send feature!

 

With anything it seems depending upon hardware, firmware, and ISY firmware. There is no hard and fast rule about what amount of (wait) seconds are required to make the write successful.

 

I have crafted a few poll questions in hopes of narrowing down based on a sample size of users what has worked for them in the past. It would be most helpful if you could also state and post up what your program looks like that helps you achieve 100% successful remote write updates to the MS.

 

I pose this question today as I am seeing random results with brand new MS sensors with the exact production date, firmware, and ISY OS. I am trying to narrow down what steps may be required to help me and others in the future.

 

Any insight you have to share please do indicate it below.

[larryllix]

The awareness of the feature was the best part of the poll and I thank you for the information Teken.

 

I remember some  rumblings about this, some time back, but never investigated. I always figured it didn't apply to me or my devices, despite 10 MS units.

Edited December 15, 2015 by larryllix

[GDavis01]

 

 

Since 4.2.X.X the 994 Series Controller has included this remote update feature in the programs section.

 

Teken... can you briefly explain how I can access this feature? I cannot find any reference to this in the programs section! Thanks

[Teken]

Teken... can you briefly explain how I can access this feature? I cannot find any reference to this in the programs section! Thanks

 

Hello GMD99,

 

Sure, here is a image capture where you will find the option. This option is available for all battery operated devices but should be noted anything that that does not have a motion sensor will obviously not wake up until you press the set button.

 

It has also been observed some battery operated devices simply do not accept the remote *write device update* feature.

 

This feature has primarily been used to update the Insteon motion sensor.

 

As stated above it will save a person lots of foot work in high mounted areas.

[Brian H]

Wouldn't the 2843-222 Open Closed Sensor or 2854-222 Hidden Door sensor also wake up if you open the door?

[BamBamF16]

Brian, mine do.

[Brian H]

Thank you for the information.

[Teken]

Brian, mine do.

 

Can you share what your settings are via screen capture. Is the Write Device Update 100% consistent when enabled?

[Techman]

Doesn't the "automatic write to battery operated devices" option in the ISY pro do the same as the write update program?

[jerlands]

Doesn't the "automatic write to battery operated devices" option in the ISY pro do the same as the write update program?

 

I thought the same but apparently not.  I experimented with a 2845-222 door sensor by changing the LED option to on, the update attempted and failed with the ! I then opened the door to trigger On but no update and failed with the small 1011.  So I wrote a "write device updates" program then did the same but this time the update succeeded.  I tried this twice with the program and both attempts went thru.

 

 

Can you share what your settings are via screen capture. Is the Write Device Update 100% consistent when enabled?

 

 

 

Write Updates - [ID 00DB][Parent 00BE]

If
        'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' is switched On
 
Then
        Wait  2 seconds
        Set 'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' Write Device Updates
 
Else
   - No Actions - (To add one, press 'Action')
 

Seemed to work ok..

 

 

Jon...

[larryllix]

If this is equivalent to the device being in linking mode, would a query work in this manner also?

[jerlands]

I changed the program to query but that failed to write.

[Brian H]

Battery devices are in a power saving mode.

A query will not work.

 

This new feature waits until the device wakes up. Like detecting a motion or door opens. Then while it is awake. Starts to write to it.

If memory serves me many of them have a way for the program to keep it awake until turned back to power saving.

[BamBamF16]

Can you share what your settings are via screen capture. Is the Write Device Update 100% consistent when enabled?

That I can't answer. I set a hidden for sensor to update on levels for a light in a scene it controls based on the time of day. Occasionally it doesn't take right away because I have to reopen the door abd close to turn the scene in with new values. Abd the controlled light is in the dog room and I'm not in there.

 

Jeff

[Teken]

I wanted to add some data points in hopes this will save others sometime in this endeavor. Its clear to me this feature requires a little bit of trial and error should a positive outcome be sought.

 

It goes with out saying depending upon the hardware revision, firmware, and production date. This feature may not work on all known battery operated devices in the Insteon line up.

 

The following devices on hand were able to remote *Write Device Update* with various wait times and (IF) conditions in place.

 

Trigger Linc: Production: 3211, Rev 1.3, ISY v.28 Required 1 second wait

Trigger Linc: Production: 0912, Rev 1.5, ISY v.34 Required 0 second wait

 

Open-Close: Production: 2514  Rev 1.9, ISY v.40 Requires 1 second wait

Open-Close: Production: 4114R Rev 1B, ISY v.43 Requires 1 second wait - has no internal pin

 

Motion Sensor: Production: 4309 Rev 2.0, ISY v.00 Requires 2 second wait

Motion Sensor: Production: 3910 Rev 2.0, ISY v.34 Will not update via ISY but will from HL2?

Motion Sensor: Production: 3914 Rev 2.4, ISY v.41 Required 3 second wait

 

So far these are my observations from doing many trials and validation tests. I have several MS sensors as you see above from various production years and firmware. All of these MS could be remotely updated via House Linc 2 software with out issue.

 

When UDI first released this remote update feature these sensors were enrolled back in the day where the 994 Series Controller did not follow the e-docs completely. Meaning the firmware did not query the hardware device for all parameters and hence why we all saw ISY v.00 for battery operated devices.

 

Regardless of that fact when the remote device write update appeared I had no issues in using this feature, none!

 

This past month I moved one of these ISY v.00 sensors to another place and in doing so decided to hard reset the MS and enroll it knowing the ISY firmware would be displayed.

 

As you see high lighted in red (above) it shows up as v.34 in the system.

 

This MS will not remote update at all now using the current firmware in place. All of the other MS still using the older v.00 remotely update just fine. In another related thread people were complaining that when you selected the *Options* tab for the MS a whole bunch of random errors would appear.

 

I will include them below . . .

 

Now, with the MS that were added later which shows the actual ISY firmware when you select the options tab there is no error and the various options do appear with out issue. From this basic test and validation process its clear to me this feature still requires some development and fine tuning.

 

As its quite impossible that existing MS sensors having the v.00 remotely updated fine prior to deleting from the system. Then when adding back into the system that now indicates what ever firmware like above (v.34) this feature no longer works?!?!?

Edited December 16, 2015 by Teken

[wrj0]

This technique also works to update 2852-222 Leak Sensors.  Set program to watch for the heartbeat, wait 1 second, then have the program do the Update Device.

Sure beats running around to all leak sensors after a PLM update; especially for those in hard to reach places like beneath the dishwasher.

[Teken]

This technique also works to update 2852-222 Leak Sensors.  Set program to watch for the heartbeat, wait 1 second, then have the program do the Update Device.

Sure beats running around to all leak sensors after a PLM update; especially for those in hard to reach places like beneath the dishwasher.

 

You know that isn't something I had even considered!

 

Would you be so kind and provide the hardware production, rev, and ISY firmware? I ask because the leak sensor has under gone several firmware updates and this may impact a successful write update.

 

As I have many that span several firmware releases now.

 

NOTE: It was also observed that some of the Trigger Lincs required the program to monitor the closed condition instead of the open condition before it would complete a write device. This is why its important to use both (IF) conditions when appropriate for your environment.

 

It was also noted that sometimes these devices had to be activated several times before the entire write process was completed and the Admin Console would show a successful write.

 

Lastly, do not count on the console to portray the successful write process with out closing out the Admin Console and coming back in to confirm success. As many of us continue to see the Admin Console freeze and not show *current* status until the UI is closed and reopen again.

 

Very frustrating to say the least . . .

Edited December 16, 2015 by Teken

[larryllix]

This technique also works to update 2852-222 Leak Sensors.  Set program to watch for the heartbeat, wait 1 second, then have the program do the Update Device.

Sure beats running around to all leak sensors after a PLM update; especially for those in hard to reach places like beneath the dishwasher.

Sounds great but what are you updating on a leak sensor?

I would assume just links to a new PLM?

[wrj0]

Sounds great but what are you updating on a leak sensor?

I would assume just links to a new PLM?

Correct.  After a PLM failure, a spare PLM was put into place following the Wiki PLM replacement procedure.  Motion sensors and Leak Sensors showed the green Pending Changes Icon.  Enabling a program like the one jerlands posted above, allows the Leak Sensors to be updated without manual intervention on the first occurrence of the Leak Sensor's heartbeat.  After the program performs the Device Update, I include a 1 second wait, and then have the program disable itself.  It will be re-enabled if another PLM has to be put into service.

 

My five leak sensors, purchased at different times, are 2852-222 v.00 and 2852-222 v.41.  Programs run on an ISY 994i/IR PRO v.5.0.2

Edited December 16, 2015 by wrj0

[Teken]

Correct.  After a PLM failure, a spare PLM was put into place following the Wiki PLM replacement procedure.  Motion sensors and Leak Sensors showed the green Pending Changes Icon.  Enabling a program like the one jerlands posted above, allows the Leak Sensors to be updated without manual intervention on the first occurrence of the Leak Sensor's heartbeat.  After the program performs the Device Update, I include a 1 second wait, and then have the program disable itself.  It will be re-enabled if another PLM has to be put into service.

 

My five leak sensors, purchased at different times, are 2852-222 v.00 and 2852-222 v.41.  Programs run on an ISY 994i/IR PRO v.5.0.2

 

I gather you have one of the first leak sensors like me hence why you have one with a v.00? Can you provide the program here for others to follow so its clear how its structured.

 

My intent is to make this thread as helpful and documented as possible for others to follow later on.