Michel Kohanim

Hi Brian, Thanks so very much. This will be the only test necessary to figure out if the problem is with configuration or hardware. In the meantime, if you have not factory reset yet, would you be kind enough to send us your error logs (support@universal-devices.com). Thanks and with kind regards, Michel

Hello ssingh1234, Unfortunately I am out of ideas except: 1. Please factory reset the one that used to work when you used option 1 2. Make sure you are within a range of an access point 3. The actual door lock is close to ML With kind regards, Michel

Hello Brian, 1. Do you have self signed certificates? 2. If you have a good backup, please factory reset your ISY and then let me know if it stays up 3. If it does, please go to Tools | Diagnostics | PLM Status/Info and let me know what you see With kind regards, Michel

Hello thruster999, What's your ISY's firmware version? Also, when this happens, you do not get any status updates back from the motion sensors in the Event Viewer or do you? Do you get any green 0101 icons next to any of your devices when this happens? With kind regards, Michel

Hello ssingh1234, Just to be certain, did you follow the instructions here: http://www.universal-devices.com/mwiki/ ... orningLinc ? It's very important that you choose the 3rd option otherwise everything will be removed. With kind regards, Michel

Hello rossarmstrong, Evapotranspiration was added to our 3.1.3 release to be out shortly. The accuracy depends on the averages of temperature and humidity as provided by WeatherBug. Testing was minimal since we really do not know the points of reference except those freely available on the Internet. With kind regards, Michel

Hello cashoefman, Thank so very much for your contribution! With kind regards, Michel

Hello thruster999, On level/ramp rates/scene activations are all stored in devices themselves and ISY is bypassed for those types of scenarios. So, no, ISY is not the problem here. The problem is that the responder or the controller in that scene are losing their links and therefore do not communicate with one another properly. If the problem is isolated only to scenes with motion sensors, I strongly advise against restoring EVERYTHING for two reasons: 1. Now, we do not know which one of your devices were causing the problem 2. Restoring things that do not need to be restored is a waste of our valuable time So, if this happens again: 1. Restore the responder (KPL or SWL or whatever device responds to your motion sensor or the scene in ISY). If this works, then the problem is the responder 2. Restore the controller (i.e. the motion sensor). If this works, then the problem is the motion sensor 3. If the problem is that on level/ramp rates for a specific scene when activated from ISY are lost, then restore the PLM. if this fixes the problem then the issue is a defective PLM With kind regards, Michel

j0dan, Perhaps but this will go to the core networking and quite abrasive when it comes to regression testing. What are you trying to communicate with? With kind regards, Michel

Hi j0dan, DNS resolution requests are not thread safe and therefore, we put a lock around it and thus the delay. So, you should see a variable amount of delay depending on what other network activity/operation ISY is currently performing. With kind regards, Michel

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