Michel Kohanim

@whywork, There are two components to isy on Polisy: 1. Admin Console, all the UI, and all the meta data information (including major.minor.revision = 5.0.4) 2. The actual program that runs on polisy which has major.minor.revision = #1 (above) + isy_ver (_1, _2, ....) We use #2 for changes and things that we can do quickly to test. Compiling #2, does not change the major.minor.revision. Once we are happy and find no bugs in #2, then we do a full major.minor.revision. The issue with mail server is case-sensitivity. It's much more intrusive than we originally thought and also impacts backup/restore. We should have a fix by mid next week. With kind regards, Michel

@isy_troubleshooting, If you are certain everything is OK, then I think it's timeout related. There's no way an SSL handshake would be completed in 1/2 a second. With kind regards, Michel

@cwitter, We are looking into it. With kind regards, Michel

Thank you. We'll take a look. With kind regards, Michel

@Techman You need to use Admin Console (Cloud) and then reinstall the firmware + restore backup. With kind regards, Michel

@mbking, That was the issue. It's fixed. Thank you. With kind regards, Michel

@mbking, Are you using ISY Portal to check the logs or are you retrieving from the Admin Console? If the Admin Console, then are you certain you're on 5.0.4 (Help | About)? Are you using Admin Console (LAN) or Admin Console (Cloud)? The reason for all these questions, I cannot reproduce it AT ALL. With kind regards, Michel

@mbking, Changing timezone in Polisy does not automatically change the timezone/DST offset in ISY. You need to restart ISY (Admin Console | Configuration tab | Reboot). Apart from the time zone, what else is the issue? With kind regards, Michel

@tazman sudo pkg upgrade -f FreeBSD-kernel-polisy sudo shutdown -r now With kind regards, Michel

@tazman, What exactly is the issue? Do you get any errors when you start isy (sudo service isy start)? With kind regards, Michel

@srm, Just unplug. It's fully safe. With kind regards, Michel

@DKump, I already responded to your ticket. With kind regards, Michel

@mbking, This is not a minor issue. For ISY to get datetime/zone/network information, it must communicate with udx. If you do not see the correct timezone in the Admin Console, then there's something very wrong. Also, the IP address comes from udx. So, maybe udx is not running? (do you get the correct IP address in Configuration tab)? With kind regards, Michel

@jmsikora, Can you please send the output of df -h zfs list With kind regards, Michel

@mbking, The date was an issue we fixed in 5.0.4. But, older log entries were not fixed. So, you will see those. With kind regards, Michel

@mmb, These are X10 messages sent by something other than ISY (or perhaps they are responding to ISY). With kind regards, Michel

All, sincere apologies, one of the files was not updated. Please: sudo pkg update sudo pkg upgrade isy sudo service isy restart With kind regards, Michel

@DaveStLou, As mentioned, node servers must be removed and reinstalled. This has to be done from Polyglot dashboard. With kind regards, Michel

@ACoward, If you are still having the same issue, please send your error log to support@universal-devices.com. With kind regards, Michel

@asbril, The point of ISY on Polisy is to migrate iSY to run on Polisy so that you don't need two boxes. We started with INSTEON support. Once we get Z-Wave working, then you can migrate everything to Polisy. With kind regards, Michel

@mbski, Please create only one program through the Admin Console. The contents is immaterial. With kind regards, Michel

@bgrubb1, Most probably Java cache. With kind regards, Michel

Hi All, v5.0.4 is now available. Fixes 1. You should be able to use the Admin Console directly from Polisy (LAN) 2. Stopped our experimentation with time travel ... so, the logs will now have the correct timestamp (the old entries will continue having wrong timestamps). Also, separated error log from system messages. So, now there's a different log file (SYSOUT.LOG) capturing isy operational messages 3. Fixed the issues (case sensitive) so a) UD Mobile should start working b) If you have any node servers installed, you might have to remove them and restart 4. After Polisy restart, udx would need to be restarted for isy to work 5. And, finally, for the geeks out there, you can now disable uftdi driver in case you only use the serial port. All you need to do is to put the following in /etc/rc.conf and then restart the isy service: isy_load_uftdi="NO" Instructions sudo pkg update sudo pkg upgrade (at the minimum, you should have udx (2.4) and isy (5.0.4) sudo service isy restart (this will automatically restart udx if not already started) With kind regards, Michel

Of course, you can transfer ISY Portal license from ISY to ISY on Polisy. With kind regards, Michel

In 99.99999% of the cases, that's applied to ISY. So, it's up to you: either Polisy or ISY but NOT BOTH. With kind regards, Michel