Geddy

Probably nobody familiar enough with the issue to help. I don't use this node server so can't help in anyway. Tagging @xKing as listed developer of the node server on PG3 store. Otherwise, you might want to go to the git and raise the issue there to see if it gets any resolution. https://github.com/exking/udi-mqtt-pg3

Check out this post and pay attention to the version of boards in the ISY994. You either have 300 or 500 series boards in the ISY994. The ZMatter dongle for the eisy is said to have much better range. So if you did try and didn't have good range results from the board in the ISY it's possible the ZMatter dongle would improve range slightly, but as @Technesssuggests above you should build out a strong z-wave network for it's mesh properties. If you bought the ISY994I ZW+ PRO directly from UDI then it should have a Zwave. If you bought it 3rd party it's possible the z-wave board could have been removed before selling. Only way to know for sure would be to open it up (wiki instructions) and confirm the board is installed. Last comment would be if you power up the other ISY994i ZW+ and log into the admin console...if it says you're in safe mode it's got a firmware that is looking for a PLM. If you're just going to test Z-wave with that device you should update to the Z-wave only Firmware so it wouldn't be looking for a PLM and not be in "safe mode". In the "Current Release" area find the firmware that fits the version board you have and look for the link similar to this, "ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM)" (specifically the part bolded).

It’s in the current release area. Directly:

@JMarotta this doesn’t seem right, but I don’t usually control the Hue devices from admin console. What IoX firmware and UI are you using? (In admin console use the Help menu then “About”. Make sure these match exactly. (As of this posting IoX version is 5.6.0) What is your PG3x version? (As of this post current version is 3.1.25) Have you rebooted the eisy lately? Are there any errors in the Hue log on PG3x? The log might not display on the web without a refresh, but you should be able to download the log and review that. Maybe put logging in “debug” mode and try to restart the node server try to control a device then download the logs again if they don’t appear in the web display. (NOTE: don’t leave logging mode in “debug”, change it back to “info” or “error”)

Note that Insteon devices cannot be linked to multiple controllers. If you migrated to eisy your ISY994+Serial PLM should have be taken offline. There is no such thing as "running in parallel" as the links to the devices will migrate to the new PLM. If you try to link them back to the ISY994+Serial PLM then they won't work in the eisy and you'll just have to re-link them to the eisy+USB PLM to have them controlled by the eisy. This is as designed by Insteon. But glad you got whatever you were attempting to "work". It's never a good idea to leave an old system running because that will risk causing more problems. Just following the migration steps released by UDI is the best path to a successful ISY994 to Polisy or ISY994 to eisy migration. Any 3rd party integration should be handled separately and at the end users own "risk".

@oamber don’t unzip the file downloaded to update. Let us know the following (related to the ISY994) What is your current firmware on the ISY994? what computer OS are you using? do you have/use Zwave? if yes, see this post about zwave version follow the directions to upgrade to the proper 5.x version Finally, let us know what firmware you are trying to upgrade to. (On the ISY994)

Insteon devices can only link to one controller. Something has got to give up if you're trying to run both the eisy and ISY994. Which device is your PLM connected to? That's going to be the only device you can control the devices with. If you migrated to eisy from the ISY994 you should have moved the PLM to the eisy as part of that process. You can run two controllers and have 2 PLM in service, but the devices can only like to one PLM. Your newly linked device to the eisy is probably the only one you can operate through the eisy as the others are still controlled by the PLM connected to the ISY994. Is there a reason to keep the ISY994 in service? Note: if you bring over the PLM from the ISY994 to the eisy the sole device you connected to the eisy will need to be re-linked with the other PLM (once connected to the eisy). Make sure you follow the migration instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

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!