MrBill

I tried to like that post, but apparently I've over-reacted today... silly forum.

I was about to resposnd until i got to this part.... which is probably the issue but I don't have the experience with 2 PLMs in the same plug (which might lower signal to the other) nor experience with houselink to point the finger.... @CPrince If diming these keypads is truly all Houselink does get rid of it, remove that has a potential issue.

If using windows, Install the ISY launcher on your desktop. Follow the instructions in the first post of Essentially if Java is installed go to https://isy.universal-devices.com/start.jnlp which the first time it's used will install an icon on your desktop named "ISY Launcher" When clicked, this takes you to Finder... which starts the admin console.

Start reading that thread from the point I linked, I think it will get you through it.

You might want to add two NR's first. One to send direct from the ISY, and one to send via the nodesever. Receiving both is a pretty good indication of when that point was reaches becasue as you know Pushover is pretty much instantaneous. From the ISY direct to pushover I use: (of course you don't have counter variables established so delete that part) token=[redacted]&user=[redacted]&message=ISY Rebooted ${sys.date} ${sys.time}\nUptime before reboot: ${var.1.42} \nSaved Value: ${var.1.43}\n\nSent direct from ISY. and then the ISY sends one thru the notification node server too: ISY Rebooted ${sys.date} ${sys.time} Uptime before reboot: ${var.1.42} Saved Value: ${var.1.43} Sent via NotificationNS Receiving both tells me the ISY is talking to Polisy.

I don't have a Mac but I've heard of this problem before. There is a solution in a thread somewhere, you might get lucky and find it... If not someone that uses Mac will reply here soon and give you the piece of information you need to select the zip file itself.

Just out of curiosity how long is it before you get the first email? As I mentioned above then end of my 9 minute wait is really about 20 minutes after ISY reboot. If I intentionally reboot ISY, I tend to reboot Polisy at the same time, however Polisy reboots in a fraction of the time. My polisy doesn't loose power during an outage (unless it's an extended outage), ISY does. I have a windows computer that I can power up remotely, I can then enable the VPN on my iPhone or iPad and use the app "RD Client" to connect to the windows computer using Remote Desktop. The windows computer has the admin console ready to go, and I can access Polisy that way too via a web browser on the computer. Due to the small screen of the phone it works better to use the iPad but i've done it all with the phone too. That in a nutshell is the plan should I need to manually intervene from somewhere remote. So far I've never had to use it but I have run tests.

Does this mean you had to log into Polisy and restart the nodeservers, or did you have to log into Polisy AND set the credentials of the ISY in the section shown below: If you had to set the credentials there, that's why nothing connected. The question then is how did saved the credentials get reset or removed. I have the same boxes checked. Startup for the ISY is rocky. There's always a raft of queue full errors in the error log. I've experimented with shutting Polisy down during reboot, but it really doesn't seem to make much difference. I do have a few programs (but not many) that I delay start. I have a few programs that I delay the start of, the method that I use involves killing two birds with one stone. First I use this program: Startup/UptimeCounter - [ID 008D][Parent 0126][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 9 minutes Resource 'ISYnotification.Reboot.Notification' Wait 10 seconds Resource 'NotificationNS.1704.ISYRebootNoticiation' 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) Updated 2020-02-15 now minutes in 10's (instead of hours) (slower update to reduce load) From this programs use, I know that the ISY does alot of thrashing about at startup. I don't actually get the reboot notification until about 20 minutes have elapsed, instead of the expected 9 minutes. The notification is sent twice... once directly from a NR to Pushover, and the second time it's sent 10 seconds later is via the Notification node server, that serves the purpose of telling me that both the ISY rebooted and that the ISY is talking to at least one node server. This is also about my only "run at startup" program, but you'll note that it runs a program called "Start heartbeats and Misc" which is quite a list... with wait 2 between each entry. You'll note that on startup the THEN body of this program runs... during that initial 10 minutes the status of the program is TRUE. The last statement of the THEN body runs the ELSE body of the same program, which itself is a never ending Loop, when the ELSE body run, the status of this program becomes FALSE. I use this fact to delay the start of some programs by using a folder condition. If Program 'Startup/UptimeCounter' is False Then Allow the programs in this folder to run. The programs contained in the folder don't run during the initial startup when the THEN body of the uptime counter is running. It should be noted that most programs don't cause an issue and don't need to be prevented from running. The ISY seems to not get to running programs very quickly in the startup process anyway, based on notifications that I've had programs send. One more thing... When I do reboot the ISY, I never try to start the admin console until I've gotten the notification. I usually tell Alexa to set a 20 minutes timer when I reboot and it usually goes off around the same time as the arrival of the notification. I hope that the startup process gets streamlined somewhat via ISY on Polisy. Edit to add: The Folders that I delay are specifically things that might try to send Insteon commands. Of course, if you've prevented something from catching up during startup, you've got to make sure it will catch up somehow.

If you're using a scene you should turn the scene on/off with alexa... If the scene is set up correctly all the KPL buttons should operate properly. If you turn the device on or off without the scene the button indicator will not change.

Brian, If you go up a level the rest of the products are available to click into: https://www.nokia.com/shop/en_us/smart-lighting

when web browsers are allowed to launch drive-by applets... You're not doing that. UD Mobile is new... still in development. It's actually grown rapidly.

You don't need a web browser that supports java, you do need to install Java from https://java.com/en/ by clicking the download button there. Next install the Launcher by clicking here. This will create an ICON on your windows desktop called ISY Launcher. Use that to start the admin console. (PS - there are other ways to launch the admin console, but that's the easiest for a newcomer.... It's also the method I used 99.9% of the time and I'm not new....?) For more detailed Launcher documentation see this thread:

Check again who you pre-ordered from... From this page https://www.nokia.com/shop/en_us/smart-lighting/nokia-smart-lighting-keypad/ you click where to buy. On the next page its says "Purchase from these retailers" and there is only one listed. WHen you click the link your on a smartlabs site: https://nokia.smartlabsinc.com/products/nokia-smart-lighting-keypad

Do you have a sceenshot of the NR you're trying to use and the error message window when you click test? Feel free to black out private info.

@silverton38 There's at least 2 threads on Nokia.. one is in the Coffee shop, the other might be the tail end of a long thread in the Smarthome section. there might be more mentions, the news hit around before the end of July

You can add the ISY to the portal and accept the connection in the admin console. At the point you will be using a free 30 day trial license for the new. The next step is to email support@universal-devices.com including both UUID numbers and your portal user name and request that they transfer the paid license from the old UUID to the new UUID.

Re-writing the switch setting is a thing that will lead to eventual early failure. However rewriting the switch twice a day is 730 times per year. A quick google suggest the life of an EEPROM might be 100,000 cycles. Lets say smarthome used cheap EEPROMS tho and the life cycle is only 10,000 cycles... that still means around 13.8 years before failure. That said... any chip that will fail over time, *might* fail early. In our bedroom there are 3 buttons on each of 2 keypads that might be on during the night, one always is they other 2 might be. Anyway I took the buttons off (removing the 4 little tiny screws) and removed the little clear plastic square and painted it with black fingernail polish (just for those 3), the reinstalled the black square of plastic behind the buttons. The result is a nice soft outline of light around the button. It's harder to tell those 3 are lit during the day time, but all 3 are things that you don't really need to see if the button is lit.

House Code M and Device code 13 are both prone to power line noise, with M13 itself being double scary, as well as All Off, the 4 bit binary code for each is 0000. M13 ON would translate to 0000 00000 0010 (unit code have a 5th 0 bit or M All Off 0000 0000 (where X is any unit code) There was no checksum, parity bit or anything else. There was a start code which was often represent as 1110 in writeups but it was really 3 active 0-crossings followed by 3 inactive 0-crossings whenever that occurs in noise, the following 0-crossings are interrupted as bits of an X-10 message... as you can see M and 13 and All off where easy to represent as 0000's (I wrote an early X10 software for the Novation Apple Cat modem. Optionally both a DTMF decoder chip and an X10 transceiver could be added to the blazing 1200 Baud modem, later it was available at 2400 baud. I got as far as being able to dial my modem line, hear a beep and enter some DTMF (touchtones) from the phone dial and have some lights turn on or off. No software whatsoever existed for either of the options, you had to read and write the modem registers directly. I tried to combine that with a commercial software package available for the Novation modem at the time called TAM, for Telephone Answering Machine. TAM used a 3rd party voice synthesizer for the outgoing message and then actually activated a cassette tape recorder to record an inbound callers message. Thanks for the trip down memory lane... that was early 80's)

Could you post the programs that monitors the Leak Detectors? Maybe it's written incorrectly, or perhaps it's a heartbeat program and the message you are receiving is misleading you into thinking it's a false alarm. To paste programs into the forum it's really easy... just right click the program name and pick "copy to clipboard" then in the forum push the <> button in the toolbar and a window will pop up, click into the window and type Control-v.

It will work. If your on the 4.x branch the path of least effort is upgrade to 4.9. From the release Note for Version 4.9: Be certain to follow the directions, and when you're done make sure to check Help > About and make sure both the firmware and UI match to 4.9

Another note to add... After you've updated the firmware and UI (they must always match). the Test button's test email will probably end up in spam. Your actual notifications won't, but the message that calls itself a test will.

What version is your firmware and UI? You likely need to upgrade. There are MANY threads about this, but in short all the way back at the end of last year UDI's outgoing mail server got hi-jacked by spammers. If you're on v4 firmware update to 4.9 if you're on v5 firmware update to 5.3.4

Have you updated to v5.0.4?

it probably will be. They seem to actually de-list items they don't plan to restock, for example 2845 Hidden Door Sensor has been de-listed.

I'll have to pass on this one, I have no Z-wave and don't know how it works in scenes. If know else responds I do know who to nudge....