Michel Kohanim

Hi mitch236, Please open this guide: http://www.universal-devices.com/docs/I ... 0Guide.pdf The process is: 1. Create a Certificate Request (#e, page 10). Make sure you use 2048 key strength 2. Send the Request to any CA (such as Verisign, Thawte, GoDaddy) 3. Once you receive your certificate from CA, import it to ISY (#f, page 11) With kind regards, Michel

Hi sorka, Sorry. I should have paid more attention. I sent the link to this post to the inventor of ISY Plugin for HomeSeer. With kind regards, Michel

Hi iostream212, We cannot yet assign values to variables. If you mean Substitution variables for notifications, then choose Utility - Meter from the drop down. With kind regards, Michel

Hi johnny66, The error log seems to be there. The regular log has 32K. Do you still not get any logs? If that's the case, would you please go to your browser and do: http://your.isy.ip.address/rest/log http://your.isy.ip.address/rest/log/error Please save and send both to support@universal-devices.com. With kind regards, Michel

sorka, What are you referring to? Are you referring to programs? Admin Console? Default web interface? With kind regards, Michel

Hi EVictory, I am so very sorry. The problem is that there's a zero size file. What you need to do is this: 1. Telnet to ISY and login (http://wiki.universal-devices.com/index ... o_Your_ISY) 2. At the prompt, type: RF /CONF/172.PRP Retry the backup. With kind regards, Michel

Hi jpjoe, It's possible that PLM was getting noisy itself. Just keep an eye for any anomalies. With kind regards, Michel

Hi johnny66, That's really odd. Can you please telnet to ISY, login, and at the prompt type: ls /log What do you see (and specifically, their sizes). With kind regards, Michel

Hi jpoje, That's quite encouraging! Please do another count on your PLM. If the number is above 800, then we will have to reduce them somehow. With kind regards, Michel

Thanks jpjoe. Do you now get status feedback from your devices in the Admin Console? i.e. you control them on the device itself and then status is updated in the Admin Console. With kind regards, Michel

Hi jpjoe, My pleasure. If you are already in the middle of File | Restore Devices, then please only do the last step. With kind regards, Michel

Hi jpjoe, Please do the following: 1. File | Restore ISY with your good backup 2. File | Restore Devices 3. Go to Tools | Diagnostics | Show PLM Links Table, click on Start, wait for completion, then click on the Count button ... how many links do you see? With kind regards, Michel

Hi Tom, thanks so very much for the update. With respect to your last question, unfortunately not. With kind regards, Michel

Hi jrini, It all depends on: from which firmware version did you upgrade? Since you upgraded from 3.3.10 then the sensor issue is moot (we added heartbeat in 4.0.5). As far as the SWL, I really do not know. That does not make any sense at all. With kind regards, Michel

Hi jmed999, It's whatever WB decides. I would assume it's the mean of max/min for the day (so max+min/2). This said, it would be best to verify with WB. With kind regards, Michel

Hi Michael, I think the problem you are having is the same as I always had before IM set me straight: ETo is not and instantaneous value; it's a sampling throughout a day and thus any usage of it at an instance-in-time (except when the next day begins) makes no sense and is probably a wrong value. You are correct on all other counts. jmed999, it happens at 12:00AM + the polling interval. So, if your WB polling interval is every 5 minutes, then it will be at 12:05. If every 15 minutes, then 12:15. With kind regards, Michel

Hi jrini, What procedure did you follow to fix the KPL issue? Please note that if those two other KPLs are V41, you really have to remove them from ISY and then add them back in using v4.0.5. With kind regards, Michel

Hi hyounker, Yes! With kind regards, Michel

Hi jrini, What's your ISY's firmware version? If 3.3.10, then you need to upgrade to 4.0.5 since we had to put a workaround (only for V41) because database operations don't respond properly on these devices. With kind regards, Michel

Hi Serge, This is firewall related. What firewall do you have? Please put ISY's IP address in the exclusion list or trusted zone. Or, you might want to use https instead of http to access ISY. With kind regards, Michel

Hi hyounker, Thank you. While waiting for our scheduled time, let's see if we can fix the device list issue. Can you please: 1. Clear your Java cache 2. Go to http://isy.universal-devices.com/99i/admin.jnlp Please try this URL and let me know if the UI issue is resolved. With kind regards, Michel

Hi LeeG, thanks so very much for all the help. Hi hyounker, links to our support team is below in my signature. We'd be delighted to help you. With kind regards, Michel

Hello johnny66, As I mentioned before, the URL you see on your tool is NOT what's on the wire. This, I guarantee you. Whatever you type on the browser is converted to something like: GET /path-to-whatever HTTP/1.1 Host: whatever-host Multiple spaces between GET and path should be tolerated. And, we have 1000s of these modules installed and none exhibit the same behavior. And, finally, nothing has changed since 3.2.6 and you still have the same issue with 3.2.6. So, it's very hard for me to accept that ISY is the issue here. Has anything else changed? Perhaps a new router? How long have you had your ISY and what model is it? With kind regards, Michel

Hi Michael, thank you. As much as I do not believe this to be the root cause, we'll certainly test it. Again, I think you lose connectivity first (for whatever reason and perhaps it has to do with your firewall or proxy) and then ISY pops up the authentication again. What you might want to try is: make sure ISY is NOT on the same network as the dns-name (i.e. you are remote) and see if that also exhibits the same problem. With kind regards, Michel

Hi johnny66, Thank you. HTTP commands do not have URLS. They have headers, so it would be: GET /whatever-path HTTP/1.1 Host: whatever-host ... As such, what you see is the tool interpreting HTTP headers. I really do not think that's the issue. It would be really great if you could: 1. Backup ISY 2. Downgrade to 3.2.6 and let me know if that fixes the issue With kind regards, Michel