MrBill

I spent about an hour today downloading everything that google found with this search "site:cache.insteon.com" these were the most interesting group of files:

for the fastest assistance you might just open a ticket for this: support@universal-devices.com In some cases the answer may be to delete the file, in others it may be to reload the firmware manually.

You may also be able to enable two node operation via the options button in the admin console. If that works you'll have a "closed" node which has reverse logic. I don't have any with the 2843 model number all mine seem to be 2421

As mentioned by @Javi credentials are reset to admin/admin during that v4 to v5 upgrade. To further comment on the remeainder of your post Mobil Connect and the UDI portal are two competing portals and only one can be used at a time with the hardware. Stick with the UD portal at my.isy.io for compatibility with both the UD portal AND mobilinc Pro.

Lets contain this conversation to the already running threads in the Smarthome section of the forum. Thanks!

Cellular gateways typically don't have routable external IPs. They use a technology called "Carrier NAT". If you have a local network beneath the gateway you should still be able to access your ISY on the local LAN. You can subscribe to the portal to get access remotely, but you will need LOCAL ISY access to get that set up.

I wanted one of those once... never coughed up the cash tho

I haven't used it but somehow the PyInsteon project works with "This is a Python package to interface with an Insteon Modem. It has been tested to work with most USB or RS-232 serial based devices such as the 2413U, 2412S, 2448A7 and Hub models 2242 and 2245." (source) I believe the Home Assistant Insteon integration uses that code.

there is the ability to run a program at startup. Which could possibly be used to query... I'm not familiar with the ZEN17 tho to know if it responds to queries. 'Run At Startup' can be enabled from the Program Summary tab. If you leave the IF of the program blank it will run the THEN block at startup if Run at Startup is enabled for the program.

It's been happening slowly for a long time. There are MANY threads debating the topic on this forum. It just became apparent yesterday to a lot of users because the cloud server went offline.

As long as you have a PLM (Insteon 2213s) you can set your ISY up fine without any subscriptions needed. the portal subscription is less than a buck a month and is the recommended method for remote access. (you can however open ports and use the old fashioned and UNSECURE method if you really want to)

I agree the written upgrade instructions are hard to follow and contain something that are outdated. Actually you wanted copy to clipboard. Not sure why it didn't work. One problem I have helping people along is that I have no idea how things work on a Mac. Last time I replaced my laptop i was going to go the Mac route (already in the apple ecosystem for phone and tablet) but in the end just couldn't justify the additional $$ Agree.

I'm surprised smarthome.com is still up at this point. I've wondered for awhile if the nokia stuff would reappear once the insteon name is done being trashed.

Don't use the enable internet access option on the admin console menu. Instead your best bet is to subscribe to the ISY portal. It's less than a buck a month, and you can use it with mobilinc pro or the UD Mobile App. If you insist you can open a port, but I don't think the "Enable Internet Access" option works with UPnP anymore. UPnP kinda became unfavored in general a number of years ago.

I started a 2245 cloud server shut down thread in the Smarthome section... lets try to keep all 2245 cloud shut down discussion there.

Smarhome appears to have shut off their cloud servers which operate 2245 Hubs. It appears there is a path for you to migrate to home assistant using that hub. DO NOT FACTORY RESET IT. I have very little information on this other than a user on reddit is reporting success. EDIT: Here is a better link than the one belowthe link I posted yesterday. Please Keep all 2245 Server shutdown discussion in this thread.

I think we need to put it all into the smarthome section because it's going to keep coming no matter what we do.... It appears 2245 hub users can migrate to Home Assistant using that hub, but I haven't done it yet.

I'm going to add here... for anyone using a 2245 Insteon HUB that hasn't yet factory reset it... DO NOT FACTORY RESET IT. There's a reddit thread that indicates users can migrate to Home Assistant. I don't know alot about it yet, but I will... my son's house is effected. I order an rPi this morning to try what's been suggested.

Since this thread is uneeded I'm going to ask @Geddy to close it.... Before it becomes a secondary insteon shut down thread... we already have enough of those discussions.

If you're unwilling to check Level 3 Event Log then I wish you luck, you know best!

This seems very much like Noise on the powerline delaying Insteon signals. https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting Open the Event Viewer and set the dropdown to level 3 and capture what's happening there. It's more detailed with transmission attempts than the log.

Try using the backup option first. File --> backup ISY. If you can successfully get your backup file there, then you can say no to the backup question under Manually Upgrade. Use version 5.3.4 since you don't appear to have z-wave. A few more helpful tips: 1) make a text back up of your programs. If a program uses "adjust scene" it will need manual help after the upgrade. To make a text backup of your programs, click the top folder on the programs tab (usually named "My Programs") and then right click it, choose "copy Folder to Clipboard" then paste the clipboard into any old text editor that won't try to add formatting and save it. If you need to reference it later you can. 2) after the upgrade make your first stop in the admin console Help --> About. Verify you have the same versions for Firmware and UI 3) second stop in the admin console Programs --> Summary look for the color Yellow in the ACTIVITY and STATUS columns. If you find any it's like that either the program contained "adjust scene" and needs manual help to put it back the way it was, or you failed to check#2 above.

Both. The settings for the root of the scene is what happens when the ISY (and anything that uses the ISY as a controller such as Alexa). The settings for the controller are what happens when the controller button is pressed. Let's use a different example to understand. imagine a kitchen light, 2 switches one at each end of the kitchen. Both of those switches would be scene controllers. You might also program Alexa via the ISY. The kitchen light could be programed to turn on full from one controller, turn on to 50% from the other controller, and turn on to 10% if the ISY/Alexa turned the scene on. It's really very powerful... you can set the scene up differently for each controller.

There's several features in *some* insteon devices that aren't implemented by the ISY... another is the ability to detach the load on 6/8 button keypads. The problem is at some point in the game Insteon changed it's mind and went from trying to be an open platform, to one that wanted to be secretive.... Many devices UDI had to reverse engineer to support them at all. In some cases they may not have known the feature existed, or they may have choosen to ignore it because they didn't have enough data to be sure their implementation would always work.

Yes that will work fine. If you don't have node servers you could use a Wifi bulb with a Network Resource to turn it on, and another to turn it off. The network Resource examples in the wiki only include examples for Phillips Hue which, while i love my Hue bulbs, is probably overkill for your needs. That said it shouldn't be too difficult to work out a wifi bulbs Network resource needs. @larryllix might have thoughts....