Illusion

@roblombardo, I am right there with you. The answer is that IoP does not support Mobilinc Connect. MrBill, I wanted to still keep Mobilinc with the ISY Portal and I put all the info in from your other post (which I also found in the wiki and my Mobilic cannot see my ISY... Any thoughts?Cannot sync, cannot connect. I am at a loss

Okay, I got my LG TV to respond to WOL from my ISY on Polisy. Worked great. Put in programs. Worked great. Moved and rebooted Polisy (and IoP) and now nothing. Read other thread talking about going through switches, which it is now, but took long Ethernet cable and got both on same switch. Still nothing. Also, related? If I add a second custom configuration, the node server still only shows 1 node. And only that first one shows up in the ISY. And nothing I do seems to edit that node. In fact, I put in the wrong IP the first go around and ended up having to delete the WOL Node Server and re-install to get the 1 WOL node working... for a while ... I am not network savy and am a bit lost here. But this is a deal breaker for me to move to the IoP. If I cannot get this to work, I will have to move back to the ISY994 where Wake On Lan still works...

Okay, so I got it to show up. For some reason my PG3 stopped pointing at my ISY. And search for ISY failed. Manually putting in the ISY details worked. But now I have other issues that I think I will reach out to the creator on... Right now I am just working with this one poly and will add in all the others when I can wrap my head around why such a simple one is giving me so much trouble. I am like 5 hours in on this one now. Thanks for moving and setting up a thread for me. I should have done that but was so overwhelmed....

Thanks so much. I have found that, installed it, but I cannot seem to get the node I set up to show up in the ISY.

I also miss WOL. It was the only way to turn on my LG TV from the ISY

Hey Techman, I am on Mojave 10.14.6 and am also having trouble after upgrading to 5.3.4. I get a launcher icon, but it says that version is not compatible with 10.14. Using your link from above will get me a start.jnlp icon on my desktop that will launch the ISY launcher, but then I have to choose to download the admin console from the LAN or Cloud. Both work, and I end up with a working Admin console, but it takes a long time and I do not get a 'program' that I can have in my dock like I could with 5.3.0 From the post: it says 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp Note: If you have version 5.0.8 or lower installed on your ISY, then use this link instead: - http://isy.universal-devices.com/994i/5.3.4/admin.jnlp Note: MAC 10.6.x users must use the following links instead - http://isy.universal-devices.com/994i/5.3.4/admin16.jnlp (Admin Console) Using the http://isy.universal-devices.com/994i/5.3.4/admin.jnlp link I get a admin.jnlp icon that I can put in my dock as a document, by the trash, but not something that can hang out in program area of the dock like I used to be able to. Same if I use the http://isy.universal-devices.com/994i/5.3.4/admin16.jnlp link. I can make this work and live with it, but is there another option to have it like it used to be? Is there a benefit to using http://isy.universal-devices.com/994i/5.3.4/admin.jnlp vs http://isy.universal-devices.com/994i/5.3.4/admin16.jnlp I can detect no difference in launch/use.

Update: The tamper stickers were put on there by the eBay seller, not Smarthome. I guess he has had some bad actors in the past.

I came here to the forum after scoring a couple of unused 2423A5 Synchrolinc modules on eBay. But neither module worked. But they looked like they had never been used. I found a couple of threads dealing with an issue similar to mine: In both cases there was talk of the dreaded bad capacitors. But in both cases the link tables were bad for the devices, just as in my case for both new modules. I think we may have a bug setting up these devices in the ISY firmware. Both my new modules end up being added with bad link databases regardless of factory reset, add method, restore, query Insteon engine or anything else. But both modules work flawlessly when linked directly to another device outside of the ISY even if they are still in the ISY. But building a scene in the ISY with a module and one of them as the controller fails. They seem to take trigger level settings from the options button in the ISY without fail. I pulled one of my older back-up SynchroLincs out of storage and noticed that it is stickered as V1.1 while these two new guys are stickered as V1.15, but both will get added to the ISY as the same v.30. The two newish modules also have 3 tamper stickers on them, where the old guard does not. The old guy out of storage adds and works like butter, but nothing I do can get the new guys to link to the ISY in a way where the status changes will update without a query (which always returns the correct load state).

Makes no difference how they are added. Link table is bad. But both units will control a device set up outside of the ISY!

I have tried both Start Linking and New Device, (but I used auto discover). I will try again using manual device selection, but I think there is a communication bug here... These two synchrolincs show as the same item number as all my older ones, but the hardware version sticker shows V1.15 to my older ones at V1.1 The just purchased ones also have three tamper seals on them whereas my older ones have no such. Because a query always shows the correct status, I created a scene with a device and the Synchrolinc as controller. No good. But then I created a link between them directly outside of the ISY and BOOM, the Synchrolinc controls the device without fail. But the link table is a disaster.

I just picked up 2 Synchrolincs on eBay and both of them get added to the ISY with that same bad database. No amount of factory resetting, removing, re-adding, restoring, linking by address or by button press results in any benefit. Synchrolinc seems to work, take adjustments to its trigger settings, but without a correct database will not report status changes...

All fixed. New KPL arrived. Pigtailed it and added it as a new device and played around a good bit. Thought the group might be interested to know that it made no difference whether that main button was set as Toggle, Non Toggle On, or Non Toggle Off, it functioned the same in the ISY regardless. On turned it on, off turned it off. Other sub buttons worked as expected with toggle settings change. Ran an event viewer on it, and it did not have the second command set seen in the problem KPL. Solution was simply to remove the main button from the scene it was controlling, and add it back. I have never had a scene cause such behavior before. Sorry I did not think of it as a solution earlier. But way way easier than deleting and adding back new (again 125 links and lots of programs). But it does seem from this that the remove and start fresh would have indeed worked. Thanks all for the feedback.

@stillwater Interesting idea to reset and restore the PLM. On the list of options now. @Techman "Buttons Toggle Mode" setting makes no difference. Only setting it to Non Toggle OFF makes a difference in operation. With it set to Non Toggle Off, pressing the on button sets the status as off in the ISY without the weird on status for a flash. Non Toggle On, and Toggle both result in flash of on status, and then off status. I do not know how I finally got it to stop turning the scene off so I am holding off making any more changes as it actually accomplishes the desired function of turning on the load in the scene. I have ordered another 6 button KPL and when it gets here I plan on additional experimentation where I can add as a new device.

Techman. Hardware version is 8.1. Not sure about date code. Not an issue with hot or neutral connection. Keypad put on a pig tail (table top enclosure) and moved locations and voltage tested before coming to the forum. Stillwater. That is interesting. This KPL has 125 links and is in dozens of programs so not super anxious to start over with it, especially now that I have it turning on the scene like it should. But if I cannot let this go, I may experiment with that. lilyoyo1. Not location specific. KPL in table top enclosure and moved around...

Oh Yes! I have done multiple factory resets. I have been working on this for 6 hours today. Been doing Insteon since the beginning. I have never seen anything like this. I am at a total loss.

Oh sorry! I meant to put that in the original post. I stopped all programs from running and it still happens. I did a compare links and all are a match.

Edited with new findings Background: I had a 6 button KPL (very old, first gen) fail the other day. I did lots of factory reseting and stuff and thought I had brought it back to life. But I would hit the top big on button and a few seconds later it would be off. Looking at the event viewer there was a fade down event after every time I hit the on button and the switch would fade itself off. Okay, never seen that before, but old switch. I yank that and put a new one in its place. Disregard above. After extensive testing, I have determined that that old KPL is just wonky. Weird flashing lights after reset. Refuses to respond to key presses now. This one I turn on and its indicator leds stay in the on position, but the ISY shows it as off instantly after I hit the button on. It shows it go on for a split second, then it shows status as off. (no load connected, just using as a controller). It was also turning off the load that is in the scene with the main button as the controller. After lots of reset and restore work, playing with the toggle/non toggle settings, and updating the scene control type of the responder, I finally got the load to stay on, but the status of the KPL shows as off in the ISY. Now I begin to wonder if something similar was going on with the one I pulled out. I grabbed an event viewer of me turning on the switch and there is too much there that I do not understand and I am hoping someone can look at that and offer a suggestion: This is what happens as a result of me pressing the top on button: Sun 02/13/2022 11:17:17 AM : [INST-SRX ] 02 50 56.CF.CE 00.00.01 CF 11 00 LTONRR (00) Sun 02/13/2022 11:17:18 AM : [Std-Group ] 56.CF.CE-->Group=1, Max Hops=3, Hops Left=3 Sun 02/13/2022 11:17:18 AM : [D2D EVENT ] Event [56 CF CE 1] [DON] [0] uom=0 prec=-1 Sun 02/13/2022 11:17:18 AM : [ 56 CF CE 1] DON 0 Sun 02/13/2022 11:17:18 AM : [D2D-CMP 01C5] CTL [56 CF CE 1] [DON] op=is --> true Sun 02/13/2022 11:17:18 AM : [D2D EVENT ] Event [56 CF CE 1] [ST] [255] uom=100 prec=0 Sun 02/13/2022 11:17:18 AM : [ 56 CF CE 1] ST 255 (uom=100 prec=0) Sun 02/13/2022 11:17:18 AM : [INST-SRX ] 02 50 56.CF.CE 00.01.01 CF 11 01 LTONRR (01) Sun 02/13/2022 11:17:18 AM : [Std-Group ] 56.CF.CE-->Group=1, Max Hops=3, Hops Left=3 Sun 02/13/2022 11:17:18 AM : [INST-SRX ] 02 50 56.CF.CE 51.12.25 40 11 01 LTONRR (01) Sun 02/13/2022 11:17:18 AM : [Std-Cleanup ] 56.CF.CE-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Sun 02/13/2022 11:17:18 AM : [INST-DUP ] Previous message ignored. Sun 02/13/2022 11:17:18 AM : [D2D EVENT ] Event [56 CF CE 1] [DON] [1] uom=0 prec=-1 Sun 02/13/2022 11:17:18 AM : [ 56 CF CE 1] DON 1 Sun 02/13/2022 11:17:18 AM : [D2D-CMP 01C5] CTL [56 CF CE 1] [DON] op=is --> true Sun 02/13/2022 11:17:18 AM : [D2D EVENT ] Event [56 CF CE 1] [ST] [1] uom=100 prec=0 Sun 02/13/2022 11:17:19 AM : [ 56 CF CE 1] ST 1 (uom=100 prec=0) Sun 02/13/2022 11:17:19 AM : [INST-SRX ] 02 50 56.CF.CE 11.01.01 CF 06 00 (00) Sun 02/13/2022 11:17:19 AM : [Std-Group ] 56.CF.CE-->11.01.01, Max Hops=3, Hops Left=3 Sun 02/13/2022 11:17:19 AM : [INST-INFO ] Previous message ignored. Sun 02/13/2022 11:17:19 AM : [INST-SRX ] 02 50 56.CF.CE 11.01.01 C3 06 00 (00) Sun 02/13/2022 11:17:19 AM : [Std-Group ] 56.CF.CE-->11.01.01, Max Hops=3, Hops Left=0 Sun 02/13/2022 11:17:19 AM : [INST-INFO ] Previous message ignored. There appears to be a second command from the switch in the event viewer from a single key press. Also, while the ISY shows the KPL main button as off, the switch LEDs are showing it is still on, and indeed if I query it the ISY will update the status to on. Another press on will again cause it to show off in the ISY status.

Please see: Just those two posts in that thread should answer your questions. 5m of reading or less.

@shannong I do not want to get into a flame war with you, but in my experience UDI staff respond to posts of all types in the forums more than any other company I have ever experienced. Nearly every other community/user forum I have ever participated in has almost no official responses to user posts. Often, it seems, these companies leave it up to volunteer moderators to be the de-facto face of their company on the community forums that they host. I agree that as UDI has gotten bigger, and a vastly greater portion of their income has moved to large contracts vs individual users, their employee engagement with the user forum that they maintain has decreased from the good old days. But this reality is contrasted by their greatly increased individual customer ticket support system. Even as they have gotten larger, their customer support, both on the forum and through their support ticket system, is unmatched by any other company that I have ever engaged with.

@shannong Please see this tread to answer you more detailed upgrade questions:

I am having trouble now updating my last 2440. I replaced a switch and needed to write updates to the 2440. I put new batteries in it and put it far away from the PLM (as I also have one of the PLMs that will not talk to it) and I cannot succeed in the write updates. I have done this a dozen times using this distant programming method without fail, but now I cannot make it work. This is the first time I have tried since moving to the 5.x branch and I wonder if it is related? Followup: After a painful factory reset of the 2440 and a full restore using the far away trick, I am back in operation. I guess the 2440 had a glitch that required a wipe to allow comms to resume.

I can confirm that I as well have never been able to get to my Polisy on an iOS device. Using Safari or Firefox both yield the Polisy page with the "not connected to server.." banner.

Fixed now. Maybe it was the browser cache?

Absolutely.

I updated from 5.1.0 to 5.3.0. But my polisy shows my ISY is still on 5.1.0. I restarted the polisy, but it still shows ISY at 5.1.0? ISY Shows running 5.3.0...