Geddy

In prior posts this was classified as an "information only" type error. Indicating that it is not a real error and could be ignored. I am not sure if this has changed in Polisy/eisy era, but feel that if things are working well then it continues to be information only and could be ignored. You reference a -70001 as Vector error, but you seem to have just left out the first "1" from the actual error code. I also get a lot of the -170001 "errors" and don't worry about it. And that's just a small section of the error log from this morning.

Beyond what others above have all helped out as troubleshooting methods...if it is a power supply here's the info From the Wiki - "You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector" No, because of the changes from 4.x to 5.x the only way to migrate is from the 5.x branch. If you have Z-Wave installed on the ISY994 you need to be careful which version of 5.x you would upgrade to. Presuming that you get the ISY994 operational again upgrading might be in your future. But it takes a little bit of effort so don't attempt it randomly and without reading all the directions and posts about the update first. Highest priority is getting the current device operational again. Then you can consider updates and new hardware. Good luck!

@K-bert It's very strange to get a successful message then nothing. It might be time to submit a support ticket on this to see what's happening. I know with my Gmail settings I can send a test and it works in back-to-back attempts (I allow about 20-30 seconds between presses). When you're using Gmail make sure you are using an app specific password. It will NOT work if you're using your usual user@gmail.com password. Gmail changed last year to require higher security settings and not allowing random apps/services to just use user@gmail.com/password to log in. Be sure to follow these instructions: https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings#Configuring_(unique)_App_Password I doubt it matters, but maybe put something in the "From". It isn't required, but adding something might help. I just tried with mine and it sent fine with or without something in there and I'm using Gmail. My screen looks this way:

I think you're misinterpreting the meaning of "run" in your situation. Programs always run unless they are disabled. If you didn't want something to "RUN" then you could handle that in two ways... Split this into 2 programs and disable the 2nd program and only call on it from the first program. Put program in a folder and then set folder permissions to only evaluate during the schedule. This is tricky and should only be done in rare cases and by advanced planning and understanding of folder conditions. (See section 9.5.7 of the ISY cookbook for discussion of Folder Conditions) The program "evaluated" the IF portion. It didn't "RUN" the "then" portion because it was "False". With nothing in the "Else" there was nothing to "RUN". Are you saying that the lamp was on and turned off at a time you were not expecting it to turn off? Both @dbwarner5 and @Javi have explained the program will always evaluate the "if" and react accordingly. In your program both events must be true for the "then" to trigger. Otherwise, the program is false and the "else" would trigger. With nothing in the else then you don't perceive the program ran unless you look at the summary tab in admin console and see the "Last run time" as you are showing. To test this you can set a random light to turn off in the else then manually trigger the program "run if" while the lamp is on. The random light should turn off. Now...delete that from your program because you don't want it randomly turning off later! Additionally, you can test the current program while sitting at the computer by right clicking the program and selecting "run if". The program would trigger and set a "Last Run Time". The "Status" should also remain "False". While still viewing the summary tab, use UD Mobile, admin console, or other method to trigger the lamp on. You should see the "Last Run Time" update again. And it should still show status = false. This means programs always evaluate the "IF" statements. To stop that the programs need to be disabled or in a folder with conditions met to stop programs from being evaluated. Lastly, if you indeed come back and say, "yes, my lamp turned off at 7:05am" then you could have an issue with another program. The program you pasted would not have turned the lamp off at 7:05am.

@K-bert thanks for updating with the info from the support ticket. That's helpful! I had been suspecting that many of the problems being faced with ZMatter are due to how different device manufacturers incorporate things differently. With the rapid growth of "generic" devices coming to market being touted as "z-wave plus" I'm sure many meet the bare minimum of any z-wave "standard". That's got to make it difficult for a controller to try to handle every little difference. Hopefully there's a solution soon!

Command Class Hail (0x82/130) Version 1, Controlled This Command Class is transparently implemented in the library to trap unsolicited reports via Hail in legacy devices. Data holders: hail: Updated every time Hail command is received (Source: https://z-wave.me/manual/z-way/Command_Class_Reference.html#SECTION0016530000000000000000) I don't use z-wave (at least not much...yet), but seems that it is/was a way that ISY would update the device status if the device didn't report status naturally. There was an old post that used a program to query the device when "hail" was sent so that the status in the ISY would match the switch/device status.

@K-bert Make sure that you have at least one "group" in the lower section of that setup screen. Also make sure one group is selected when you run the test to. I just tried from my eisy with the default server settings checked and don't get an error. If you continue to have issues you might want to try setting up a dummy Google Gmail account and use that for sending. Note that Gmail now requires higher security and an app specific password. The instructions on the wiki will walk you through setting that up to be sure it will work. If you still get the error take a screen shot of the SMTP area and group area (white out personal contact info) just to confirm it's saved correctly. Double check that the test message didn't go through. It could be showing up in your junk mail of the address you're sending it to. Sometimes the test message goes to Junk but actual notifications don't. It's possible the system thinks it was rejected, but it actually connected and sent the test.

@K-bert This is another one that probably the best way to get the attention of UDI at this point is through a support ticket. It seems the biggest issue is indeed z-wave/ZMatter related so individual devices probably need to be handled through bug tracking, and that's best handled through the direct support process. Good luck! And if you get any tricks/fixes in the support request please update here in case others need assistance similar to this.

@K-bert please review post above yours from @DennisC. A support ticket is the best way to get info to UDI if you consider this a bug or other issue.

@FerventGeek seems more like a developer question than general user support question (the primary function of these forums). Perhaps this would best be something you ask UDI directly through the "contact us" found on their site.

I think your questions are best asked directly to UDI. You should contact them through their website: https://www.universal-devices.com/contact-us/ As for the forums this is more for user-to-user support and UDI does help out with keeping things in line from time to time, but currently the focus is on sorting out the eisy release and keeping IoX moving forward. @BWalsack I think your primary question (related to PLM) is deserving of a new post, but will leave here so you can "follow" the prior questions. Best way to "follow" a thread is clicking the follow button () at the top and setting up how you get notifications from the site. But, for your issue of connecting the PLM to the eisy you need to get the Serial PLM kit that UDI offers to handle taking the PLM signal from the rj45 jack (really a modified cable using serial signals) to a serial DB9 then the DB9 to USB cable. This is mentioned in the eisy page under "Device Support". There are numerous other posts about how to connect the serial PLM to the eisy. Additionally, there was a rj45 to DB9 cable included in all serial PLM boxes. Many long time users might have tossed the cable since the ISY994 accepted the modified rj45 connector and didn't realize the Serial cable was also in the box. If you still have your packaging look in there. Please note it's NOT the same as just taking a standard network cable and going from PLM to DB9. This information has been posted in many other threads. Use the forum search or Google Site search to look for "pinout" configuration. A lot of this was covered in the pinned post by @lilyoyo1 in this area. Should you have further related sales questions I suggest you use the "contact us" link provided above to directly pose these questions to UDI. These forums are more for after purchase support rather than sales support.

If this was an issue in prior releases it might not have been reported through the support ticket method to alert UDI that it might have been a bug. If you're still seeing this issue please submit a ticket to get specific review of the issue. https://www.universal-devices.com/my-tickets

Seems like you should submit a support ticket to get assistance. It might be a bug and UDI needs to review what happened.

What do you mean? What's showing "undefined"? Where? Will you provide screen shots showing what you are talking about? It's possible you need to reboot again so that everything comes up correctly. Don't try to access Admin Console or PG3x Dashboard too soon after powering on the eisy as there are a lot of processes running. Have you attempted to re-install the node servers? Go to the "purchases" area and try "(Re)Install" on node servers that you're having issues with.

No issues here. Email notifications still working as expected. Just ran a few that are triggered by programs and they spun out an email just fine. What are you using for email server settings?

@pjjameso you can have ISY devices trigger an Alexa Routine. See some of the discussion in these threads: @dbwarner5 has a post in the first thread with the steps at the time. Perhaps they still apply.

@EW1 welcome to the Universal Devices forums. It appears there are two Sonos node servers available (Sonos and ST-Sonos). Which one are you using? I think @lilyoyo1 covers the how to achieve this. Hopefully it works with the node server you're using. If not please provide more information related to your system for which node server and what Universal Device system you are using.

As @DennisC points out I'm not sure what you're referring to as "faux Node Server" (you later say that @Javi has called it that). I don't pay much attention to Elk stuff so maybe there is something like this, but just don't know. As far as I know "node servers" run on devices outside of the ISY994 that you have and feed information into the ISY994 system. In the past it was Polylgot Cloud (of course cloud based - closed last year) or Polyglot v2 that could run on rpi systems (now also not being supported by UDI or many developers). The current offering is Polyglot v3 and available only to run on Polisy or eisy. If you want a true node server process to continue with the Elk system then you would need to get an eisy (or used Polisy) and run that way. It can clearly still push data to your existing ISY994, but the Polisy and eisy are designed to replace the ISY994 and add all the functions of node servers (not just the Elk system). Since you say you don't want to migrate to another hardware then you're somewhat limited. I expect that ISY994 + Elk Module should continue to work as it does now. Knowing that UDI is ending support for ISY994 you're at the mercy of it as it is today and if you have issues getting help here (which isn't bad, IMO). I think it would possibly be wise to consider upgrade viability for your system(s) to give you even more control than you currently have with the ISY994+Elk Module.

I've learned in this process that I prefer to make sure I log out of PG3x prior to updating anything. This way it forces me to login completely (Portal then PG3x dashboard) before I'm in the system again. It's just a process I added that usually allows me to avoid such issues. I don't know if it really does or not, but I figure it can't hurt. My thought is why have an open login on a system that you're trying to update. If you log out then only system processes should be running and nothing that I might have had open/editing/updating would be locking something that might need to be updated/overwritten. Kind of like installing a Windows program...it warns you to close all other programs before installing. How many of us actually do that though? I sure don't, but with IoX/PG3/PG3x I have made it habit to log out of anything I can if I'm not using it with hopes to avoid issues on next use. Glad #4 update/reboot worked for you.

@tlightne I think with all the issues being worked on at the moment the best way to communicate with UDI about a specific issue is through the Support Ticket process. It also allows them to troubleshoot bugs in the Z-Wave and IoX system. https://www.universal-devices.com/my-tickets/ I think you recently commented that you're going to hold off on the 5.5.7 update even though you're already on 5.5.6 and have issues. I'd suggest at least updating so UDI has information from the current release to try to resolve your issue.

It's odd that it continues to come up. And no, there's no "set"/known amount of time to allow. I remember @Javi suggesting as much as 30 minutes in the early release days of the eisy. Hopefully it's not that long now, but could be at times. Thankfully, I usually perform updates when the system isn't needed so I can work on something else and come back to it. I think others had reported this window, and I know I saw it after the first update process (I think it was on 5.5.6 though...for me at least). If you still have it then be sure you clear you Java cache too just to be certain. Since there aren't lots of posts of issues with the 5.5.7 update I think a lot are finding it worked well...or just haven't tried it yet. If you continue to get it then you might want to open a support ticket to get help and give feedback directly to UDI about this issue. Ticket link: https://www.universal-devices.com/my-tickets

Correct! Yep. the issue that @garybixler posted was a "subscription" issue probably had nothing to do with updates. If you followed the URL posted previously (http://ip.of.the.isy:8080/rest/subscriptions) then the result is the .xml for what is using the subscription slots. There have been many posts about there being a limit for simultaneous connections. Typically Portal will always occupy one slot. Others might be node servers, other mobile apps using port forward, and then there's admin console (if local). It's usually a random occurrence, but @garybixler implied that it's been happening more recently. If it continues to happen try to narrow down when it happens and open a support ticket. It shouldn't be happening often.

I believe there is a 10 sub limit. It’s possible some node servers aren’t releasing correctly and you get the error. They should eventually clear, but it can happen if you’re keeping admin console open a while. It can also happen after a reboot as nodes try to update and push data to IoX. Next time you get it (or just to check) see what you get using this URL: http://IP.of.the.ISY:8080/rest/subscriptions Make sure you use your device IP. I think updates would have resolved other issues, but not the subscription issue.

Are you using any mobile apps and have a lot of node servers installed? Do you get this soon after a reboot/restart or randomly? It’s possible there are a lot of things trying to connect at once and limiting the subscriptions connecting to the ISY/IoX process. There was a URL given recently to check, but I forget what it was in relation to. I think @MrBill referenced the URL. (Sorry mobile at the moment so unable to search forums to look for it)

@mbking I experienced the same thing last night. It should give you a force update option. What version is your app?