Geddy

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

@Eric It's a personal call as to what you WANT to upgrade to. Just take your time to explore the options and what you're comfortable in undertaking to migrate. I would probably lean more toward migrating with the existing (working) PLM. Then when you're able to buy a USB PLM have it available as a spare/backup should the existing PLM fail. The new eisy uses a PLM with USB connection. not sure what "IP connection" you're mentioning. I migrated from ISY994 with existing serial PLM using the Serial DB9 cable that came with the PLM that I still had and added the USB/Serial cable so the process was fairly simple for my system. If you don't have the serial cable you have to add the DB9 adaptor and can buy the kit that UDI sells to make the cable needed to go from existing PLM to eisy. Although the process does give you the option to replace PLM during the migration steps if you purchased a new USB PLM to go with the new eisy. And @MrBill replied during my reply saying about the same.

HA! Doubtful, but probably just one trying something like this recently. Yeah, not a GH user so can't help further. Just knew of the Alexa discussion from attempting to use something in that process a few years ago. Sorry, misunderstood the original problem/goal. I thought you wanted a light to come on in the closet not outside of the closet. Is there not a switch close by to just flip on when opening the closet door? Good luck with your endeavors. 👍

Found this online: http://cache.insteon.com/pdf/2457D2.pdf Page 18 & 19 reference "Local Programming" that I thought might be possible if it isn't an option within the IoX system.

@xlurkr Not sure how/if it can be done with Google Home, but know ages ago it was said to work with Alexa (as far as triggering a routine). What ISY device are you using (ISY994, Polisy, or eisy)? Could you add Z-Wave controller to your ISY and just control something that way? Maybe it's the SmartRent that's somehow blocking you. -- see edit below! Otherwise, maybe try some just straight up motion sensor bulbs. I know Govee used to have some, but what I got in the past isn't available now. They are indoor/outdoor and some do dusk to dawn and on with motion...if it's in a closet (and mostly at night) it should allow the light to turn on when the door is opened and should stay on at least a little while. https://www.amazon.com/Motion-Sensor-Built-Equivalent-Bright/dp/B07F6HBLXC - similar to what I got for outside in the past. (Sadly, those motion sensors don't last long in Georgia heat & humidity) Or something like this that's used for under cabinet lighting, but also could be used in a closet setting: https://www.amazon.com/Lighting-Wireless-Rechargeable-Operated-Wardrobe/dp/B085PY9VYV/ (Use 3M command "tape" so not to leave any marks or permanent tape in the closet) Edit: Reviewing some of the old post linked above and subsequent links found this post: (sure, it's from 2018, but didn't seem likely then...wonder if it's been made possible since)

link in prior post takes you to the "Current Release" area of the forums. This is the list of all current releases. Looks like 5.5.9 is current release for IoX (eisy/Polisy).

@Glynr What is the firmware on the eisy? That should be brought up to current release for IoX to have a successful migration. There were some issues in earlier versions of IoX that created problems when migrating. Are you migrating any Z-Wave devices? Be sure that you've followed the migration steps as necessary to your devices: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994

@Wes Westhaver There should be an option to turn the LED off. I don't have any of these modules so can't confirm. What settings are available when you click on the device? Is there a Backlight, Status, or LED brightness setting at all? What Firmware are you on? (This is posted in the ISY994 area). If you're on ISY994 FW 5.x you might have to press the button labeled for the setting for it to "take". That's a UI issue that was introduced in 5.x updates. On this one I'd have to click on "Backlight" to get that value to set. The above is for an outlet I have so your options for the plugin dimmer might be different. Otherwise, look up Light Dims as an option (for this and other LEDs in the room). There appeared to be a way to dim the light with local programming (Google the user manual for it), but not sure how that's done and it's not advised if being controlled by a controller so makes it seem that a controller would be able to turn the status light off (at least dim it some).

@Fredo Check the actual Geofence Location is still defined in "Location Settings" on Mobilinc. If it is then make sure the variable is still the same as you have indicated above. I recently had a similar issue and either the location or the variable had been deleted from the app. I'm not sure if it was iOS related (I recently updated to 16.4.1) or something else, but I noticed some programs not triggering for a while. I'm running IoX on eisy, but it was clearly app related as something was missing. I think I had to recreate the location and reset my variable. I then had to adjust my programs to reference the new variable. Since I'm on IoX I had some issues with Mobilinc making the variable through the ISY Portal connection, but I made a local connection and it worked right away. I since changed back to ISY Portal connection method and my geofence and programs trigger correctly. While not an issue for this situation you should consider updating the ISY994 to the last release of 5.3.4. There weren't many fixes from 5.3.3 to 5.3.4, but with support ending for the ISY994 you should at least be at the current Firmware so any forum support you get will be on the "most recent" build. I echo @Javi and @DennisC comments of trying UD Mobile. You can use Geofence to call on programs to change the variable as you cross the boundary. There's a learning curve setting up the new app, but it is very customizable to fit the various needs of users. It's also being currently developed and supported by UDI, unlike Mobilinc (that hasn't been updated in several years).

@PB11 split your post out from a solved topic as you're asking about "Unmanaged" node servers. What hardware are you using? My guess would be Polisy. I believe if they are showing unmanaged they were managed by PG2 and you're logging into PG3. You either need to go back to PG2 and remove from there then install in PG3 side. Otherwise, you should be able to remove them from the IoX Admin Console and the Polyglot should update. I think @bpwwer can confirm that's an option. As for the update issue review the release notes for 3.1.19. If you've attempted the normal reboot process then try from the admin console configuration tab to force a Polisy reboot. Last ditch effort would be a full power cycle (pull the power supply). Make sure you're allowing ample time for the updates and with the Polisy getting expected beeps when you reboot it.

@giomania the eisy should auto detect the IoX service since it's on the same machine. It should be using the IP 127.0.0.1. What are the settings for your ISY when you review using the eisy PG3x dashboard? ISYs -> Edit Current ISY Note that with PG3x you should not need to setup the ISY when it is the IoX service running on the same eisy. If you have altered those settings that might be your issue. What device is at 10.10.2.20 and what is using that port? Is that something for the eisy/IoX? What are you setting a static IP on? That option has been removed from eisy because of the number of support tickets networking issues created on the ISY994. Another issue might arise if you have multiple VLAN and don't have cross traffic allowed.

Bummer. Thought it might have worked. I don't know how long it has been since the skill has been updated, but it clearly says it supports LOCKS. I'm not sure if that's the Insteon equipment you're using or z-wave locks that others use. I agree that maybe a support ticket might be best way to get attention to this. But @bmercier does check the forums now and then and might have some insight to this issue.

When you're on the ISY Portal site (my.isy.io) and on the Alexa Echo settings how are the locks added? What category do they show? You might want to select "Device with Open/Close" syntax. My thought is they're just showing as "Light" You could then make a routine to "lock" or "unlock" to control them. After you change the category on the ISY Portal you need to remove the device from Alexa and re-discover. (Sometimes easier from alexa.amazon.com, but that site isn't as helpful as it used to be.)

I don't have a Polisy to try it on, but from the comment above it seemed just put that URL in a browser and apparently there were processes to run and it would just result in having the system updated to PG3x. Nothing has been added to the wiki as far as processes so think it's just use that URL. @bpwwer do you know of anything else needed to upgrade from PG3 to PG3x on the Polisy? Important comment above though: make backups of everything before attempting to migrate PG3 -> PG3x. (I might include a suggestion to take screen shots of ALL configuration pages for node servers you are running before the migration. Couldn't hurt just for visual reference if they need to be setup again.)

I think the "differences" really only impact Node Server developers. @bpwwer would be the best to answer if there's anything impacting us, as users, between the two. But, it's probably not anything that would make one better/different than the other on the user side. It's more developer based from everything that's been posted previously. Without getting into the weeds (mostly because I don't know what the stuff means) I'll just leave it at that. But on the surface (for users) as best as I see it (currently) PG3 = PG3x PG3 runs on Polisy - able to update/upgrade to PG3x on Polisy (not a reversible update) PG3x runs on eisy natively (just like @MrBill said in the first reply) Current node server store for PG3 and PG3x are exactly the same.

When you say you "installed admin console" from my.isy.io what did you do? Or do you mean that you just added the admin console URL to your ISY Finder window? Make sure you got the "Admin Console URL" link and not just the "URL to ISY" link. The Admin Console link needs to have "desc" at the end of it. (It appears that it did in one of your shots) I'm not sure if it makes a difference, but are you using the start.jnlp that's downloaded from the wiki (via direct link to UDI's site)? Are you local to your ISY or attempting this while remote? I know I ran into an issue a few months ago, but it was a glitch with UDI's site at the time I was attempting to connect while remote. It resolved itself once their site/portal was stable again. If you log into ISY Portal does it show the ISY994 online? (since you posted in ISY994 area I'm assuming this is indeed ISY994 equipment.) Try not double clicking on the URL and single click and see if you get an option for "Admin Console (Cloud)". Lastly, what Firmware are you running?

Like this: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy or https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy Now that you've got it working it might not be a "fair" test, but clear your Java again (selecting all 3 options). Then run start.jnlp to put the icon back on the desktop and run IoX Launcher. If it doesn't "Find" the IoX what happens if you hit "Refresh"? Usually devices aren't randomly hopping IPs unless the router reboots or multiple devices come online at nearly the same time as you rebooted the Polisy. If something randomly took the IP during a reboot of the Polisy you might have other network issues. Either way, glad you got it sorted out easily.

Probably not moving away from Java anytime soon. Problems are usually all that get reported/posted about. Don't see people posting when stuff works as designed. Yes, I believe there is hope that UD Mobile would be available on computers (it's already able to run on macOS (though think only M1 and better, but might recall somebody saying they got it on an Intel MAC). Some have been able to get it to run on Win11 with an Android emulator (I think). I've seen @Javi post that it's hopeful to get on Win11 natively, but maybe not a high priority.

There was a quick comment about that in a recent news post from UDI https://www.universal-devices.com/eisyir-flirc/ I haven't seen any posts of people performing this step, but it's an option. Here's recent discussion about it:

Sorry to take the topic off topic so much, but just had to. The claims were absurd. Back to point of OP using better methods of getting alerts. I think @MrBill's post above with the link to the variables is very helpful. @Jimini I think you could try both options to get a feel for how both work. I believe Pushover allows a trial period and then just a one time purchase for $5 and think that would cover any other devices you own and any in a "family" plan on Apple (not sure how Android does family/share purchases). @Jimini What Phone OS are you using?

I don't want to argue the point, but I'd like to know where this happens. I live in Atlanta (once, if not still, the largest local calling area in the nation) I don't have to use 11 digits. I have family in LA, they don't have to dial 11 digits. I have friends in NYC and they don't have to dial 11 digits. So if some of the most populated areas and largest local calling areas don't then what "metropolitan" area has to dial 11 digits to "call across the street"? Do you have first had experience of such or just read some random blog that might have inferred that?