Geddy

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

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)

Since you can add Insteon by typing in the address, but the "Start Linking" doesn't add Insteon OR Z-wave I would suggest you open a ticket with UDI Support so they can get some logs from you. That sounds like it could be a bug or other issue and they'd be best able to help. https://www.universal-devices.com/my-tickets/ It might help if you export your error log after attempting to link some devices. Please report back what you hear from support and how they resolved your issue so it might help others should they have similar issues.

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