Geddy

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.

@dwengrovitz I'm going to venture a guess that it DOES NOT since the information on the node server only mentions: The Ring nodeserver creates nodes for your doorbells, stickup cams & floodlights. https://github.com/UniversalDevicesInc/ring/blob/master/README.md

@macbannai it's been a while since I set it up and I'm not local so cannot check current configuration. I did see your post in the hue forum (earlier). I think my suggestion would be to remove the current installment you have and then reinstall. I know there were some issues early on, but I think that was both early eisy PG3x version and IoX issues that have since been resolved. The main issue is timing the start up of the node server and pressing the button on the hue bridge. It's not too time sensitive, but you need to make sure the node server is fully running before you hit the bridge button. I know since I had the bridge installed in PG2 and had not had an IP reservation for the hue bridge when I went to eisy & PG3x the IP changed and I had to add the configuration to look specifically for the new IP address. I've since had the IP address reserved in the router I use and haven't had an issue that I can recall. In one of your posts on the hue area you said: I'm not sure how/why you would get that error. That might be something UDI would need to check for through a support ticket. But otherwise, make sure the eisy is registered to your portal account. If you remove the node server and install again perhaps it would register correctly now. What version IoX and PG3x are you running currently? I know I'm currently on IoX 5.6.4 and PG3x 3.2.2, but I've been running the hue node server since probably February or March without issue.

@macbannai yes, with the use of the Hue node server - https://forum.universal-devices.com/forum/358-hue/

@glarsen and @gviliunas please submit a ticket to UDI to report this as a possible issue since it's been repeated. Support tickets are the only method UDI has to track possible bugs and issues. While they try to keep up with the forums sometimes issues like this might need special attention for review and, if needed, fixing in future releases. https://www.universal-devices.com/my-tickets

@ggitchell moved your post out to it’s only thread to get some help for your issue. Where you posted was a thread from months ago. It’s possible you need to update the eisy to current firmware (can be found linked in the “Current Release” area of the forums) to overcome your issue. Please let us know actual firmware number and UI you are running from the Help -> About screen. It is possible a power cycle might be necessary to get all systems loading correctly if you have attempted any updates. But please let us know FW version first.

Why not have the ISY trigger whatever you're trying to trigger with Alexa. Has it ever worked? Perhaps motion event status isn't being sent to Alexa now. Seems like something @bmercier could help with or else open a support ticket to see if what you're experiencing is normal or if something needs to be altered to pass the motion sensor status to Alexa. Still haven't told us what kind of motion sensor you're using. Perhaps others here have experienced with similar devices and can help.

I don't use motion sensors so don't have any ideas that might "help", but I have to ask...do you expect to see something report back to Alexa? What kind of motion sensors are you using? And why do you care if Alexa keeps activity (a log?) of motion? What's the reason for that? I do use Alexa, but never go check the app to see activity or status of devices. Help us understand what you're expecting/needing for us to figure out if what your observing is expected behavior. If the motion sensor is working (as expected to turn lights on) what are you looking for within Alexa? Unless you have Alexa triggering a device or routine when the motion sensor triggers I don't see any reason to even expose that device to Alexa. As you say the ISY is seeing the event and triggering as expected.

I agree with @Techman that this seems very isolated and unusual. I have quite a few disabled programs and they did not change status. Not sure if you could pull the IoX error log and review that or submit a support ticket and attach it to the ticket to see if something stuck out on the IoX side. @GTench - are you still having your issues? I would perform a full power cycle (depending on the device you're on use the multi function button to shut it down then unplug the device). Then clear Java Cache and start with a fresh slate. If you have the issue in IoX after what was a PG3x only upgrade perhaps something was already corrupt or something from the UDI side got released that shoudln't have. Either way, if you've attempted the backup twice and it still happens after a power cycle you should open a support ticket to get specific help. https://www.universal-devices.com/my-tickets

@RedReiter83 just in case this might have been a glitch in 3.2.1 please update to 3.2.2 (just released today). After you update, try using a different browser. I always use Chrome and it works fine. I've never seen it not populate the pull down where "production store" should show. You're on Firefox. Perhaps you're running a plugin or something that's blocking some portions of the site from loading. Try in a private browsing session and/or try in a different browser. When I tried in Firefox (and in Chrome) it never allowed the dropdown to be empty. Are you running any other VPN or internet security software that might block web from loading all aspects? Last option is to click "System" -> "Switch portal profile" and log into the portal again.

Thanks @bmercier for the update. Was able to update with "Upgrade Packages" then reboot and all seemed to work fine. Haven't pulled the power yet this time as things seemed to sort out well on first attempt. (@MBell, I wonder if more time was needed between the reboot and when you tried to log into admin console again. I allowed about 5 minutes (give or take) because I got into something else before I came back to the update.) For those that come later here are two screen shots to watch for: After hitting "Upgrade Packages" you get this alert (I usually leave this on the screen and don't go back to working on the admin console while the update is running) A few minutes later I received this alert: After clicking "OK" to both alert boxes was at the Configuration tab in admin console and hit "Reboot". Admin console closed and I allowed ~5 minutes before trying to open/access admin console again. I then confirmed I could log into admin console then tried PG3x web interface and all was right in the world.

@Jim P do you have remote connection enabled on the UD Portal? Requirements from the Node Server: PG3 Remote connection must be enabled and active Settings are in Portal under Select Tools | Maintenance | PG3 Remote connection After you updated to 3.2.1 did you run the system "Re-install all node servers"? I know you can't get this one installed, but making sure you got the others installed to get the UDI Python interface updated that's a necessary path. Not sure if that's something too, but just wanting to make sure that part has been completed successfully. In the meantime, could you also try to install a free node server to see that it installs correctly? Maybe something like Ping...just a random one. Can be removed if it installs correctly if you don't want/need it. Or any other free one just to try to make sure something installs.

Interesting that it doesn't go to the desktop by default. It always has in prior Windows versions. I don't run Win11, but if it's like Win10 just drag it up to the desktop. Otherwise, clear the Java Cache (checking all 3 boxes) then run start.jnlp again. That should add it to desktop. If not, your settings might be blocking desktop icon creation. I've not ever seen others say it doesn't add it to the desktop in Win11. Glad support resolved the issues.

What do you mean "stuck" on 5.6.2? If you're having issues with the update process at this point please open a support ticket and get help that way. Otherwise please start a new thread to get direct help to your issue. @mikeorst same for you. If you're "stuck" either post a new thread to get specific help or open a support ticket with UDI to get their help for the update process. https://www.universal-devices.com/my-tickets For most users, it seems to be smooth updates from "recent" versions. Since the pace of updating is keeping steady being several versions back might make it a little more difficult to support directly on the forums. There are a lot of posts to check for tips/tricks of making the update take. Usually the simple solution (at least step in troubleshooting) is to: Press "Upgrade Packages" button Leave alert/warning on screen In a few minutes if you're using UD Mobile you might get alerts of device going offline, then online Sometimes another alert will pop up on the admin console window that updates are complete and a reboot is needed. Press "Reboot" button in the admin console. Wait for UD Mobile to notify offline/online status (again) Depending on your hardware, perform a multi function button shutdown (review wiki user guide for your device to find this process) Pull the power supply Wait 20-30 seconds Plug in Wait 2-3 minutes Clear Java Cache (while waiting above) Download new start.jnlp Run start.jnlp Run IoX Launcher Access Admin Console (LAN) [if local] Confirm UI/Firmware in Help -> About menu The issue has been that some older firmware the "Reboot" button press in Admin Console isn't fully triggering a full power cycle of the device. It's stopping most services, but not enough to fully update the system. Many have found that shutting down the device and pulling the power is the best troubleshooting step to take. I suggest shutting down the device first rather than just blindly pulling the power supply because sometimes updates either can still be running or something else is stuck and just pulling the power could corrupt those processes.

It's not a given to go directly to PG3x, but that is indeed the only one that is currently being updated. For the Polisy running PG3 the current version appears to be 3.1.21. So confirm you are running that version at least. Moving to PG3x means that if you have any PG2 node servers still running that you will lose those as PG3x removes PG2 from the Polisy. You still haven't said which node servers are giving you trouble. It might be best, since you haven't provide enough detail to really help troubleshoot your issue further, to open a support ticket and get help that method rather than multiple forum messages to not get much further into the issues you are having. You can read more about the process of updating to PG3x on the Polisy User Guide in the wiki. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide

@gregkinney randomly rebooting to try to restart node servers is not a suggested "solution" to the problem. Best to narrow down what node servers are giving you issues and troubleshoot why they're acting up. 1st step is making sure you are on the latest version of PG3. Are you running Polis or eisy? Are you on PG3 or PG3x? If on eisy and not on PG3x 3.2.1 then you need to upgrade to that and then REINSTALL all node servers (it's a menu option, and in the instructions found in the announcement post for 3.2.1). From there you should focus on one giving you issues, put that node server log into debug and then restart the node server. After it settles download the log and contact the developer of that node server either by posting in that area or perhaps via forum PM. Sending them the log privately is best to get them to review it specifically to your issues. If the developer of your problem node servers is not active on the forums then submit a ticket to UDI and include the logs with the support ticket and maybe they can help identify what's causing them to fail regularly. https://www.universal-devices.com/my-tickets