Geddy

Perhaps it's best if you post the program(s) that you are expecting to run at startup. Perhaps they're scheduled and the schedule portion hasn't been met. Easiest way to share a program to the forum is to right click on the program, choose "Copy to Clipboard" then paste into your message. If you want to use the code block it would be okay, but it should paste as plain text anyway and will be easy for others to read and help make suggestions for any alterations you might need. As for folder conditions, that is not in the summary tab, but if you don't have folder conditions you shouldn't see the folder as an item/name in the screenshot you provided above so it's doubtful you have folder conditions, but that's not a full screen shot so can't say 100% for sure. Probably the most important column of the screenshot you have above isn't included. What's the "Last Run Time" for the programs you're expecting to run at startup? Depending on how the "IF" portion of your program(s) you might need to adjust the grace period. Please review this portion of the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order#Boot/Startup_Sequence_and_Program_Execution_Order Only other thing I might suggest is that if you have a large system and it's running the query at restart it could be missing that so many programs fire. In that case some people have put them in folders that the folder conditions would be triggered at reboot and then wait "x minutes" after the reboot to fire the programs. That's just a guess and a suggestion to alter how programs are triggered on a device/service reboot.

@Xcaliblur Welcome to the forums. When you install the nodes server make sure you select a slot for them to install into. It's defaulted to "Select Slot". If you forget to do that and hit Install it should give you an error on the lower right that says "Node server slot not selected". It goes back to the main install screen. If it was one that you purchased then it would show up in your purchased list, but it hasn't been installed because of a missing slot to install it into.

Take a look at this thread. If that applies to you. Since it seems Moblinc doesn't officially support the eisy there's not much that can be done, but I will say that it's still working for me on IoX 5.6.0. Another option (for iOS) is to run Locative + Occupancy node server (via UD Portal) to trigger geofence.

Do you mean the i3 Outlet (WR01)? It's possible that i3 still aren't 100% supported by IoX even though 5.6.0 did add some support on the i3 dimmer switch it's unclear if i3 is "fully supported" at this point. Might still be work in progress.

@Javi cannot confirm about crossing geofence as I haven't left my area today, but the app is set to "Always" for iOS 16.4.1 for me. I do not recall having to change it since the iOS update whenever it was released. @MrBill sorry...understood that your internet drops don't play in. I was thinking that it would potentially create an issue for not triggering something on the IoX if not connected. You're saying at the phone level itself the Geofence isn't triggering on your apps. Strange that your apps had changed settings. I do recall a a few popups soon after the 16.4.1 update for some location tracking apps asking me again to allow "always" tracking. I wasn't expecting some at the time so might have been tapping from muscle memory and inadvertently changed some to another setting without realizing it.

Glad you got it sorted out. @Javi has been great with creating and maintaining the UD Mobile wiki information for any other questions you might have. https://wiki.universal-devices.com/index.php?title=UD_Mobile And FYI, indeed MobiLinc Connect doesn't support the eisy, I've had no issues keeping the app (Mobilinc HD) connected to my eisy/IoX using ISY Portal access. I have control of all my Insteon devices; that works well for me. I have slowly been moving to UD Mobile, but my overall use of any mobile app is so small that it's not top of my list.

@tmorse305 as far as I know I haven’t had any missed geofence triggers. I don’t have one that fires daily so it’s possible there could be issues, but I use both UD Mobile and MobiLinc for Geofence. Both have continued to work fine in the last few weeks (since I updated to iOS 16.4.1). I don’t think there would be any iOS related issues, but does puzzle me if @MrBill is having issues now and then, but he has complained about Comcast dropping so might be network related misses (just speculation). I would think it if was a widespread iOS issues there would be a lot more posts here or on other geofence related systems like it was a few years ago when Apple really did break geofence in a major iOS release.

@TheA2Z it has been discussed here that email to text is very unreliable. T-Mobile had been one of the last to have complaints, but it’s not suggested as a “best method” these days. Best options are UD Mobile alerts, notification node server and Pushover, or network resources and Pushover. it’s very possible that T-Mobile is filtering email to texts just like AT&T and VZW have been more so over the last few years. You can find a lot of discussion on the forums using the search or Google Site Search for the forums.

Also confirmed can create programs while remote. Thanks @bmercier!

Sadly, I can confirm above errors are happening in IoX and UD Mobile (I just get the "Could not get programs data" error like @TSinclair). Unable to create a new program (worked fine on admin console yesterday). Adding to the oddity (for me), after I close Admin Console when I try to run it again I get a "Cannot determine a valid Java Home". I have removed Java, rebooted, installed Java, rebooted and still have this error. If I clear java cache and then run start.jnlp again it will load admin console just fine, but next attempt has issue. @gadgetfreak are you logging in locally or through portal access?

Correct. "ISY Portal Node Server" was introduced (on the ISY994) ages ago through the ISY Portal when you added the Occupancy Node Server. It comes across to Polyglot 3 (PG3/PG3x) as unmanaged (as yours shows). It is not "required" (as @MrBill replied). But if you're still using the Occupancy settings for geofence (as outlined in the wiki) then you would need to keep it available. If you're not using the Occupancy+Locative option for geofence you can remove the node server. To remove it use the ISY Portal web site (see image below...select Configuration then "Remove") Then you will probably need to remove it in your IoX admin console. Lastly refresh the dashboard for PG3x. You might need to restart PG3x (menu option under "System" in PG3x) for the database to update and remove the entry for slot 1. UD Mobile has just recently added geofence as an option. It does not need the ISY Portal option that you have installed.

What makes you think that? The UDI Z-Matter board/dongle was released in November/Dcember 2022 with Z-Wave support available at time of release. Zigbee/Matter was slated for hopeful release in "early 2023", but hasn't been released yet. Currently Z-Matter still only supports Z-Wave (as you said, works well for you...great!). Just because you can't add Matter or Zigbee devices to the Z-Matter products doesn't mean there are issues. It's just not supported by the UDI Z-Matter product yet. Additionally, you keep saying "Z Matter"... "Z Matter" is not a platform/standard. "Z-Matter" is the device that UDI developed; "Z-Matter" board (for Polisy) or dongle (for Polisy or eisy). It stands for Z-Wave + Matter support ("Z-Matter").

@peterathans no, and I doubt anybody outside of UDI knows when they would have them in stock. You could attempt to contact them through their web site if urgent (for your need/knowledge). Just know they might not give a direct answer if uncertain. https://www.universal-devices.com/contact-us/

Just make sure that you meet the requirements for "Latest Firmware". If you have Z-Wave you need to make sure which version you have before blindly upgrading to 5.3.4. Not really. Just read forum posts and wiki for migration help. If you're going to get the eisy you should be sure to review the eisy User Guide in the wiki. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide With your Moblinc are you using their "portal" (Mobilinc Connect)? If you are and you're on 4.x then I would probably cancel and disable that first. Would be good to also read through this if you're using Mobilinc Connect and wanting to setup ISY Portal: https://wiki.universal-devices.com/index.php?title=Main_Page#Switch_from_MobiLinc_to_ISY_Portal

@tony5isy welcome to the forums. Hopefully somebody can get you up and running again. Do you mean that the ISY994 is in safe mode? If so then it means the PLM is not communicating with the ISY994. Make sure the PLM is connected to “Port A”. First real question is what is your ISY994 firmware and admin console UI. When you log into admin console go to the Help menu then About and post a screenshot of the FW and UI lines, they will be next to each other. These need to match exactly before you proceed. Make sure the PLM is plugged in for a few seconds before powering on the ISY994. Observe the lights on the ISY994 as it boots up. Refer to the wiki for the light pattern during boot.

@mbking & @Javi nice catch! I don't have any favorites at the moment so might not have impacted me because of that. @Javi are you pushing 1.0.30 to test flight? Showing 1.0.28 currently. I know it might take some time, but didn't want to downgrade if it's pushing soon. Thanks!

@mbking try restarting the phone and see if it still does it. I just updated and do not have an issue. I'm on 14 pro max iOS 16.4.1. Do you happen to be running any beta version of iOS?

Exactly! Most don't. It's been a pet peeve for some around here since 5.x altered the UI. Glad that worked!

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/