Teken

As indicated above it can be done but requires technical know how. I offered that resource link to you and others to show case that its being done in Australia by a vendor. It would not be a stretch to say someone who had the will and finances could accomplish the very same task. Having said all of this it should be noted that the current shipping 2413S PLM has the following hardware / feature enhancements. 1. Upgraded capacitors to stave off the 2 year life span. 2. Removal of the ALL ON / ALL OFF command table in hopes of reducing this occurrence.

If you decide to do so it would be great it you could document the process and the final outcome. I am sure that many others with like minds would appreciate your first hand experiences in this endeavor. Blaze a trial and let us all know . . .

Well, perhaps there is a middle ground that can be found. In this resource link it describes a method to use a HUB II with a 994 Series Controller. I would gather the process could be the same for a HUB Pro which is Apple Home Kit enabled: http://forum.universal-devices.com/topic/17271-hub-ii-isy-echo-integration/ You can certainly try with in the 30 day return policy and if it works please do share the outcome and trials with the membership.

Not unless you have the technical skills to do so. NOTE: Here is an example of a company that has taken a HUB and made it into a PLM interface for the 994 series controller: http://forum.universal-devices.com/topic/17549-2242-522-hub-to-isy-serial-conversion/

Are you speaking about Apple Home Kit? If so UDI has no intention of supporting this protocol.

Bringing this back to the top and wanted to know when UDI will support via software the ability to set the second node. As I received a couple more Open-Close sensors and they too do not have the mechanical jumper to enable two node use. Its been more than six months since this thread was first created.

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Restarting_Your_ISY-99i

Specifically the older 2476 ST units that had a built in timer did not have a proper air gap inside. As an aside this device continues to be improperly supported in the 994 Series Controller firmware. When selecting the options tab it will declare a fault which it never did in previous generation of firmware. Once you close the error message attempting to change any value in the 2476 ST device do not take or can be applied.

Glad it all worked out and sorry for the confusion on the sensor wiring. These were really old pictures taken as a means to trouble shoot and recall what position the cables were in case I needed to redo things etc. As you can tell it comes in handy when helping out others. I know its easy to say and read written text over the Interwebs . . . But, sometimes having some visual aids just makes the job easier for everyone. Merry X-MAS . . .

I am a visual learner so here are some old photo's of my jack shaft install. Please note my system was the older model before the whole My Q ever existed. I wired the I/O Linc directly to the main GDO in parallel and works like a champ. This avoided the whole idea of buying another remote to be sacrificed and soldered on to. Sorry the picture isn't the best as it was taken during a power outage in my area and was running on emergency back up lighting which is 25 feet away. NOTE: In the picture you can see I used the N.O. sensor wire. You will need to decide which method works for you in your own environment. For me it made sense that the light on the I/O Linc would light up once the door was open and off when the door was closed. Comes down to preference and if it makes sense to you to have it the reverse . . .

Hello Kevin, Just to clarify the portal is $49.00 for two years not one. So that's $24.50 per year, which as I understand it UDI struggled on whether to have a subscription fee module. In the big picture this should provide a nice revenue stream for the company. Keeping in mind their intent is to continue development so other third party hardware / cloud services can be integrated with the 994 Series Controller. I too can't stand any kind of subscription services! [emoji35] But unlike other companies around the world this isn't a fad or a nice to have service for UDI. It's a long term roadmap that will hopefully allow tighter integration with other third party devices which are all the rage now. [emoji53] Ideals are peaceful - History is violent

Not sure if these are on the list as I quickly reviewed the list above: All, Sump, Fire, Laundry, Generator, Deck, Security, Motion, Hot Water Tank, Clothes, Secure, Enable, Disable, Active, Activate, Deactivate, Solar, PVR, DVR, Rotate, Turn, Restore, Default, Reset.

Just a heads up a dual band 2822-222 I/O linc is in the works from Smartlabs. There is no current ETA of its release or form factor but its safe to say it will probably use the same case as the newer On-Off Module, Range Extender, Lamp Linc, Alert Module, etc. Hopefully it will offer more features and options in the new release besides recycling a new outer case. More than likely it will lose the front convenience outlet unless they actually have the mind set to make the case thicker. If history is any indicator it will have a power draw of <.75 watts, 1000 volt surge rating. It would be really great to see a multi port like the Smartenit device form Smartlabs though.

Did you try the same on a PC? Ideals are peaceful - History is violent

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.

I have been seeing this same issue with back ups too. It has been suggested (assuming this applies to you) that if you have lots of network resources to suspend them. Once that is done try to create a back up . . . If that doesn't work the next step is to disable any programs that might cause a race / loop condition. Doing both should allow you to complete a back up. If neither resolves the issue you should try to do this on a Windows PC. As its been an issue on Mac / Linux box's for random people in the past. Also, it should be noted several releases of that stupid Java has impacted the controller. Which may also be the cause of some of these issues some of us are seeing now. God, I can't wait for Java to just die and go away . . .

If you haven't rebooted the controller do so and try again . . .

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 . . .

LOL . . .

Hello Chuck, Also if it was not made clear if you have a pro version of the 994 Series Controller. You can select the battery icon at the top this will turn every battery device with pending 1011 write icons grey. When you're ready to update those battery operated devices you can select them one at a time for completion. Here is another method you may want to try on a few battery operated devices to save some ladder time: http://forum.universal-devices.com/topic/17600-write-device-update-remote-battery-updating/

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?!?!?

Larry, Simply plug them into any outlet in the home that shows proper coupling / bridging when the 4 tap beacon test is performed. Any other dual band device can be installed where ever you wish. Best practice is to have a plugin dual band device on each corner of the home on all floors, zones, areas. Ideals are peaceful - History is violent

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

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.

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.