Michel Kohanim Posted January 12, 2011 Author Posted January 12, 2011 jwagner010, Thank YOU. We reproduced and fixed the problem! It should be available in the next release shortly. With kind regards, Michel Quote
Moshe Posted January 12, 2011 Posted January 12, 2011 Michel - I checked all of my Insteon devices and none of them are v 35. Quote
Moshe Posted January 13, 2011 Posted January 13, 2011 Michel - Why would the scene test show failed on some of the devices even though they worked correctly. Quote
Brian H Posted January 13, 2011 Posted January 13, 2011 A scene test is the worst case test. It sets the hop count to one. I believe three hops is normal. So a scene test can fail and the scene may still work with normal commands. The test shows marginal communications that can slow things down or why a module may sometimes miss a command. Quote
Moshe Posted January 13, 2011 Posted January 13, 2011 Brian H - So in the above scene test that shows that most things failed, how is it a help to me to pinpoint the real problem. Thanks Quote
Sub-Routine Posted January 13, 2011 Posted January 13, 2011 If most of the Failed devices are on the same circuit then you can search for a device on that circuit that is creating an issue. Rand Quote
bocaray Posted January 15, 2011 Posted January 15, 2011 How do I remove the 'write' symbol from some of the devices??? Quote
Brian H Posted January 15, 2011 Posted January 15, 2011 Do you have the Pro Version? You can delay automatic writes and automatic battery device writes with the Pro version. Quote
bocaray Posted January 16, 2011 Posted January 16, 2011 Yes, have Pro version. Please explain "delay automatic writes"??? Quote
bocaray Posted January 16, 2011 Posted January 16, 2011 Found it! Discovered the "Write updates to device" command. Duh... Quote
Teken Posted January 16, 2011 Posted January 16, 2011 A scene test is the worst case test.It sets the hop count to one. I believe three hops is normal. So a scene test can fail and the scene may still work with normal commands. The test shows marginal communications that can slow things down or why a module may sometimes miss a command. Brian, I was not aware this was how the scene tests was intended and operates. This would explain why sometimes a scene would fail when I was doing some testing, yet the activation of the scene operated normally. I am not sure if this has ever been covered or explained before. But, I would like to thank you once again for all the information and insight. This is why having these discussions are so important . . . Quote
Moshe Posted January 16, 2011 Posted January 16, 2011 Brian - The switches are on different circuits. This problem started when I upgraded to 2.8.10. After I turn off the current breaker one at a time to each of the three switches the problem still exists. ( The scene intermittently does not work on one of the switches.) Quote
Michel Kohanim Posted January 17, 2011 Author Posted January 17, 2011 Hello Moshe, I have to be clear here since there's absolutely no correlation between 2.8.10 and "some" devices in "some" scenes not responding. ISY does not at all distinguish between sending a command to scene A or scene B. What you might want to try is to disable all your programs and see if this helps the issue. If it does, then you have a program that is causing a conflict. With kind regards, Michel Quote
bocaray Posted January 17, 2011 Posted January 17, 2011 Guys, My Thermostat Adapter displays the set temp value correctly but the Unit of Measure is says Centigrade "©" not Fahrenheit “(F)â€? Is this an error or do I need to configure something different (re-install)? FYI: I don't know why but every few weeks I lose communication with it and I am forced to re-install it??? Quote
ficklma1 Posted January 17, 2011 Posted January 17, 2011 I too am having strange Thermostat behavior with 2.8.10. I'm seeing that sometimes logging into the admin console the Thermostats status screens have no information and manually quering them doesn't refresh the screen. I have to log out of the admin console and log back in. Is anyone else seeing this? Quote
ficklma1 Posted January 17, 2011 Posted January 17, 2011 I've read through this post and I'm seeing similar issues that Moshe is seeing. Prior to upgrading to 2.8.10, I was on the last official release and didn't notice any of the random communication issues that I'm seeing now. I posted some of my findings in this post http://forum.universal-devices.com/viewtopic.php?t=5705 Any ideas on how to track down what could be causing these issues? I've already disabled programs, etc. If this helps, I did notice that I had to completely remove and add back one of my KPL's in the admin tool, this seemed to have cleaned up communication issues I was see with that one device. Thanks in advance for your help. Quote
Michel Kohanim Posted January 17, 2011 Author Posted January 17, 2011 Hello bocaray, Where do you see C instead of F? ficklma1, If the REST interface becomes slow or stops working that's a known issue. If you have communications errors with one or more of your devices, first we have to figure out whether or not the problem is scene related or device related. i.e. do you have the same problem when you query the devices. If you do not have status present in the Admin Console, this points to firewall issues. Would you be kind enough to make sure that ISY is in the trusted/white zone of your firewall. Please note that disabling firewall does NOT help this situation. With kind regards, Michel Quote
Moshe Posted January 17, 2011 Posted January 17, 2011 Michel - I will disable the programs and see what happens. Thanks Quote
Moshe Posted January 17, 2011 Posted January 17, 2011 Michel - I disabled the programs that you suggested, and you are correct. Two of my programs were conflicting with my scene. When I disable the programs the scene test works perfectly 100% of the time. I have been using these programs for over 6 months. Why do you think the problem showed up now? Thanks again Quote
mlennox Posted January 17, 2011 Posted January 17, 2011 I'm having a weird problem with one of my motion sensors and/or programs that may coincide with the recent firmware upgrade, or may not. Just looking for direction. I have a program that sends an e-mail notice to me when a motion sensor is triggered on. I have the motion sensor set for a 30 second timeout and nothing has changed on the sensor side of things. What's happening is that after motion is sensed, I'm getting spammed for about 10-15 minutes (every minute) with an email alert even after all motion has stopped. Quote
Michel Kohanim Posted January 18, 2011 Author Posted January 18, 2011 Moshe, Scene Test in previous versions did not turn on the scene before doing the test. This could explain the scene test issue but this does not explain why your programs do not run. mlennox, Please post your program here. With kind regards, Michel Quote
mlennox Posted January 18, 2011 Posted January 18, 2011 Hi Michel, I think it was just a coincidence. I opened up the motion sensor and found that the battery terminal connection was very loose. I squeezed it tighter, reset and re-linked the device to ISY and now it seems to be operating properly... I'm guessing the cold temperatures in the garage may have made for a loose connection to the battery... I'll keep an eye on it and see what happens. Quote
RLIKWARTZ Posted January 23, 2011 Posted January 23, 2011 I've noticed that if you run a program from the program summary when it's true the start time is about 30 seconds ahead of the time at the top of the screen. Quote
Michel Kohanim Posted January 23, 2011 Author Posted January 23, 2011 RLIKWARTZ, How long has the Admin Console been up when you do the test? In all cases, the time on the program summary is MUCH more accurate than the time on top of the Admin Console. With kind regards, Michel Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.