MrBill

No one searches or looks for past posts due to the level of disorganization in this forum. After all who would go to a thread titled "Serial PLM discontinued according to smarthome" to find this post. I even suggested the same day: But typical for the disorganization found here, we've continued to the drag the original intent of this thread off-topic. Unfortunately properly managing an online forum takes a dedicated person and a fair amount of time. Pouncing on posts that drag a thread off topic and moving them to their own thread in the correct sub-forum. Conversely, pouncing on posts that have currently open topics and moving them into the thread they belong. Another "best practice" in support forums is to automatically lock threads without a new post in 30 days. This forum is all over the place, no one knows where to find anything. It also suffers from "too many choices", that is people can't guess the correct place to post because there are way too many sub-forums for the size of the community. Worse yet, some nodeservers have dedicated sub-forums and some don't, yet it would be a real mess if all 112 nodeseverves had their own sub-forum. I happen to agree with @whywork (although they actually didn't say rename anything) that reclassifying the Polisy section would be good... "Geek Batch" is outdated... It the equivalent of including the word "new" in a name.. time itself expires the title. However since that's really more about Hardware, I think Geek Batch should get renamed Polisy Hardware and OS, then immediately beneath that add the subforum ISY on Polisy. The problem with a new sub-forum named "Polisy Nodeserver" is that there is already an entire section named "Polisy Nodeserver".

Have you tried restarting the ISY? Next suggestion would be to check the error log (Tools > Error Log) and see if there are any clues there. Another question is what does the program do? Post examples... If any of the conditions change during the wait state, it will end the wait state. This is by design and not a bug.

To elaborate on versions people are spitting out.... 5.0.16C is the last ISY firmware version that works with a series 300 z-wave board. If your admin console has a z-wave menu, and Z-Wave > Z-Wave version = 4.55.00 then this is the version you need. You might also think about a z-wave upgrade board from UDI, with possible discounts base on the age of your ISY. If there is no z-wave menu at the top of the admin console, or the answer to Z-Wave > Z-Wave version = 6.81.00 then go to version 5.3.3 Be sure to read all the instructions. Generally upgrades go quick and easily these days, the exception is if your ISY Programs use "Adjust Scene", all of those programs will require a manual fix.

I helped someone else work this out, and I can't find the thread to link. the short answer is you need multiple daisy chained programs: Program: Door_is_unlocked If Status door is unlocked then Run program User_1 (if) Program User_1 (disabled) If access code is 1 then notification user 1 else Run Program User_2 (if) Program User_2 (disabled) If access code is 2 then notification user 2 else Run Program User_3 (if) .....and so on A disabled program runs if run by another program, but not if the IF condition is met. The problem with using 'ZW 003 Schlage Door Lock' User Number is 1' alone is that the user number doesn't always change, and to activate an If statement it needs to change.

log into https://alexa.amazon.com (from a computer browser) and delete every device and scene, then tell Alexa to Discover devices.

You just need to buy Pro upgrade. It's a soft upgrade, no hardware required.

ahhhh I see... anytime I try that browser I seem to have problems...

You sure? I have 5.3.3 installed on my no-PLM ISY and i just downloaded the file again: granted I didn't try to install that file but the LINK to download works.

Restore Device does work, or at least in should. How were you using it? Typically restore device is used after factory resetting a device to put the links back into the switch that the ISY thinks should be in the switch. Yes the GUI really needs some UX help. Fancy talk for they need to remove things that aren't used. And personally I'd use labels for each setting to the LEFT and move the SET button to the RIGHT side of the dropdown and call it SET or SAVE.

The write changes button isn't the answer anymore and the answer is not intuitive!! Set the dropdown on the RIGHT, then Press the button to the LEFT of the dropdown. In other words the buttons shown here are On, Beep, On Level, Ramp Rate, and Backlight. Yes those are buttons not just labels and Yes they act as the Set button for each parameter. Additionally there is a bug with Backlight. The dropdown starts at zero, that does not represet the current value set in the module. If we set this device to say 50%, the change will write to the device correctly when we press "Backlight" Now we move to another device this dropdown will lie and say it's 50%... It's NOT... it's whatever was last saved in the device. etc... Finally when the admin console is restarted the backlight will again show 0%, but that's not whats stored in the device. In other words you can accurately send values to the device using the backlight drodown and button, but they value displayed by the dropdown is never accurate unless you just now set the value. I really wish UDI would make this process more intuitive, and fix the backlight GUI bug, this is a repetitively explained in the forum.

Startup/UptimeCounter - [ID 008D][Parent 0126][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 9 minutes Resource 'ISY.Reboot.Notification' Wait 1 minute $iUptime.Counter.old = $iUptime.Counter.curr $iUptime.Counter.old Init To $iUptime.Counter.old $iUptime.Counter.curr = 10 $iUptime.Counter.curr Init To $iUptime.Counter.curr Run Program 'Start HeartBeats and Misc' (Then Path) Wait 5 seconds Run Program 'Startup/UptimeCounter' (Else Path) Else Wait 10 minutes $iUptime.Counter.curr += 10 $iUptime.Counter.curr Init To $iUptime.Counter.curr Run Program 'Startup/UptimeCounter' (Else Path) Wait 9 minutes to make sure the modem and router had time to recover (if this 'run on startup' was restore from PowerFail this delay is needed for the modem and router to come up before send a notification) then wait 1 min so notification goes out before counters reset (yes they reset too quick without a wait) I use this program. It's my only 'run at startup' program, although it runs others. Having only one 'run at startup' allows a tiny bit of load reductions at startup (see last paragraph for reason). The initial 9 minutes was to make sure the modem and router came back online first (although those devices probably never lost power). I initially was counting uptime in hours, but revised it to 10 minute blocks when I realized there should be a 10 minute delay in section (A). Traditional linux systems count uptime in 1 minute increments but 10 minutes increments were good enough for my purposes. Once the Then block completes once at startup, the else block loops forever. (in 5.x there is a repeat statement that could also be used but this program existed before that was available and this works just as well.) My systems fairly large, there are usually "UDQ queue full" errors on startup, I've found when manually restarting the ISY it works best wait for the reboot notification before starting the admin console. I don't think there is a method for the ISY to restart nodeservers yet. Edit to add: The date/time that $iUptime.Counter.old was last changed is also a handy reference point if you want to know when the ISY was last restarted without having to convert minutes to hours/days/etc then do calendar math... (yellow high-lite on the variables page shows the approximate date/time of the last restart)

yes... your ISY will have a unique long unique URL that looks something like this: https://my.isy.io/isy/77722bbbb555555069dba03f09795e63e57f02b6d7cbebebede80c0a22e334076 (I randomized that one) If used in a rest call such as https://my.isy.io/isy/77722bbbb555555069dba03f09795e63e57f02b6d7cbebebede80c0a22e334076/rest/nodes which will also require credentials, but unlike local rest calls its not looking for the simple local credentials, instead use your portal credentials. Edit to add: the unique url can also be used with the admin console remotely... Manually add to finder with /desc on the end. When the admin console opens with it's normal credentials request use your portal login credentials, the typical simple local credentials will not work remotely.

Yep... portal subscriptions are far more secure than opening your own ports and dealing with certificates.... the open port/certificate methods are really kind of out-of-date, but some people are holdovers that still use them and some people prefer them instead of cloud dependencies, and some people just plain refuse to spend on subscriptions (I'm in that camp most places... except UDI's because of it's low price point.) Start here.

Clciking Purchase modules should take you to an URL with www.universal-devices.com/my-account/?uuid=uuid: etc. Once there however it lands on "General" and you need to click "My Products" Just to make sure, its the admin console Help > Purchase Modules: EDIT TO ADD: I was already logged in to the UDI site today because I used the support portal (tickets) just a little bit ago. As I recall tho, the Purchas modules may not work right if you are not logged into your account on the website. Log into universal-devices.com then execute the admin console link to purchase modules.

Did you plug it into the bottom row and not the top? Also you need to purchase the Z-wave module. (Scroll down a little further.) its $1.00, Help > Purchase Modules.

To me it seems more like the rep at aartech is confused. I could see why they wouldn't want to accept PLM orders at this point, but there are cases a person might want to buy an ISY-994 without purchasing a PLM. I'm surprised UDI has not emailed them with reassurance that ISY's will be filled immediately and there is no shortage (of course maybe they did and aartech failed to respond).

As mentioned other people are going to be better at reading the events log than I am. One thing I note however... you have mismatched firmware and UI, The firmware is 5.0.16C while the UI is 5.0.16. This needs to be corrected and then you should retest. To be clear, both firmware and UI should be 5.0.16C. The best way to start the admin console is to use The Launcher (Launcher is different than Finder, people seem to confuse that point.) Launcher always matches the correct version of the admin console with the version of the UI being used. See the thread linked below for how to install Launcher, Launcher does require an internet connection (or actually maybe the latest version doesn't require internet connection... I'm not 100% certain on that point--there was a recent change--launcher is still the best way tho). If you still prefer you can still download and start admin.jnlp directly from the ISY, but if you want to continue using this method please delete you copy of admin.jnlp and clear your java cache then get the new admin.jnlp from your ISY.

Glad you got it working on another device. As for the one with the issue, you could open the Event Viewer and set it to level 3 and compare what you see between the one that works vs the one that doesn't. Or if you need interpretation post the event viewer log in the forum, and someone will point out what might be happening (probably not me, I'm not good with interpreting the event viewer).

I didn't see the need either, thus the reason I didn't re-install it. There are some people that can't live without Siri and want to use the apple Home app. Maybe if I started that way I'd still be growing my system from that aspect, but at this point it seems like just one more branch on a tree that adds additional maintenance needs that serves no purpose for my uses.

@Michel Kohanim and @larryllix I find it odd that the aartech link above advertises that the product is "on sale until July 12th". Why would would they feature a "sale" item, that they are not taking orders for?

Sorry to answer this differently that the question you asked, but save yourself the trouble. Instead of opening a port and installing a self-signed certificate subscribe to the UDI Portal instead. Less than $1.00 per month. Includes remote access to your ISY, Alexa Integration, Google Home Integration, IFFFT integration, portal nodeserver, the polyglot cloud nodeservers and more.

There is a roundabout way to get homekit support of ISY nodes. I don't know very much about it, and don't currently have it set up, so I can't tell you anything about possible limitations or answer questions. However when I first set up Home Assistant (I use Home Assistant more or less as an ISY front end) and was playing with things I added the HomeKit Integration and was able to add all my ISY nodes including insteon devices. After just trying lots of random things with my first install of Home Assistant, once I was comfortable with how things worked etc, and had a better idea of what I wanted to actually use.. I started over with a fresh install which of course erased my homekit integration, and I never set that one back up. In short you can use Home Assistant as a middleman. Add the Universal Devices integration first then add the homekit integration and it will auto discover your Insteon and Z-wave devices.

It's not intuitive: Set the dropdown on the RIGHT, then move back to the left and PUSH the button to the LEFT of the dropdown that you adjusted. (write changes is not needed). Specifically press the Label box for the dropdown: On, Beep, On Level, Ramp Rate, Backlight. Additionally there is a GUI bug with "Backlight", after you set it, and press "backlight" the change will be written to the device as expected. When you move to the next device the "backlight" dropedown will be prefilled with whatever you set the last device to, it doesn't reflect the value actually stored in the device. When the admin console is restarted it will say 0% again for backlight. None of this effects the actual backlight setting in the device, its just the admin console display. To rephrase, the backlight value can be set from the admin console, but the value displayed in the admin console is false.

that site is repairing a 2413u or the USB version. I'm not up to speed on the differences tho. the resident expert on this topic is @Brian H

for fastest assistance on that, you might want to open a ticket... send email to support@universal-devices.com