Geddy

@Goose66 looks like you’ve hit the quota on messages. Maybe delete some and @drprm1 can msg you. LOL @drprm1 nice try. I’m “just” a user like many others. Only helping out on the forums to keep things neat and tidy at times.

@drprm1 probably best course of action is to submit a support ticket to UDI perhaps submit your ISY error log and node server log package in the ticket when you submit. This way UDI can review the IoX log files and review the node server log with the developer. https://www.universal-devices.com/my-tickets/ For the node server log click on log, change it to debug wait a little bit then restart the node server and wait again. If log has reset to "info" put it back in debug and operate the door a couple of times (by button/remote press, MyQ app, and IoX command). Just so all types of triggers are attempted and perhaps any logging done by the node server will be captured. Then download the log for the node server. The log type should change back to info, but be sure it's set to "info" when you are done. It's not a good idea to leave logs in debug mode. I think they have edited PG3/PG3x to reset it to info to not have huge log files, but best bet is to set it yourself. Of course UDI Support might suggest other logging options as well, but this will at least give them a better starting point when opening the ticket.

Posting on forums is not "reporting issues". If you have an issue you would like to "report" to UDI please submit a support ticket or contact UDI directly through their sales email. https://www.universal-devices.com/contact-us/ Perhaps neither business sees that there is an issue to resolve.

Since on Polisy have you converted that to PG3x? I believe for the Polisy PG3x is on 3.1.26 version. It's a great addition to the system to be able to trigger other events. I'm sure you'll get squared away.

@JBlake01 Are you sure you have an active portal license for the eisy? I'm not familiar enough with the process of install that I don't recall an IP address ever being an issue. I know it's looking for the ISY UUID for the target ISY, but not an IP address. I think support will be the best way to get you fixed up. Please post how you get this fixed so it can help others down the road. (And we can learn what happened too!)

@roblombardo same advice as above for you. Since the log seems to indicate it is installed correctly I would open a support ticket with UDI to see if they can dig deeper. Since this node server is so new there could be a few issues here and there now that more people are using it. If you get this resolved through support please post back what they did to help so that it might help others that run into this issue. https://www.universal-devices.com/my-tickets/

Did you click "authenticate" again in the node server? If I go directly to the link now it gives me the same error. But I clicked on authenticate again (even though mine is working) and it took me to that site. If you are not being forwarded to that when logging in then something else is blocking you. Possibly browser or OS related. I think the best thing, at this point, would be to open a support ticket with UDI and they might be able to review the logs and situation more to see what's happening for your specific issue. https://www.universal-devices.com/my-tickets/

What browser are you using? I seem to think that I had an issue when I installed it for some reason. I think I was in Firefox at the time. I think it was blocking some popup or new tab creation. I'd try from a different browser first. When you click authenticate it should open a tab to the Ring login site to login then prompt to allow UDI to use the Ring information. I just tried it in Chrome and it didn't open a new tab it just went straight to: https://oauth.ring.com/oauth/users/sign_in Maybe if you click authenticate then open that link in another tab you might get to the prompt, but I didn't fully try this time.

You can read the UDI announcement about ending support for the ISY994 on their site: https://www.universal-devices.com/byebye994/

I linked to the pin out in my prior post. You have to alter the adaptor to use the specific wires shown from the UDI site for the adaptor. I'm not sure if they've set it up prior to shipping out or if you have to wire it as such. I'm guessing that you don't still have the old serial wire that came with the PLM? It was tucked away in the box packaging so many people didn't keep it since the ISY994 used a standard cat5 from PLM to ISY994 even though it was using serial communications.

Just to be sure...your "installed, upgrade" means that you got the eisy upgraded? IoX = 5.6 (Firmware & UI) PG3x = 3.1.25 (Current versions as of this post) On the eisy I would press the power button 6 times to force a power down. The blue light will eventually turn read. (prior link to wiki for Multi Function Button) Once eisy shuts down (red light on power button) Pull the power to the eisy Unplug the PLM Wait a minute Plug in the PLM wait for solid green light (or maybe 30-60 seconds) Plug in eisy - wait for it to completely boot (maybe a few minutes) If still not working make sure you followed the pin out for the adaptor. Perhaps something is crossed up there.

Please review the steps in the wiki: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_Node_Servers_to_PG3x I didn’t migrate node servers so can’t say how it works or what to watch for, but seems straight forward.

THAT is possible…just have to use geofence (UD Mobile or other options) and can trigger programs when the geofence is exited that would activate/enable other programs to run while gone. Then the reverse when you enter the geofence that basically disables those programs (if you don’t want them to run when “home”). That part is simple!

No, at least I've never hit either of those buttons on the eisy. You might need UD Mobile to setup the portal trial on the eisy, but you've been around long enough you can probably run through those steps on your own without the help of UD Mobile. I think UD Mobile was just the quickest/easiest way to get users setup with the eisy and the portal trial straight out of the box. There are certainly the tried and true method of admin console from a computer (such as you've done) that should work just as well.

No. Doesn't appear to. Read the blog post from UDI linked above. Only options I see are "motion" and "ding". Perhaps something in the Ring side might pause or handle alerts differently depending on it's "armed state". The node server is only for doorbells, stickup cams & floodlights.

The license is bound to the Polisy Polyglot instance. It is not tied to a specific ISY/IoP instance. If the Polyglot uses the ISY994 in the ISY setup area then it will push the nodes to the existing ISY994. Since node servers aren't "installed" on the ISY then being able to see the ISY994 UUID is insignificant as you want to install it on your Polisy, but just make sure it's using the ISY994 as your active ISY/IoX instance. I don't have a Polisy so can't send screen shots, but in PG3x I have "IoX Configuration". Making sure your production ISY994 is checked in there and all node servers should target the ISY994 to send information.

Requires PG3x. Can run on eisy or Polisy that has converted to PG3x. Per UDI site blog post: https://www.universal-devices.com/eisy-ring/ And from Ring node server “more info”: https://github.com/UniversalDevicesInc/ring/blob/master/README.md#requirements

@pkauf Have you ever had it connected via a node server? The current node server doesn't list the j7+ in the supported product list. I don't have that model so not sure if it should work like those that are listed. (Source: https://github.com/BME-nodeservers/udi-roomba-poly/blob/master/README.md)

@kstev, for the time being Amazon still offers the Alexa site (https://alexa.amazon.com/) to reach the smarthome devices and at the bottom of that page it has a "Discover" button. You might test by removing devices from that page then running discover from the page to see if they come back in. Note that any routines you have in Alexa with any deleted device might need to be recreated (or edited to put the device back in the routine). Otherwise, I hadn't had any issues with Alexa discovering devices with vocal prompt, but I haven't added devices recently (maybe the past 6+ months). Could be a new "fix" from the Alexa team (that got fired) with limited support for new devices in 3rd party systems. As for the hints - yeah, new to me too. Not sure why or what is needed there. Haven't ever tried to add devices from node servers since many of their own systems integrate with Alexa I didn't want to have random names for the same device.

@Bumbershoot yep...and just moved this into it. I've been running this a little while since it was in the non-production store and it's been good. If I could just get a spider to quit building a web in front of the floodlight I could use the motion trigger overnight more often.

No. The node server links to the same cloud system they use. It's as if it's logging in just as you would with their app. It maintains the connection using the ISY Portal (at least that's how I read it as a reply from @Javi in another thread. Also, the YoLink has to handle the information somehow. It has to go from the (local) device to their (local) hub to their cloud then the node server syncs the information to IoX/eisy. It's not making a connection directly from the eisy to the (local) hub. Oh, and your mention you still have to select the name to get the mention to work. Still didn't get the notification to @MrBill, but that should.

I think I recall @MrBill saying elsewhere that he doesn't have any YoLink devices (yet). But you can look through the YoLink area of the forums to learn more or ask specific questions there for help. Also reviewing the YoLink information in the Polyglot store or even the github for the node server might be good sources for self help and answering general questions. You did misunderstand that. UDI has confirmed that they are working with Insteon to support the new i3 devices. UDI even posted a block in early March about the efforts to support new devices. https://www.universal-devices.com/i3-support/ As with many things in the IoT/HA field these days nothing should be considered permanent. It's always good to have an idea of what else is out there, but for the foreseeable future I think most of us will be fine with the new iteration of Insteon and the ongoing development that UDI has in place for eisy and Polyglot.

As far as I know it's never been negative in admin console. It should be accurate without using the negative.

I'm by no means a "tech geek", but setup is simple for many. Just have to read the instructions and trial and error. Correct. Current UDI ZMatter dongle only supports Z-Wave as of this time. Don't know what to expect until UDI gives more information and real life application of the firmware they will release. But given how the Hue line was developed you will probably always be better served with their hub. It's getting back into the whole Matter discussion and thinking process. I expect that all systems will still work better with the "hub" they were designed with, but the Matter support is expected to allow control from other hubs/controllers (mostly assuming it will be minimal control) . But at the end of the day, many of the fine details of the systems will still be best managed by the hub devices were designed to work with. (Just my 2¢)

Have you read through the Hue forum? https://forum.universal-devices.com/forum/358-hue/ It's super easy to setup and works very well. I don't mind having the hub because sometimes the Hue app is easier for my wife to set a color. But I only have a few bulbs. I think the "more info" link is still broken from the Polyglot store so you can see if there is more help from the git for PG3 - https://github.com/exking/udi-hue-pg3