Geddy

@apostolakisl what version of Windows were you updating?

This has been "documented" (i.e. commented on the forums) a ton of times. It's well known that alerts using the SMS/MMS systems are being filtered by many mobile service providers. Thus the draw of the notification system that has been developed. VZW is found to be one of the worst for delaying email to text alerts. While I expect that it could be your receiving side or something between point A and point B know that if there is high amount of traffic coming from the UDI "default" email system that it could be considered spam by some relay servers and therefore delayed in processing or even bounced anywhere along the way. It's long been suggested that people setup an extra free email (i.e. gmail, yahoo, outlook.com) and use their servers for sending. Even some have setup an extra account on their ISP and sent to the same domain so not to have an account with a free provider, but be careful doing that because you might forget you have that setup and change ISP and suddenly not get notices (again...the great advantage of the notification node server system) Steps for setting up a Gmail account are in the UDI Wiki and are updated to reflect the current process for additional security that Google requires. Just note that Google/Gmail also has a requirement that the account be active so make an effort to log into that account a couple of times a year. It's not really. The issues are self inflicted. Either search the forums for delayed text messages or even search Google for delays sending email to text alerts. On an individual test basis (i.e. if you sent from personal email to #@vzw) it might be instant, but consider the volume coming from a "default" mail server and how providers are filtering such alerts you get the picture that it's the cell provider that's causing the delay, not the sender. Further, email to text is a large target for spammers. Cell providers are trying to stop junk texts and email to text is one way they've tried to limit such abuse of the system. This might have once been the best way, but it's clearly NOT the "best" method now. An alternative some have commented using here is sending to an email that only gets ISY notices. Using a 3rd party app (like Spark email) that you can trigger for alert sounds and allow during "do not disturb" or "Focus" times so alerts are still received and it is ONLY an ISY/UDI alert. This is somewhat clunky (IMO), but if your "group" is not willing/able to get UD Mobile alerts and if you want them to continue to get alerts email is still fairly quick, and IMO acceptable option.

This doesn't work with the eisy. You can only use the UD Portal option to connect Mobilinc to the eisy. Should have thought of something else before doing this. UD Mobile is currently supported by UDI and actively developed to work with Polisy/eisy while Moblinc Pro hasn't been updated for several years. If you're going to learn a new system you should have read a little more before buying the Mobilinc Pro. Glad you got it to finally work! Yes, Moblinc does not see any node server items. I'm not sure if it works with Z-wave or Zigbee because I don't use them with the app so haven't tested them. (You're asking the wrong person about how a mobile app works because I rarely use any mobile apps for HOME AUTOMATION (it's automation for a reason...so you don't have to adjust it!) Moblinc works fine with Insteon devices just as it did with the ISY994 (for my instance). Use it and see if it does or doesn't do stuff you want. If it doesn't do things you want/need then you should follow @DennisC suggestion of getting UD Mobile. It's currently being developed by UDI and designed specifically for the eisy (and Polisy) and the future expansion that UDI has planned for their infrastructure. Good luck! Glad you appear to have things working again. Did you ever resolve your initial question about getting things working with Alexa? That link is in the first reply I gave you.

This is normal and expected. It's possible that you were using the IP address in the past and this time IoX Finder window actually found the local broadcast address for eisy.local and added it automatically. I've had "Not Found" display sometimes, but it usually goes away if you're local and on the same network. Unless your router is running some sort of VPN or VLAN setup it shouldn't be an issue. I've never let "Not Found" bother me if the addresses were there. It's more or less something goofed up in the cache. If you're worried about it you can clear the java cache, delete the UD*.state files (look for reference to these in the wiki) then download a fresh start.jnlp file and add the IoX Launcher to your desktop. More than likely you've got the IP address cached in the finder window and it automatically added the .local address when it found it today. Mine actually has 3 entries because I also have the UD Portal URL listed since I usually access from a laptop and have that address on hand so I can login when remote. As long as you're able to log in nothing you've seen is a concern.

@737simguy after you're back and perform a full power cycle let's see what happens. I think Michel has commented that another IoX update was coming this week so perhaps that will be out before you return and further improve some stability. As for sensitivity to power supply...I don't think it's all that sensitive and think UDI added a delay for internet drops so it wouldn't notify users on a brief drop (I think that was a big issue when the notifications first started). You mentioned having an eero router. Is the eisy connected via wire or wireless? If wired is it connected to the base/hub eero or one of the satelites? Also, when you get back and can access the device locally pull an IoX error log and a PG3x system log when you get the alert or within the same day. The next step I would suggest is opening a support ticket and these logs would be beneficial to UDI to review what's happening to further troubleshoot. https://www.universal-devices.com/my-tickets Ultimately though hopefully updating to 5.6.4 and a full power cycle might be a big step in the right direction. I don't recall seeing any reports lately about random disconnects, at least not like there had been previously. Safe travels!

@737simguy it could very well also be an internet connection stability issue. So unless you're there and know there's not a drop on the internet side you can't be sure just what's causing it. I know I've had a few drops over the past week or so, but we've also been having some internet issues (who doesn't on Comcast?).

Yes, 6 button press should power down the eisy and the led on the button will turn red. On the rare times it doesn’t perhaps an update is still running. It’s not instant, but has taken up to 10-20 seconds for me to have the light turn red. It appears it should be performing shutdown tasks before powering down.

@ggitchell as @DennisC suggests try updating again with the button press since you can’t get into admin console. Yes, the one button push is the process. It might not process if the system has been up for a while so perform a power cycle again then let it boot up and sit for several minutes then press the button once. Allow fair amount of time then press the button 5 times to perform a reboot. Then you can try admin console again. Just for our reference are you using the LAN or Cloud option to try to connect? Try the other if you’ve only been trying one. Just another tool of troubleshooting.

PG3 cannot run on the RPi. PG3/PG3x is developed to only run on the Polisy or eisy. You mentioned PG2 on the RPi originally.

@ggitchell sorry that didn't work. It's time to open a support ticket with UDI and see if they can help get to the bottom of this. https://www.universal-devices.com/my-tickets Hopefully it's an easy fix. Please post back once resolved so it might help others should they have similar situation.

I can't answer the other questions as I never used ELK. Others have migrated from ISY994+ELK module to the eisy + ELK Node Server to better answer your other questions and situational concerns. I'll leave it to them to help you. Good luck! However, for this it's suggested you copy all current programs by: select the root "My Programs" folder. right click select "Copy Folder to Clipboard" paste to a text editor (for Windows use Notepad or equivalent - NOT WORD) This allows you to have a printed version of ALL your programs and even denotes if the program is "disabled" for if/when you have to recreate it. Using a regular text edited (like Notepad) keeps the formatting plain where as Word or a word processing program might manipulate code or spellings without you knowing it. Finally, you mentioned having a PG2 node server running on RPi, I don't know for sure, but don't think that can push information to IoX on the eisy. You can check the node server list (https://polyglot.universal-devices.com/) to see if what you're running is available in PG3x to make the move to the current offering.

I wouldn't suggest updating remotely. Mostly for the risk of having to perform a power cycle to fully complete the update. It's possible, but enjoy the time away and get to it when you can.

@737simguy If you "follow" the Current Release area when new topics are started you will get an alert (depending on how your notifications are setup) and you can review and update as indicated. Just go to: https://forum.universal-devices.com/forum/339-current-release-announcements/ Click the "Follow" box on the right side of the screen: Then set it up to email you or it will just alert you on the forums. I've found that to be very helpful to get an alert when new updates are released. There have been a couple of times here or there that I didn't get a notification, but figure that was just a system oversight, but it typically does really good to alert those following the area. And it only alerts you for NEW topics. Not replies or edits to existing topics. Lastly, after you update to 5.6.4 make sure your system reboots correctly. Sometimes the "Reboot" button hasn't fully forced a reboot of the eisy and many have had to perform a power cycle. I believe with 5.6.4 I did a power cycle even after it said to reboot to be able to get PG3x running correctly, but I think that even got fixed with the 3.2.2 PG3x update. Let us know how it is after your updated.

@ggitchell please perform a power cycle. Press the power button 6 times, the light should turn red. Remove the power supply. Wait 20-30 seconds plug eisy back in Allow it to fully start (2-3 minutes) - if you’re running UD Mobile it will probably say device is online if you have notifications on. While waiting clear Java cache (checking all 3 boxes) download a fresh start.jnlp from UDI site run start.jnlp and launch admin console Your screenshots above are indicative of Java cache needing to be cleared and updates fully completing.

@737simguy please update to current version (5.6.4) to be sure this wasn’t fixed in the update. Keeping up to date is essential and should be the first step in troubleshooting, especially when you have an issue similar to one reported almost a month ago and before the most recent release. https://forum.universal-devices.com/forum/339-current-release-announcements/ if you still have the issue after updating please post a new thread or open a support ticket so UDI can track any issues you might be having.

So you went from 5.3 to eisy. The migration path is clearly written that it works from 5.3.4. This is best served as a new post to get different attention/help. Your original issue appears resolved.

@baabm I’m not sure what to suggest. The steps look fine. But if you haven’t canceled Mobilinc Connect then you need to do that and only use UD portal to access the ISY service. I’m also not familiar with that version of Mobilinc so it might have other issues. Have you reviewed these steps? https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions You need to confirm on the ISY admin console that it is registered with UD Portal. That is in the Configuration tab then Portals. But you said it’s green on the web interface for the UD Portal so should be okay.

I’m not sure the setup of that version of the app, but review these instructions in the UDI wiki to see if you can get it to connect once you have UD Portal setup and connected to the eisy. https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration Just note that you will only need to set the Secure HTTPS as “my.isy.io”, port 443, and use your portal credentials….leave local settings empty.

Yeah...don't think there's a way to "move"/migrate from one portal to another. They've always been different animals. You could open a support ticket to ask just to check, but I'm afraid it's more than likely not possible.

Help us understand something before you get further into this...do you mean you used Mobilinc with their Mobilinc Portal? If that's the case then you're going to have to setup UD Portal as though it's the first time. There's no "migration" from one portal to the other as they've always been mutually exclusive. Now, if you had UD Portal setup and were just running Mobilinc (the app) and connecting via UD Portal you've got options (perhaps). But I don't think this is how you had it setup. I don't know how Mobilinc's portal worked, but I've always used Mobilinc (Pro) with UD Portal and it still works with eisy as it always did with my ISY994. You might be able to still use the Mobilinc app (perhaps...I'm not sure if their MoblincX app works as I was happy with the Pro). Lastly, it looks like you are referencing this area of the wiki: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 If so that's the correct method to setup UD Portal and Alexa Integration. PS: Please be sure to update the eisy to the current IoX and PG3x versions. You reference eisy running 5.3.4, but that was never a version for the eisy. Current versions can be found here: https://forum.universal-devices.com/forum/339-current-release-announcements/

I've not ventured into more of the Ring offerings than the Doorbell Pro and Floodlight cam myself, but I know people that have and they like the system. I'm sure if Ring opens up other devices to something controllable that it might be something UDI could consider. I know @Michel Kohanim commented (elsewhere in the forums) that Ring requested some sort of business plan for the interaction. My guess would be that perhaps Ring only allowed a small connection to the Doorbell and Camera motion and ring status for the time being. It's certainly something to consider putting into the Product Request category or contacting UDI and asking about it while giving a use case scenario. Take care!

@macbannai fantastic! Glad you got it to work. I'm sure you've done this (since it's been a "few" hours), but be sure you close and re-launch admin console. That should add the devices the node server finds. At least that's typical when new node servers are added or even any new devices added to a node server. Admin Console only adds new nodes on launch or some have the ability to query and it can get added. I usually make a habit of not having admin console open when making changes in PG3x since it needs to be relaunched anyway why have it open? I don't want to risk making changes in two different places and something not "take" and have to alter it again. In this case multi-tasking isn't always the quickest option. If you're bouncing around in the web portion of PG3x the log will always be blank when you first click on it. The log only displays information from the point you begin viewing it forward. While it's always logging entries you won't see the historical side of it. You would need to download the log files to get that information. When I was testing last night I had the log set to debug and then hit restart and the log went crazy (super fast - that's why I suggested turning off auto-scroll). Anyway...glad it's working. Hopefully it fits your need.

Just checked my settings currently. Somehow I don't even have the bridge address in the setup. Which bridge do you have? I think they have a v2 out as the current generation. It's the square shaped bridge. Since it looks like you've gotten beyond the part about the node server not being registered you should be able to restart the node server and it should automatically query the bridge. I might remove the address just to try it auto finding it. If you need it you can add the custom parameter in. Mine also doesn't have user/pass settings. I'd prefer not to have user/pass stored in the node server so hopefully manually linking as the node server starts up works out for you. If you want/need the user pass then you need to add them as custom parameters. Try this: Open PG3x to Hue node server log Change log to "debug", turn off AutoScroll Press button on Hue Bridge Restart Node Server Manually scroll the log area watching the output. Hopefully it will auto connect! Like I said...I set mine up a long time ago so I don't remember all the steps I went through if I had issues. So far it's working out okay. I know there was talk about a new API being worked on by Hue and I think the developer was holding off adding "new" stuff to the node server until that API was finished. I'm not sure the status of that, but if there is new stuff hopefully it will get added. Works well for my current situation though so I'm not checking it out all the time.

@macbannai Thanks...locking this thread and will help in the other thread you had from before.

Will try to help over here, but replied in other thread. After you remove the node server and re-install it let us know here if you're still getting the "Node Server not registered" alert. If you do you might need to open a support ticket to get assistance with getting the node server correctly registered with the device.