Michel Kohanim

j0dan, The errors are those that are generated by the server. Timeout means that the server did not even respond within the timeout period that you can configure. Read response failed means 404/401. You should be able to see more information in the Event Viewer. With kind regards, Michel

Hello andyf0, I am hoping to have a release by the end of next week. With kind regards, Michel

Hi Steve, Yes, it makes a LOT of sense. Network Magic basically roams around all IP addresses in your network and tries to send them random http requests. And, obviously, ISY does not like it since the requests do not include the authentication headers. With kind regards, Michel

Hello zmzmzm, Yes. With kind regards, Michel

Hello jellis, How old is your PLM? In my experience, if the PLM fails once, you are almost guaranteed that it will fail again. If it's still under warranty, I recommend getting it replaced. With kind regards, Michel

So am I! I would've assumed it's lumen or lux but there are no other indications from which we can deduce what it is. With kind regards, Michel

Hello Steve, The first thing is to figure out if ISY is in the middle of these phantom activations. Is it possible to unplug your ISY for one night and see what happens? Do you have anyone else trying to login to your system? All those are authentication errors. With kind regards, Michel

Hello thruster999, Just got this email from SmartHome: "I have not heard of motion sensors losing links, but there have been reports with KPLs. A motion sensor failing to turn on a responder might not be the motion sensor's fault. It could be a KPL failing to respond." When this happens next time, would you be kind enough to restore only your KPLs and not the sensor? This would let us know where the problem is: the sensor or the KPL. With kind regards, Michel

Hello joefly, I think the best is for huddadudda to: 1. Change the password on his rule 2. Save it 3. Export it and send it to you Then, you would: 1. Import 2. Change the password 3. Change the port/IP address and test With kind regards, Michel

Hello joefly, Are there any type of credentials for this utility? If so, you might want to try adding an Authorization header in the request. Also what is the URL for the page you have posted? If it has a path, then you will have to put that path before the ? (make sure you remove the ending /). With kind regards, Michel

Hello joefly, The path does not look normal /?xxxx ... you might want to remove the initial / and see if that helps. Above and beyond that, we need to look at the URL for sleep by viewing the HTML source of the page that allows you to put your computer to sleep. Do you have that? With kind regards, Michel

Hello thruster999, Thanks so very much for the detailed info. Yes, please do keep us posted. I have already contact SmartHome and hopefully we'll hear back from them soon. With kind regards, Michel

Hi LeeG, Thanks so very much ... I do appreciate it very much. With kind regards, Michel

Hello thuster999, Thanks so very much. I am going to forward this post to our SmartHome contact to see if they have any information. With kind regards, Michel

Hello thruster999, Thanks so very much. Can you tell me whether or not these are V2 or V1 thermostats? V2 thermostats have 4 nodes representing each. With kind regards, Michel

Hello LeeG, Thanks so very much ... I am not sure what is causing this issue either. It might have something to do with duplicate RF messages and perhaps we are not ignoring an echo as we should. I cannot reproduce; so, in your case, do you have to press an RL button multiple times before you see the erroneous DOF? Does the same thing happen with DON? With kind regards, Michel

Hello thruster999, No we have not ... but, do you have any thermostats in your system? (very important question) There have been reports of motion sensors losing their links but they are quite isolated and I am not aware of any SmartHome activities in this respect. There are also reports of devices (such as KPLs/SWLs) losing their links after power outage. I do not think this is related since, in your case, we are dealing with battery operated devices. With kind regards, Michel

Hi Orest, This is not a release notification but about what you should expect in 3.1.3. We are waiting for a few more enhancements before we release 3.1.3. With kind regards, Michel

Hello phenneberry, 3.1.3 is not released yet ... how did you upgrade to it? Please do not try downgrading. Simply point your browser to http://www.universal-devices.com/99i/3.1.2/admin.jnlp . With kind regards, Michel

Hi LeeG, Perhaps I can shed some light here: Group cleanups are handled in the same way as an SRX; i.e. if send a group command through ISY (scene test), then there are four cases: 1. SRX was received so the device acked the command with no group clean up 2. SRX was received with group cleanup 3. SRX was not received but got a group clean up 4. SRX was not received and group clean up was not received The main thing to remember is that ISY does not use group commands to activate scenes so group cleanups should only be seen during Scene Test. With kind regards, Michel

Hello DirkM, Also, please right mouse click on your scene, and then choose Scene Test. If you see bunch of failed messages, then: If you have any SwitchLinc v35s in your installation, then they are the culprits. Otherwise, as oberkc suggested, it might be noise/signal issue. With kind regards, Michel

Hello vislman, If you do not see rain rate and rain today values in the station's main page for WeatherBug, then, in all likelihood, that station does not provide that information and hence WB would be quite useless. You can always try WB module for 30 days and then return it if it does not meet your needs. With kind regards, Michel

Hello eximer168, The only thing that is quite odd is that the PLM is responding with two ACKs for every command sent by ISY. What is your PLM's firmware version (Tools | Diagnostics | PLM Status/Info)? If I assume correctly, 14.20.83 is your RemoteLinc and basically ISY cannot even send any commands to it. What is happening is that the RemoteLinc itself (for some reason) is repeating the button press on button 3. Do you have more than one RemoteLinc and if so do you have the problem with both? Still the fact that you are getting two acks for each command does not look normal. With kind regards, Michel

Hello Andy, Not out yet ... we are hoping to have it out by the end of the week or beginning of next week. Currently testing and adding more features. With kind regards, Michel

Hello eximer168, It would be best to look at your logs (instead of event viewer) to see whether or not ISY is turning something on/off. If you are looking at event viewer: 1. If you see INST-ACK followed by INST-SRX preceding every DON below, then ISY is sending the command (highly unlikely for an RL) 2. If you only see an INST-SRX prior to a DON, then the signal is coming from the device and ISY is not in the middle (just reporting it) With kind regards, Michel