jrainey

Thanks Peter, I feel the same, especially given that my existing devices are dual power.

Thanks Peter, I will check it out. The features of the Nest Protect that interest me are the voice messaging, co detection and emergency lighting. Haven't seen these features together yet in my so far cursory searching. I installed the Kidde detectors about nine years ago. I was disappointed at the time that I was unable to find any models by Kidde or first alert that had either z-wave or Zigbee comms. Hopefully, this capability has been added. Thanks Jack

Thank you for your response. I am not so much interested in matter itself, but I do find the thread protocol very interesting. It appears to me that it is (will be?) very robust and responsive, even more so then either Z-wave or Zigbee. Also, given the support that many major companies have announced for it (and Matter) I believe that a lot of devices will be coming on the market in the future. The reason for the questions is that I am sort of at a crossroads here. I have experienced a number of failures of Insteon devices, and will be looking to replace them. So I am wondering if I should replace them with Insteon, Z-wave (i already have a robust Z-wave installation) try out Zigbee, or go into Thread. I also ask because I love to tinker. What got me started on this particular line of thought is that I will soon be due to replace my smoke detectors. I have been admiring the Nest Protect line, and there has been speculation that it may become available with Thread compatibility. I would love to be able to integrate these (or similar) devices into ISY at some point it the future. Again, thanks for the response, Jack

Hi all Just completed replacement of my Zooz dongle with zmatter dongle. Only glitch was that I had to remove and re-add my three Zooz ZSE29 motion sensors. No problems elsewhere. I have since done a little reading on Thread and Matter, (only scratched the surface really) and I am interested in the future of this ecosystem. Which leads me to the question: Where is UDI planning to go with Thread and Matter? I understand from one of Michel's posts that they have successfully added Thread devices, but this has hurt the performance of the Zigbee network. Not to worry, I am sure it will be resolved. I am wondering, though, where polisy/eisy will fit in this architecture. Questions I have are as follows: -will zmatter act as a thread router? -will zmatter act as a leader? -will zmatter act as a border router -will I be able to share polisy/eisy controlled devices on the thread network? I will likely have more questions as I dig deeper. Just thought I would post this and start a discussion thread. (pun intended). One more question: Where would you like to see UDI go with this new landscaoe? Thanks Jack Rainey

Hi all. Been a long time since I have posted. I am posting because I believe that I am finally ready to migrate from my ISY994i to my Polisy. Current state is as follows: Current: -ISY994i @ 5.0.16c ... 300 series Zwave controller, 2413s PLM -16 z-wave devices, including 4 Yale door locks New: -Polisy @ 5.6.2 (thanks Michel) ... Zooz 700 S2 dongle, 2413s PLM (new-out of the box) I have spent quite a few hours going over as many posts and advice I could find concerning this migration. (special thanks to @dbwarner5 for the excellent guide) I have a number of questions that I expect I can resolve during and/or after migrating, but there is one I would like to clarify a little before I start. This advice comes from the eisy/polisy user guide: "Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are migrating your Z-Wave network You must be using a 500 Series Board in the ISY-994" My question is this: Is this correct? Does the migration process actually require 5.3.4 and a 500 series board to be successful? Follow up question is what will happen if I try to migrate from v5.0.26C with the 300 series? Would appreciate any and all advice or hints you may have. Thanks Jack

Was looking into this topic earlier today. Seems that Mobilinc has switched from (abandoned?) their Mobilinc Pro product for a newer subcsription based product called Mobilinc X. Checked out reviews in the play store, and found that the subscription prices ranged from $9 and change per month, to something over $200 that might have been a lifetime subscription. Average rating was 3 stars, with a lot of 1 star ratings. Most of the low ratings appeared to be objections to the price, many of which had an answer from the company saying that there were a number of payment options available. For my part, I was unable to easily see how much it would cost by looking around the website, so I quickly lost interest.... Jack

Most routers have the ability to reset to factory default settings built into them. My suggestion is that once you have the new router up and running reset the old one to factory default before returning it.

Check out the topic "Strange problem - looking for ideas". This was PLM failure that progressed over many weeks. My suggestion would be to try a factory reset on the PLM, and go through the PM replacement procedure. I was finally convinced that my PLM had failed when it would not reset. Jack

Good point oberkc. There were two differences between the original program and my suggestion though. The first was, as you noted, the use of a scene. The second was moving the timing from the program into the built in timeout function in the motion sensor. I am not sure how aware people are of this feature, and wanted to point it out. Jack

Not sure if this would work, but you can give it a try. 1) Go into the motion sensor options and set timeout to 10 minutes. (from Universal Devices wiki -> linking a motion sensor) Timeout (minutes) - Defines the period of inactivity before the Motion Sensor will send an Off. Default = 1 minute. Range = 0.5 - 120 minutes in 30 second increments. 2) Add a program as follows: if status (motion sensor) is OFF then set scene MasterBathroomAllLightsOff OFF else Create the scene MasterBathroomAllLightsOff with all of the switches as responders I edited this post after I looked more closely at your original post and belatedly noted that you had three separate lights in the bathroom, not three switches controlling a single bank of lights. If you create the scene with the switches as controllers, then you will turn all of the lights on with any switch, which may not be what you want. Jack

Hi all, Well, the new PLM has been in place for one complete day, and I can report that the system is up and running without issue during that entire time. I have pretty high confidence that the issue has finally been discovered and fixed, and that this will be the last post on this topic. (meanwhile keeping my fingers crossed just in case) Thanks to all who have read the topic and offered troubleshooting suggestions I have learned a lot. I will add a edit to the first post noting that the 'strange problem' was a result of a slow motion failure of an old PLM. Again, thanks to all, Jack

Thanks Paul -- will watch for it. Jack

Hi All Received my new PLM today, installed it, restored and everything went without a hitch. System is up and running with no apparent glitches. The test will be tomorrow, when the kitchen sink light should turn off. If anyone is interested, the PLM info is as follows: Firmware Rev. 9E Hardware Rev. 2.4 Manufacture date 2917 Thanks Jack

Thanks for the suggestions larryllix. I have tried many combinations of waits and scene mods, but always ended up with some failures. At several points it was a single device within a scene that wa not responding. For the motion sensors, I splurged and got the pro version, which allows turning off automatic writes to these devices. In my case, the main reason is I'd rather not dig my way through several feet of snow to put these things into linking mode. Hoping that the new motion sensors will not require physical intervention to allow this. (which rasies the question - when will version 5 firmware be ready?) Thanks Jack

Thanks oberkc. One of my first purchases (and installations) with this system was a passive phase coupler, along with a couple of RF range extenders. Up until now I haven't had any comm problems, and I have many devices installed on both legs of the electrical system. If there is a specific procedure to confirm communication between the legs other than this, I am unaware of it, and have not performed it. Issues with the system increased over the past several days, to the point where few of the programs worked, and few devices would operate remotely. Today I finally pulled out an extension cord and prepared to 'move' the PLM. The first observation I made was the the PLM was loose in the outlet, and I immediately thought that this could be the root of the problem. I proceeded anyway to plug the PLM into the extension cord, reset the system, and watched through the admin console as the system restored itself. There were many 'cannot communicate with device' messages, and only a few devices came up good. After several tires, I am now at the point that the only devices that are visible to the ISY are the few z-wave devices that I have. I have concluded that my PLM has failed, although I am puzzled that it lasted seven years, and seemed to fail gradually over a number of weeks, starting with minor, but consistent comm issues that occurred only when programs were run, progressing to a total failure. I was under the impression that these devices tended to fail catastrophically after a couple of years due to low quality capacitors used in the manufacture. I have ordered a replacement for the PLM, which should arrive in four or five days. We'll see if the issues continue with the new device. Again, thanks to all for your help with this problem. Jack

Hi Guys (and Gals if applicable) Back home from my holiday travels, and still struggling with system problems. While away, the system was erratic in a number of ways. Sometimes the Christmas lights didn't turn on .. as observed by my next door neighbour. Was able to turn them on with a struggle through Mobilinc. Status of devices in Mobilinc were (at random) sometimes correct, sometimes incorrect and frequently unknown. All in all, while I was away the system that was first set up in 2010 and has been running steadily ever since was a bit of a headache while I was away. When I returned, I did a hard reset, and things seemed to straighten out .... for a while. In the last few days issues re-appeared. Certain lights did not turn on, others did not turn off. One of my simple bathroom fan programs stopped working. Hard reset again about a half hour ago. Have yet to try the PLM move item. but will do that tomorrow. In the meantime, my frustration level has reached the point that I am researching Homeseer controllers. I also noticed that my problems bear some resemblance to what smokegrub is describing in 'The PLM Saga continues' topic Thoughts anyone? Thanks Jack

Merry Christmas guys. stusviews - yes a dedicated breaker - absolutely nothing on it except the PLM and the ISY power supply. Installed for that purpose when the basement was remodelled. oberkc - great suggestion - did not think of that at all! btw .. the light was off this morning. thanks Jack

Again, thanks for the feedback. I will be away over Christmas, so will not be doing any updates for a while. In the mean time, here is what has happened since my last update. 1) The worsening of the situation appears to have been the result of a Restore Devices and/or Restore Modem (PLM) procedure that did not complete cleanly. I upgraded my ISY to PRO, gathered in my outdoor motion sensors (had to fight my way through several feet of snow) and redid the procedures, all the time watching and ensuring that each and every device was restored properly. The next morning everything had executed normally with the exception of that pesky kitchen sink light. 2) Created a support ticket with UDI. Michel got back to me and suggested that I move the PLM to another outlet. Unfortunately easier said than done, as the PLM/ISY combo is mounted behind an access panel in my basement ceiling, connected to a dedicated outlet. setting up the necessary network connection and plugging the PLM into a convenient outlet will take some effort. Will attempt that after the holidays if the situation is still not resolved. 3) I added and additional program to turn off the kitchen light 20 or 30 minutes after the sunrise program. The next day the light was still on. (aaarghh) 4) Did nothing, and the next day, the light was off in the morning as it should have been. (yay!!! ... i think). Was totally puzzled by this until my wife informed me that the previous evening she had noticed that the light was on, but showing as off in mobilinc. She exercised the light several times through mobilinc several times and then left things alone. Now instead of being totally puzzled I am only completely puzzled. She claims she didn't want to disturb me as I was re-watching The Force Awakens in preparation for going to The Last Jedi with my son-in-law and the grandsons. Again, thanks for the suggestions. stusviews .. if the problem re-emerges I will absolutely go back to square one and start troubleshooting. oberkc .... I have soft-reset the ISY many times during this struggle, but so far I have not power cycled the system .. will do that in the new year. ScottAvery .. I actually did delete the device before the factory reset and added it back in after. It was also deleted and re-added when I changed it out for a new device. In both cases the behavior continued. Thanks for that note though. Merry Christmas everyone, and if there are any amazing spoilers for The Last Jedi - I don't want to hear about them. Thanks again, Jack

Thought I had identified and resolved the problem. Nope. Actually it is worse now. Multiple devices are not responding to program initiated scene changes, when that program is run on a time schedule. The devices show incorrect status in console, and when queried will show the correct status. When the programs are run manually, everything works fine. At this point, I am not sure what next steps to take. Any suggestions would be eagerly welcomed.

An update since the last tests. As I mentioned, I had changed the execution time for the standalone sink light program to 01:00. This worked perfectly. Since I was still awake, I changed the execution time to 07:00. The light was off when I got up this morning. Before going to bed, I browsed around the forums and found a note of advice to someone about upgrading firmware .. the firmware and UI versions must be identical. When I checked mine I found that I had firmware V4.6.2 and UI V4.5.2! This has since been rectified. Feeling a little stupid right now. The program has been returned to it's former version and we will see if this is solved tomorrow morning. Will provide an update tomorrow.

Thanks ScottAvery, I have modified the program to execute at 01:00, so that should test it away from other scene traffic tonight. I have, however, modified the program as it is several times, adding and removing waits and changing the location of the line in the program, all to no avail. The only success I have had is removing the line entirely from the Sunrise program, and placing it in the SleepTime program. That success, and forcing the program to run from elsewhere at other times, like executing the then from console or mobilinc, or setting the time for a minute or two beyond the current time and watching. In those circumstances it works every time. I am considering replacing the switch with a more up to date model, but I want to continue testing for a while to see if I can isolate the cause. At one point I did access the device directly, but it made no difference. I have taken to using scenes in recent years as a matter of convenience. If I change the device or add new devices to the scene I don't have to search down every occurrence and check it out. I am puzzled by this though. This program ran flawlessly for years. The only change that might be associated with the problem is that I recently updated my ISY firmware to the latest version. Unfortunately, I can't definitively say that the problem started with the update. Thanks Jack

Thanks stusviews and lilyoyo1, The incandescent light made no difference. Same thing this morning ... light on, console status off and normal program run status. Will try to change the program time to near bedtime, and observer what happens. Will put both of your suggestions in the queue Yes, troubleshooting can be exceedingly tedious. Jack

Thanks lilyoyo1. I have replaced the LED bulb with a 75 watt incandescent that we saved when we did the original replacement. Just to update everyone on the latest status, this morning the light was still on, with the switch pilot light off, the console incorrectly showed that the switch was off. The program showed that it executed at the appropriate time, and that the then portion of the program had executed. When queried, the console updated the status correctly, and I was able to control the light via the scene. The next step, after this test with the incandescent light will be to change time of the standalone program to an earlier time.

Since my last post I have tried a couple of things to see if I can resolve this issue .. again, without success. First - I removed the device from the scene, then deleted the device completely. I then re-added the device, and added it back into the scene. (as controller) This cured problems with the scene, which was then able to control the switch as normal. Left things alone, and the light switched on at dusk as normal, but did not switch off the next morning as it should have. The light was on, and the switch pilot light was off. In the console, the switch status was showing as off, and only showed the correct status when it was queried. Second: I replaced the switch with an identical model that I happened to have, after removing it from the scene and configuration. Added the new switch into the configuration and the scene. At the same time for test purposes I installed the original misbehaving switch into another location (the walk-in closet) that had not yet gotten an insteon switch, added it to the configuration, created a scene for it, and added it to my SleepTime program, which shuts the lights off at bedtime.. Then waited. The original misbehaving switch (in the closet) turned off as it should have, the replacement switch behaved identically to the original switch ... i.e it did not shut off in the morning yet showed off in console. Third: I removed the walk-in closet switch from programming, and moved the kitchen sink light switch out of the SunRise program and into the SleepTime program. It shut off exactly as it should have. (much to my wife's consternation, as she wants that light to remain on through the night, and shut off in the morning, particularly if we are away). Fourth: Removed the kitchen sink light from the SleepTime program, and created a separate program dedicated to turning off that light in the morning. That's where things stand at the moment. Waiting to see what happens tomorrow morning. The only thing that I can conclude for sure from all of this is that it was not a hardware issue as I suspected. I would greatly appreciate any thoughts and/or suggestions as to what could be the cause and resolution of this problem. Any Ideas as to what I can check in the various link tables, for example, and, is there any way I can easily wipe and reload the PLM. Thanks in advance, Jack

Hi all, And thanks for all of the feedback. Lots to think about. I'll try to answer the comments and suggestions in order. First, for kingwr, this sounds exactly like the problem I have. It started off as an intermittent, and became more consistent after I started to investigate. Now it is misbehaving regularly. For Scott, yours sounds like it could be similar in that I believe it is a hardware problem. Paul - unfortunately the 2876 does not have the advanced options, so I am unable to test that. Oberkc - Originally the switch would turn on via the sunset program but would not turn off at sunrise. Since the factory reset behavior is consistent - the scene will not turn the switch on or off, but the status in console changes when the scene is activated. I Don't know if I said this before, but the switch operates perfectly from the console when accessed via the ISY device entry. The load is a single 75 watt equivalent led floodlight mounted in a ceiling pot fixture, so say 12 or 13 watts. I removed the load by unscrewing the bulb and there was no change in behavior. Mike/kingwr/Paul - Interesting discussion . I am unfamiliar with the 'scene cleanup' procedure. This leads me to wonder where the scenes live. When I create a simple scene such as this one which has a single device which is both controller and responder where do the components of this scene reside - in the device, the PLM or the ISY and which one resides where? In Mikes line 3, how does the ISY determine the status of the devices in the scene, and the status of the scene itself when a button is pressed. lilyoyo1 - I'm with you and oberkc too, I don't think this is a programmatic problem. Two reasons: 1) this stuff worked for years with no issues and little or no change to the involved scenes 2) (news flash) While monitoring the device (not the scene) in console from a laptop i turned the switch on and off, and the device status did not change in the console display So now, I am still wondering where the problem is residing precisely. Is it the device itself (most likely in my mind), or in the PLM (still a possibility, but at the moment I don't know how to address this) In either case, my next step is to replace the switch. Thanks guys, will keep you posted. Will probably change the switch in a couple of days. (I love retirement - nothing is urgent) Jack