Michel Kohanim

Hi Seno, and there lies the problem. If those devices supported native Z-Wave scene, you would see either Scene or Association in the dropbox. With kind regards, Michel

@roberthleeii, Thank you. If you are on 5.3.4, and if Scene or Association do not show up in the dropdown (when you drag/drop them into the scene and click on each), then those devices are not capable of supporting Z-Wave scenes. With kind regards, Michel

@johnstonf, Local on the SD Card. And, when you backup ISY, it's backed automatically. With kind regards, Michel

@roberthleeii, Do you see Scene or Association in the drop down? With kind regards, Michel

@JAbraham, Apologies. You can add a new email address, make it Admin, and then remove the old one. Yes, this will change how you login. Your username (JAbraham) cannot be changed. With kind regards, Michel

@drprm1, Did you try 10000? Also, the error means that the server is returning 401 which means it does not like your credentials. With kind regards, Michel

Admin Console only works with Java 8 and, hopefully soon, with no Java. With kind regards, Michel

@roberthleeii, If they are indeed scene controller: 1. Create a scene 2. Drag and drop the controller as Controller 3. Drap and drop others as Responders Click on the Controller within the newly created scene and that choose Z-Wave Scene or Z-Wave association for each responder. With kind regards, Michel

@waffles, Thank you very much. It's very interesting that Synology does not require WOL authentication! With kind regards, Michel

@JAbraham, 1. Go to http://my.isy.io 2. Login 3. Click on the User tab and either change your email or add a new one With kind regards, Michel

@Jimbo, Haven't released it yet. We have a massive release for both UDX and ISY using the TPM chip. Should be by the end of this coming week. With kind regards, Michel

@DennisC, We have not tested with anything but with the firmware that comes with it. As such, I do not suggest upgrading at the moment till we make sure everything works. With kind regards, Michel

Yes, for sure. Unfortunately, we have never ever tested the Zooz with any other firmware except for the 7.15 that comes with it. As such, I am not so sure where the issue can be. With kind regards, Michel

@waffles, Yes, definitely but, currently, low on the priority. Also, are there still any computers that work with WOL without authentication? With kind regards, Michel

@someguy, Most probably the contents of the token file are not correct. Have you tried contacting the developer directly through Github? With kind regards, Michel

@travcore, 1. Telnet to iSY using putty 2. Login 3. Type the following command (case sensitive) followed by the Return key RF /CONF/138.PRP With kind regards, Michel

@brians, 1. ssh to polisy 2. copy the log to your directory: sudo cp /var/isy/FILES/LOG/debug.log . sudo chown admin:admin debug.log 3. Use the SCP command (on Windows) to copy the file from polisy : e.g. scp admin@1.2.3.4:debug.log . (change 1.2.3.4 with the IP of polisy) With kind regards, Michel

@Jimbo, Definitely an issue that's been fixed. With kind regards, Michel

@Techman, Thank you for reporting. We are trying to reproduce. With kind regards, Michel

@drprm1, SNI must be checked AND you need to increase your timeout. With kind regards, Michel

@JoelW, This can only happen if your PLM does not have links to your devices. So, you need to find a backup from before your PLM died and then Restore your Modem. If that does not work, most probably your PLM was not resurrected and it's dead. With kind regards, Michel

@brians, Thank you. The next time it happens, would you please send me your error log to support@universal-devices.com? With kind regards, Michel

@drprm1, Please upgrade to 5.3.4. With kind regards, Michel

I don't think so. You can always look at /var/isy/FILES/LOG/debug.log to see whether or not the issue was connectivity with the dongle. With kind regards, Michel

@bradshawkyle, in addition to excellent suggestions by @stillwater, when this happens next, please check the Last Run Time column for your program. If the time is accurate, then the problem is signal (for INSTEON) and ISP/carrier/SMTP server (for notifications). If the times are not correct either, then either the clock in 994 is dying or you have other conditions in the program the impact the time. With kind regards, Michel