Geddy

First...where do you see that? I see their store site has "Ceiling Fan and Light Control Module", but not important. My on/off control works as expected in eisy (IoX 5.6.0). There has been a lot of discussion about keypads and fanlinc. Latest wiki seems to be updated from one more recent forum discussion: https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration This is how my KPL looks just for basic grouping: Did you happen to change anything with the "Button Grouping" option at the bottom of the keypad window? It opens up this window with the alert showing: Did you buy the device directly from Insteon or 3rd party? Either way, you might want to perform a factory reset to completely clear any device memory. It could be some onboard memory issue that needs to be cleared out to work correctly with IoX.

What are you resetting? Or do you mean just power cycles? Is it possible your Polisy jumped to a different IP address? Do you have IP Address reserved in your router? Sometimes people will bookmark the IP, but not reserve it in the router and it could jump randomly. So just confirm you're using the correct IP. (I like to suggest reviewing from the router side as most routers have a "connected device" list) I don't have Polisy so can't help with the process from going PG3 to PG3x, but did recently have an issue with all my node servers were "disconnected" today. I had to stop then start them and they worked fine. I also performed a "Restart Polyglot 3x" after 2 reconnected to force the others to restart and they did. In the process of migrating node servers each one needs to be restarted (per the wiki - https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_Node_Servers_to_PG3x) Cautions: Node servers currently installed on eisy will be removed (and possibly replaced). Node servers migrated are left in the "stopped" state. You will need to manually start each one after migration. If the Polisy was configured to manage node servers on more than one IoX (say both Polisy IoP and i994) only one IoX will be migrated and you can't choose which one it will migrate. Node servers installed on the Polisy from the local node server store will likely fail to install on the eisy. Node server licenses should be migrated as part of the Portal migration step. You might be at the point that a support ticket is the best option. Make sure if you are able to get back into PG3x again go to log and set it to debug and then "Restart Polyglot 3x". When you log back in download the log packages and include those with your support ticket. https://www.universal-devices.com/my-tickets/

Is your network hardware identical at both locations? You're using the same laptop at both locations, but is the network the same? That's probably the only difference/issue there could be. As you implied...all else being the same. My experience (and self rationalizing) is the IoX Finder window will "cache" the IP of last known local address (in the .state files mentioned in the wiki); when it doesn't find an existing entry "locally" it then (apparently) wipes everything out. Upon refreshing it will do a local poll and load any broadcasting IoX device on the local network. It's an issue I've experienced myself with a laptop when running IoX Launcher while remote it wipes out all entries because there's no local connection (I'm not running any devices elsewhere). I have my portal connection entered and that will usually remain, but even then I've seen that wiped out. Once you've connected to the other location once does it wipe out again when you next run IoX Launcher? I would expect the next time you run it the new local stored device should remain visible and open slightly quicker than the initial time.

When you try to set these options you might need to click the button to the left rather than "Write Changes" at the bottom of the window. If you are just changing the setting then pressing "write changes" it's a UI issue/bug/annoyance since the start of 5.x firmware (commented on here often) Make your changes then click the button on the left. See if that helps. Also, as @lilyoyo1 suggested, you might need to remove from IoX and re-link it. Not sure if a factory reset on the device would be necessary, but certainly removing from the current structure (if you added pre-i3 support was starting to be implemented) might help your situation. @keepersg additionally, it's also a "known issue" that the backlight value in admin console will always display as 0% when you restart admin console. (Try it for any legacy Insteon device.) Backlight acts funky when displayed in Admin Console. So don't expect that it will show you the true current setting.

@MBell while I’m sure @Javi will see your thread, the most efficient way to “report bugs” is through the support ticket process. This allows UDI to directly troubleshoot with your issue and get any logs or data directly from you. https://www.universal-devices.com/my-tickets/

Glad the file association fixed that issue...as to... This is more network related than anything else. Sometimes the finder will find it right away, but other times something just doesn't work right. I usually have to "refresh" and it will find it most of the time. Typically IoX Finder window will always find my eisy at the local IP address. I have to manually add the eisy.local address, but once it is in there it keeps it for quite a while. Since you added it does it return the next time that you run IoX Launcher and IoX Finder window opens? If not, and you are local it could be a network setting not allowing the device to announce itself or the computer just doesn't get a reply when it is searching for devices on the network. Make sure in Windows 10 that the network is a "private" network and the computer is findable (or however Microsoft states that on Private Networks). What device are you using? Since you mentioned using admin console on Win7 machine I assume you're connecting to an ISY994. That was more flaky depending on network router I used at the time. Polisy and eisy seem to have better connection history (for my own network at least). But now that you have added it the address should always show...at least until you clear the Java cache and run start.jnlp again (and note, that clearing Java cache doesn't reset that file association so you shouldn't have to go through that step again).

@JTsao I think a ticket is the best option to go at this point. Did you ever open a ticket from the attempted PG3->PG3x conversion you posted about? It's possible that it worked and you didn't see/notice it at the time and now it's impacting you because of the IoX update. https://www.universal-devices.com/my-tickets/

I think you should open a support ticket for this issue. Nobody else has reported this happening to Polisy during this update. The PG3 to PG3x upgrade on Polisy was an entirely different process. I would be shocked if UDI "forced" it as part of this IoX upgrade. Since there aren't others posting that this happened it's likely you unknowingly ran the update when you asked about it a few weeks ago even though you had an error from it. Did you ever submit a ticket then like @bpwwer suggested or did you just leave it as was at the time? https://www.universal-devices.com/my-tickets/

@johnmsch in addition to what @kzboray suggests above you might need to associate the .jnlp with Java. That can be done 2 ways (in Win10 and Win11). Right click on start.jnlp and select "properties". Then in the "Opens With" look for "javaws.exe" in the Java\jre1.8.0_361\bin directory. In the properties window it should look this way: Otherwise you can go to Windows Settings -> Apps -> Default Apps -> "Choose default app by file type". Then go down the list until you see .jnlp and make sure it's set to use "Java(TM) Web Launcher". My bet would be that you downloaded something other than the "regular" Java that you get when you visit java.com. You might have gone looking for other versions and seen some higher number versions, but those have specific use cases and not what IoX Launcher is designed to work with. Make sure you remove any Java other version you've installed before proceeding!

I'm not sure. Why not perform a factory reset like suggested for most other Insteon devices before installing just to be sure? Looks like the section of the cookbook is just a copy of this section in the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_(PLM)

@peterathans I don't expect that UD Mobile would lose geofence. I think I recall @Javi mentioning somewhere that Geofence was in production versions of the iOS app. I'm not sure on the Android side, but I'm sure it's there or will soon be there. I am not sure where you're picking up that Geofence was a beta version. I think it was just included in a beta release of iOS (and possibly Android) when it was first rolling out. That's normal for new abilities so those that are on the Beta builds get to test it out and feedback any issues experienced. But beyond that I think it was pushed to the production side fairly quickly. About a month ago @Javi commented that it was being pushed to the production store. So think you're safe in just relying on UD Mobile for geofence settings.

Congrats on the upgrade! Glad it went well. Indeed UD Mobile for remote access needs a portal subscription. But, it's the best deal you could ever ask for...It's $20 for TWO YEARS! (yes, less than $1/month!!!) (Even if you just do 1 year it's only $12!) And I see @Techman just replied...yes...if you just want to use the app while local you don't need a subscription. Personally I don't use apps all that much, but when I do it's 90%+ while away from home so the portal makes a lot of sense. Somebody in the last year or so had a similar issue of being the only one that knew what was going on. It's a little daunting to think about trying to document everything, but just hit the highlights. Make a document with links to UDI, UDI Forums, and to network items. That way if something happens to you somebody knows how to at least get support from the forums and/or start a support ticket with UDI to ask "how do I do xyz?". Have fun planning the growing options you have ahead of you!

@Vwas, You're currently on 4.9.0 (based on your earlier post). I would certainly say upgrade to 5.3.4 (do you have/use z-wave?) There were substantial updates in underlying ISY code from 4.x to 5.x and the only direct migration path to eisy is with 5.3.4. There is quite a bit of effort that might be needed (See @MrBill's post earlier) and review the release notes. It's not an urgent need to upgrade, but is necessary if you plan to migrate to eisy.

Thanks for the follow up on the ticket! Good to know it was a cache issue and maybe not certificate issue. Hopefully will begin working for others as the issue resolves.

@TUhl01 could be any number of issues. But essentially just means your device has lost connection to the ISY Portal. If this is happening a lot you should review any IoX and PG3/PG3x logs for any disconnects. If you don’t see any issues it could be a quick drop of your internet connection that other devices might not have noticed or shown any issue. Lots of alerts you should open a support ticket to see if UDI can help find the issue or describe if there are any issues in the logs they might have. I have received a few alerts, most were from times I know I issued a reboot command to the eisy or a local ISP issue because my router logged an outage.

This is what I'm talking about - show us the details of the customization window I don't have a "Default" listed in the notification Customization tab. (I made a temp one for image above) You either need to set a customization or you've made a default customization, but we don't know what it's supposed to say and why it's sending you what you received. Is this a new program? If so, then it was not setup correctly as @MrBill points out it should have "content" behind it. I made a test program to just send the "Default" as your program test-notify - If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'Geddy Email' Else - No Actions - (To add one, press 'Action') The email I received was simply: test-notify A Schedule was met at 2023/04/16 01:37:36 PM. ---------------------------------------- At: 2023/04/16 01:37:36 PM Program: test-notify Network: eisy And yes, "Copy to Clipboard" is just as quick as a screenshot, and saves a lot of time for more involved issues. For this one it's not as important, but if you ever need somebody to troubleshoot a program or suggest edits it's easier for the person helping to be able to copy/paste text from your existing program and suggest edits within the context of the program. So just good habits to form. Added plus is text programs become searchable in the forums; if somebody searches for ""Leak Sensor" and program" they wouldn't find your post because it is an image.

Also, looks like a similar issue to what you posted the other day in the Yolink forum area. There @Panda88 commented about the issue.

@landolfi moved your post to the IoX support area. Would you be able to post the text of your notification? Are you attempting to run any calculations in the program or notification? Also, for future reference the best method to post programs into the forums is by right clicking on the program and selecting "Copy to Clipboard" (last option in the menu) and then pasting as text in the message. This makes it easy to read and edit/update should something need to be altered (saves a lot of typing to by those trying to help!).

As with others having this problem I think the best bet is to open a support ticket with UDI. https://www.universal-devices.com/my-tickets/ It seems that there might be issues with users still running ISY994 on 4.x firmware. At least most of the issues reported recently seem to all be 4.x related.

It does eliminate the need for an adapter to go from RJ45 to DB9 to USB. Just the issue is you then need to alter the RJ45 to only use the wires needed on the PLM or you risk issues. I think it's been mentioned elsewhere that something could happen, but forget where. With the UDI kit you'll use the proper pinout for the RJ45 to DB9 adaptor. From there you then use the Serial to USB cable to connect to the eisy.

@Fredo yeah, that was the same problem I was having if I used the ISY Portal to connect to the device. I'm not sure why that's happening since I'm able to make variables through admin console when I connect through the portal. It must be an app issue talking to the device. Since you're on ISY994 then it's something app/portal related. My workaround for that was to change to a local IP connection and it worked right away. Try that, make your variable. Make sure admin console is closed while you're trying to make the variable. You can confirm the variable was made once you get it set in Mobilinc. Once you have it set (and if you wanted to confirm it in Admin Console) then change the connection type back to ISY Portal (just using my.isy.io as the URL and your portal credentials to login). I assume that you're using ISY Portal...but you might be on Moblinc Connect (or whatever that portal equivalent is called...change back to whatever you were using for remote access previously). Like I said, once I got the local connection it made the variable and has worked steadily since I made the new geofence area/variable. Hopefully it won't happen again, but if it does it just means I'll take a more serious look at UD Mobile and finally learn it a little more than I have. I just rarely ever open a mobile app to control my system that I've just stuck with what I had since it was setup the way I liked it.

@CNelson03 It's not rebooting (well, probably not anyway), but it's because UDI implemented a new alert process when the system loses connection to UD Portal. See this thread: https://forum.universal-devices.com/topic/40897-new-feature-ud-communications-system-notifications/ You can turn those UD generated notifications off in UD Mobile if you're not concerned about the connection to the portal. In UD Mobile on the Notifications screen click the gear icon on top right then scroll down to System Notifications and turn them off to the group/device you don't want them pushing the alert to. I also receive these every few days and find them unnecessary as I don't "rely" on portal connectivity so don't worry about it...especially when they were happening at 3am and 4am timeframe. You could create a program in IoX to send a notification (to UD Mobile or via email) when the IoX system reboots/restarts. That might be more meaningful for possible issues with the system.

"thing"? No. ISY as the "service", just as it always has been. It's just that the device ("thing") was named "ISY994". IoX still stands for "ISY on Anything". So as a service, YES, ISY lives on (anything)! https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#ISY_on_Anything_(IoX)

Also, the "PolisyISY" will always be there because that's a name you used for the device. You could just change it to Polisy or something unique and it would change to "<new_word> Dashboard". On the eisy it's changed by going to IoX Configuration (Polisy looks like the "ISYs" menu) then "Edit Current IoX" and change the name there.

@emses12 Welcome to the forums! First off you need to make sure firmware and UI match your current Firmware (5.3.0). (You DO NOT CURRENTLY MATCH!) Please clear java cache (be sure to select all three boxes in this process). Then download IoX Launcher (start.jnlp) from UDI site. For firmware please review this area of the forums: https://forum.universal-devices.com/forum/339-current-release-announcements/ Last version for ISY994 is 5.3.4. If you're already at 5.3.0 then you either don't have/use Z-Wave or have Z-wave 500 series board. The update from 5.3.0 to 5.3.4 should be fairly easy. Be sure you DO NOT unzip the file downloaded from the release post.