Illusion

Okay, I take it all back. I have lost nothing by making the big switch to IoP and the ISY Portal. I retract my request for Apple Widgets. I can do everything using Webhooks. It is incredible. Make an ISY Portal event in connections. Just like your are going to do an IFTTT integration: https://wiki.universal-devices.com/index.php?title=ISY_Portal_IFTTT_Integration#Setup_Instructions_-_ISY_Portal Then make a Siri Shortcut. You can sorta follow the IFTTT instructions here: https://help.ifttt.com/hc/en-us/articles/360053753113-Use-Siri-to-Run-IFTTT-Applets But you only need three of the steps: 1. URL (put in the web locator from ISY Portal) For your convenience, in your list of events in portal, there is a small icon beside the red X, which will give you the full URL you can cut & paste here 2. Get Contents of URL. Method 'Post'. Request Body 'JSON' 3. Name your Siri Shortcut. And now you can have this shortcut that directly activates an event in the ISY Portal. You can trigger it with Siri voice. You can trigger it with Apple Widgets on the Today View: And you can even just put one button on your home screen like I was wanting and trigger it with a touch: So far my experience is that an event takes place in under 3s. Really actually close to 1s. So happy.

@Javi Okay, Great. The IFTTT Today View widgets (Apple Widgets, not Favorites Widgets) work way faster than I thought they would so I am better off than I thought I would be. I am good without status. But if you do Apple Widgets, I think linking them to Favorites is great and so the setup of the Favorite determines what the Apple Widget does. But I would request that you support both legacy and modern Apple widgets. Legacy widgets can run just within the Today View. So a simple swipe to the today view can create an action without opening an app. In fact, the way Mobilinc had them linked to the portal, Mobilic did not even have to be in memory of the iOS device. Same with IFTTT. Widgets work even from a cold start, which is the whole point. I am not sure I understand the point of modern Apple Widgets. It is cool that they can be placed on any home screen page, not just the Today View, but interacting with them opens the connected app. I guess it does save one single keystroke from opening the app and hitting the button, but that seems like a lot of effort for 1s savings. But if there were a way to configure modern widgets to function without opening the app, that could be super cool. So now on any home screen we could have a button, or group of buttons that could execute some event. And the button could indicate a successful press. I think the way IFTTT Legacy Widget buttons work and display a successful press is pretty great. Right now the only hit to my system is that I cannot adjust the format of the widget like I could with Mobilic, but this is a minor hit.

I have moved to IoP and the loss of my Mobilinc Today Vview widgets is definitely the biggest loss. I have found a work around for everything else, including using IFTTT widgets. I think I could live with a widget that is a direct program run with no status display. That was always super slow with Mobilic Connect portal anyway and faster response would win over status display. Can always open the app if we need to see status.

I am unable to download a backup of my PG3. Settings>Polyglot Settings. There is the button there, and it darkens when my cursor goes over it, popup help appears on hover, ring highlights around it when clicked, but nothing happens. Attempted on multiple browsers.

@Geddy Thank you. Solved. I only have the one ISY online, but clearly it is still necessary to select that.

Solved. 2 things. Somehow when I moved the Polisy and rebooted it lost its reference to the ISY. I had to put the info back in there as it would not discover ISYs. And Somewhere in there I must have accidentally hit the HTTPS button or it switched to HTTPS on its own. After switching back to HTTP and deleting all polys, and rebooting, and starting over and installing new I could see it, but the WOL node would only wake up my LG TV if I use 192.168.1.255 as the IP address in configuration field. Using the IP address of the TV would not turn the TV on.

Somehow the ISY connection in the PG3 had moved to HTTPS. It was not always like that because I had a node server working for a bit. Not sure what happened there, or how. But all fixed now. Indeed there was all that TRY 1, TRY 2, TRY 3 in the log. It was a bit interesting, when I clicked over to HTTP, all my nodes in PG3 disappeared. When installed them back they were messed up. There was no configuration help panes in the PG3. Further, the message notification that "enter at least one station ID" and the one about "enter token" both showed up on your Wake On LAN poly, not on the WeatherFlow poly. That weirded me out enough that I deleted all and rebooted PG3. Then started fresh and it went perfectly smooth. @bpwwer A thought from a novice: I think the configuration help pane could be a touch more clear. I (like another user here on this forum though that the custom field that we have to add be "Station ID" and then the number of the station in value. Then when that did not work, I assumed that I needed to also add the station id in the key field and then either "remote" or "Local" in the value field. Now that I know exactly how you want the information in there your configuration help pane makes perfect sense. But coming at it as a lay person there are a lot there. Might I suggest an edit: [Station ID] [required]: At least one station id must be entered in the format of XXXXX in the Key feild (where XXXXX is the station ID of your Device and the Value field is either remote or local. Then in the example, I would also change the numbers to obvious nothings, because the numbers you are using look like they could be some kind or real port number or something to us idiots. I would also increase it to 5 digits, because I really did think the values meant something because they were a different number of digits... click "Add Custom Parameter" key = 4968 12345 value = local key = 1398 67890 value = remote Configures the devices associated with station ID 12345 to get data from hub UDP feed on the local network. Devices associated with station ID 67890 are configured to get data from the WeatherFlow server at shortPoll intervals. On a separate note: I was fine with PG2 nodes. A big factor in me switching to PG3 was so I could purchase the node I am using the most and that is this. Thank you for taking the time to make it and I am happy I could be a customer instead of just a freeloader.

@roblombardoClearly not! But I cannot figure what is wrong. What configuration in the ISY admin console? Maybe that is what I am missing. Double checked my email address and password. If I hit sync it will start, but then looses connection before the sync can finish.

@kzboray Still battling but your post makes me ask a question. If WOL is broadcast, why do we need to enter a specific IP address? My TV is on a DHCP reservation at 192.168.1.4. The Polisy was at a reservation of 192.168.1.12 before I powered it down to move it and it came back up at that as expected. But in the WOL node server configuration, would not any address on the subnet result in the same? So if I put the info into the field as 11:22:33:44:55:66/192.168.1.4 or 11:22:33:44:55:66/192.168.1.255 the WOL command would go out the same?

@roblombardo So Mobilinc is working for you on the ISY Portal? I have all the settings in there but Mobilinc Pro will not sync and just keeps saying disconnected, attempting to reconnect.

@Bumbershoot ISY has a check mark next to it in the Polisy (PG3). Not sure what your reference to IPv6 is. It is on my local network with a regular IPv4 address and a MAC/UUID referenced. @Geddy Thanks for all the info. I did read everything referenced before posting here. The ISY in the pics in IoP that I am trying to move to. My 994 is in a drawer at this point, but may come back out if I cannot get the WOL node server to work. That is a deal breaker for me as powering on my LG TV is a mission critical item. PG2 does not point to anything. I have never started up PG2 on this new Polisy Hard Drive I installed. Those node servers were set up on PG2 that is on a hard drive in a drawer. If I have to access that to delete them, they are going to stay right where they are. But maybe I can delete them using PG2 on this Polisy. But that is a battle for another day. @bpwwer Oh great. So that clean up will be easy. Thanks. I did have a major issue with a IP address change while trying to get this set up, but now I set up a DHCP reservation. Maybe I will try the 127.0.0.1, but confidence is low because I know the ip is correct and locked in now... EDIT: Wait, the ISY is supposed to be HTTP, not HTTPS, right?

Working to move to IoP and struggling on multiple levels. Working on the node servers now. Purchased WeatherFlow for PG3, got it installed and I believe set up. The node server is populated with lots of data that looks correct and up to date, but it does not show up in my ISY: Those three node servers are from PG2 that is gone for me. I am not savy enough to flash my hard drive so I ordered a new one and am just going to start fresh from PG3. But I did try to restore from my PG2 backup file hoping the node servers would just transfer over. They did not. So now I have these dead servers that I hope go away once I clean everything up in the ISY. Maybe I can delete them from the admin console and they will go away because I do not have a delete option from the PG3 interface. I was working extensively on the WOL node server but could not get it to work, and the last time I deleted it and reinstalled it, it would not show up in the ISY either. So I moved on to purchasing the WeatherFlow. And now it does not show up in the ISY either. I am at a loss and begining to think I am doing something very wrong.

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