Michel Kohanim Posted October 9, 2010 Author Share Posted October 9, 2010 Hello silverton38, Thanks so very much for your assistance. It's indeed appreciated. Would you be kind enough to go to Program Summary tab and check for any programs that are currenlty Running? If there are any, plase try and stop them and let me know if that helps the issue. Furthermore, please go to Tools | Diagnostics | Event Viewer on Level 3 and let me know if you see anything. Thanks again and with kind regards, Michel Quote Link to comment Share on other sites More sharing options...
silverton38 Posted October 9, 2010 Share Posted October 9, 2010 Will do. Just in case it matters the PLM Info/Status is F.9C.23 v92 / Connected. It took a long time for the ISY to spit that out. Quote Link to comment Share on other sites More sharing options...
nowandthen Posted October 9, 2010 Share Posted October 9, 2010 Michel, I'm looking forward to you getting that nasty bug out of 2.8.3. Control of the 2420M motion sensor via the ISY is a feature set I have been looking forward to. I've spent many hours fussing with that darn 2420M. Many grumblings by me on this site, certainly not any fault of the ISY. I am thrilled that you're coming to the rescue for those of us looking for decent functionality out of the 2420M. Occupancy sensing will keep my outdoor lights on as I move around. LOVE IT! Todd Quote Link to comment Share on other sites More sharing options...
silverton38 Posted October 9, 2010 Share Posted October 9, 2010 I tried to disable all of my programs. The act of disable is either delayed or not working. The event viewer does not come up when requested; it may also be delayed; I will check in a few minutes. Quote Link to comment Share on other sites More sharing options...
Sub-Routine Posted October 9, 2010 Share Posted October 9, 2010 Hello silverton38, Please be sure to close the Admin Console and ALL browser windows before you ISY-99i/ISY-26_INSTEON:Clearing_Your_Java_Cache. With a MAC you may also have to reboot. Next step is to check your Java preferences to be sure the 64-bit version is the first listed. Rand I tried to disable all of my programs. The act of disable is either delayed or not working.The event viewer does not come up when requested; it may also be delayed; I will check in a few minutes. Quote Link to comment Share on other sites More sharing options...
Sub-Routine Posted October 9, 2010 Share Posted October 9, 2010 Hi Todd, Thank you for your support, we are actively working on better support for the motion sensor. Rand Michel, I'm looking forward to you getting that nasty bug out of 2.8.3. Control of the 2420M motion sensor via the ISY is a feature set I have been looking forward to. I've spent many hours fussing with that darn 2420M. Many grumblings by me on this site, certainly not any fault of the ISY. I am thrilled that you're coming to the rescue for those of us looking for decent functionality out of the 2420M. Occupancy sensing will keep my outdoor lights on as I move around. LOVE IT! Todd Quote Link to comment Share on other sites More sharing options...
silverton38 Posted October 9, 2010 Share Posted October 9, 2010 I made sure the caches were clear. I cleared them and rebooted the computer. I have reverted back to 2.7.15 for now. I will gladly upgrade and allow remote access in if you would like to see what might be wrong. I have about 100+ Insteon devices; maybe that is a factor. Anyway; it is bedtime for me. until tomorrow. Quote Link to comment Share on other sites More sharing options...
Sub-Routine Posted October 9, 2010 Share Posted October 9, 2010 Thank you so much. Rand I made sure the caches were clear. I cleared them and rebooted the computer. I have reverted back to 2.7.15 for now. I will gladly upgrade and allow remote access in if you would like to see what might be wrong. I have about 100+ Insteon devices; maybe that is a factor. Anyway; it is bedtime for me. until tomorrow. Quote Link to comment Share on other sites More sharing options...
TJF1960 Posted October 10, 2010 Share Posted October 10, 2010 I just wanted to give some further feedback since reverting back to 2.8.2. After factory resetting the ISY and doing a plm restore things seemed to be back to normal. But as a couple of days progressed some kpl buttons were lighting up when they shouldn't and some devices were controlling other devices when they shouldn't. And some devices weren't reporting their status to the ISY (or the ISY wasn't listening). Yesterday I restored all devices. So far all has been well, its been about 18 hours so far. Being back to 99.9% is a good feeling! Based on another thread I read, is it looking like those of us with older plm's are the only ones not able to upgrade? Thanks, Tim Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted October 10, 2010 Author Share Posted October 10, 2010 Hi Tim, Thank so very much for the update. I am not yet sure what the root cause is but most of the reports are related to communications issues. And, in 2.8.3, we added some safeguard mechanisms to reduce the risk of device database corruption which basically prevents one task from taking over while the PLM communications module is talking to the PLM. So, in short, if there are many communication errors (as it seems the case is for all involved), ISY does not let other tasks run that might require datbase access and thus all the slow and intermittent access issues. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Brian H Posted October 10, 2010 Share Posted October 10, 2010 For some reason today. It again asked me to accept the end users agreement. It never asked when I updated from 2.8.2 and it was running with no questions from day one of the update. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted October 10, 2010 Author Share Posted October 10, 2010 Hi Brian, I think these are all related to the fact that in 2.8.3, ISY prevents other tasks from running in case the database is locked. 2.8.4 should be out shortly. With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted October 10, 2010 Author Share Posted October 10, 2010 Hello all, For those with issues relating to 2.8.3, please do be kind enough to try 2.8.4: http://forum.universal-devices.com/view ... 8822#38822 With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Candide Posted October 11, 2010 Share Posted October 11, 2010 I did some testing and the 2420M is working better, with 2.8.3, comparable to what I was seeing with 2.7.15 . Dusk-Dawn is still being triggered multiple times on my network, even when "fully" dark, but motion detection only-when-dark seems to be working well. One question, should the "manage by" jumper (#5) be set on to allow the ISY to control all settings - such as darkness sensitivity, time delay to send motion-off, etc. ? For instance is the LED flashing setting (jumper #2) setting controllable when jumper #5 is on? Thanks ... Hi Todd, Thank you for your support, we are actively working on better support for the motion sensor. Rand Michel, I'm looking forward to you getting that nasty bug out of 2.8.3. Control of the 2420M motion sensor via the ISY is a feature set I have been looking forward to. I've spent many hours fussing with that darn 2420M. Many grumblings by me on this site, certainly not any fault of the ISY. I am thrilled that you're coming to the rescue for those of us looking for decent functionality out of the 2420M. Occupancy sensing will keep my outdoor lights on as I move around. LOVE IT! Todd Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Except for the Motion Sensor Sensitivity which is controlled by Jumper 1 in all cases, each Jumper function can be controlled through software/firmware when Jumper 5 is installed. Whether you use the Jumpers/Pots and do it manually or software/firmware is user choice. Personally I think it is much easier to do it with the ISY than do it manually. As far as LED intensity (Jumper 2) software/firmware can set the LED brightness across a range. The Jumper 2 is only Enabled or Disabled The following link will get to a detailed explanation. http://forum.universal-devices.com/viewtopic.php?t=5184 I suggest running the Event Viewer in Change level 3 and see what the Motion Sensor is sending at the transition from Dark to Light. All the V2 Motion Sensors I have tested send multiple On/Off commands with motion. Not sure about Dark Only commands. Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Just tested Night Only mode. My V2 Motion Sensor sends multiple Dark messages for Group 2 just as it does for motion using Group 1. Running 2.8.4. Sun 10/10/2010 09:01:47 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.02 C7 11 02 LTONRR (02) Sun 10/10/2010 09:01:47 PM : [standard-Group][13.F2.57-->Group=2] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:01:47 PM : [ 13 F2 57 2] DON 2 Sun 10/10/2010 09:01:47 PM : [ 13 F2 57 2] ST 255 Sun 10/10/2010 09:01:47 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.02 C7 11 02 LTONRR (02) Sun 10/10/2010 09:01:47 PM : [standard-Group][13.F2.57-->Group=2] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:01:47 PM : Duplicate: ignored Sun 10/10/2010 09:01:47 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.02 C7 11 02 LTONRR (02): Process Message: failed Sun 10/10/2010 09:01:47 PM : [standard-Group][13.F2.57-->Group=2] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:01:47 PM : [iNST-SRX ] 02 50 13.F2.57 12.9F.E4 41 11 02 LTONRR (02) Sun 10/10/2010 09:01:47 PM : [standard-Cleanup][13.F2.57-->ISY/PLM Group=2] Max Hops=1, Hops Left=0 Sun 10/10/2010 09:02:09 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 C7 11 01 LTONRR (01) Sun 10/10/2010 09:02:09 PM : [standard-Group][13.F2.57-->Group=1] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:02:09 PM : [ 13 F2 57 1] DON 1 Sun 10/10/2010 09:02:09 PM : [ 13 F2 57 1] ST 255 Sun 10/10/2010 09:02:09 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 C7 11 01 LTONRR (01) Sun 10/10/2010 09:02:09 PM : [standard-Group][13.F2.57-->Group=1] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:02:09 PM : Duplicate: ignored Sun 10/10/2010 09:02:09 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Sun 10/10/2010 09:02:09 PM : [standard-Group][13.F2.57-->Group=1] Max Hops=3, Hops Left=1 Sun 10/10/2010 09:02:10 PM : [iNST-SRX ] 02 50 13.F2.57 12.9F.E4 41 11 01 LTONRR (01) Sun 10/10/2010 09:02:10 PM : [standard-Cleanup][13.F2.57-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Quote Link to comment Share on other sites More sharing options...
Candide Posted October 11, 2010 Share Posted October 11, 2010 LeeG - Thanks for the reply. Right now I have the 2420 jumper 5 off - I'll try setting it on tomorrow and doing full ISY control. Can you please explain what the difference is between Group 2 and Group 1 messages? Can I see these on the log or do I need to do the event viewer? I have an email alert sent when dusk is triggered and that has been happening multiple times. I will try 2.8.4 to test. Just tested Night Only mode. My V2 Motion Sensor sends multiple Dark messages for Group 2 just as it does for motion using Group 1. Running 2.8.4. ... Sun 10/10/2010 09:02:10 PM : [standard-Cleanup][13.F2.57-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Candide Sorry, Group 1 messages in the Event Viewer represent Motion On/Off. Group 2 messages represent Dusk On/Off. You can see the high level result in the Log. Motion Sensor - 2-Sensor / Motion Sensor - 2-Dusk/Dawn Status 0% Sun 2010/10/10 08:34:36 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 08:45:59 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 08:46:29 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 08:51:02 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 08:51:11 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 08:52:09 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 08:52:11 PM System Log Scene:Scene3 On 255 Sun 2010/10/10 08:58:01 PM Program Log Motion Sensor - 2-Sensor / Motion Sensor - 2-Dusk/Dawn Status 100% Sun 2010/10/10 09:01:47 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 09:02:10 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 09:02:39 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 09:06:37 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 09:07:07 PM System Log Motion Sensor - 2-Sensor Status 100% Sun 2010/10/10 09:15:18 PM System Log Motion Sensor - 2-Sensor Status 0% Sun 2010/10/10 09:15:48 PM System Log If the Log shows something different on your system then the Event Viewer messages should explain why. Not needed if the Logs are similar. Lee Quote Link to comment Share on other sites More sharing options...
Candide Posted October 11, 2010 Share Posted October 11, 2010 LeeG - The past few days Dusk-Dawn has been triggered two or three times. On 2.8.1 it seemed to trigger Dusk-Dawn whenever motion was detected. My log for the past 2 days: BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 06:53:08 AM System BD-Sensor / BD-Dusk/Dawn Status 100% Sat 2010/10/09 06:26:21 PM System BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 06:41:18 PM System BD-Sensor / BD-Dusk/Dawn Status Query Sat 2010/10/09 07:26:32 PM System BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 07:30:57 PM System BD-Sensor / BD-Dusk/Dawn Status 100% Sat 2010/10/09 08:27:29 PM System BD-Sensor / BD-Dusk/Dawn Status 0% Sun 2010/10/10 06:53:21 AM System BD-Sensor / BD-Dusk/Dawn Status 100% Sun 2010/10/10 06:24:52 PM System BD-Sensor / BD-Dusk/Dawn Status 0% Sun 2010/10/10 06:37:37 PM System BD-Sensor / BD-Dusk/Dawn Status 100% Sun 2010/10/10 06:42:42 PM System BD-Sensor / BD-Dusk/Dawn Status Query Sun 2010/10/10 09:54:50 PM System Thanks again... Candide Sorry, Group 1 messages in the Event Viewer represent Motion On/Off. Group 2 messages represent Dusk On/Off. You can see the high level result in the Log. Motion Sensor - 2-Sensor / Motion Sensor - 2-Dusk/Dawn Status 0% Sun 2010/10/10 08:34:36 PM System Log ... If the Log shows something different on your system then the Event Viewer messages should explain why. Not needed if the Logs are similar. Lee Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Candide Remember when Jumper 5 is installed the pot that was being used to set the Dusk/Dawn transition point (Dark) is no longer being used. The number specified in the Darkness Sensitivity field will be the controlling factor. Specifying a value that is not Dark enough could cause the MS to cycle between Night and Day if the Night indication is turning on some outside lights that are increasing the light level around the MS or the general lighting in the area does not stay Dark enough. BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 06:53:08 AM System – MORNING BD-Sensor / BD-Dusk/Dawn Status 100% Sat 2010/10/09 06:26:21 PM System – FIRST DARK BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 06:41:18 PM System – BACK TO LIGHT BD-Sensor / BD-Dusk/Dawn Status Query Sat 2010/10/09 07:26:32 PM System BD-Sensor / BD-Dusk/Dawn Status 0% Sat 2010/10/09 07:30:57 PM System – 2nd LIGHT BD-Sensor / BD-Dusk/Dawn Status 100% Sat 2010/10/09 08:27:29 PM System – 2nd DARK BD-Sensor / BD-Dusk/Dawn Status 0% Sun 2010/10/10 06:53:21 AM System – MORNING BD-Sensor / BD-Dusk/Dawn Status 100% Sun 2010/10/10 06:24:52 PM System – FIRST DARK BD-Sensor / BD-Dusk/Dawn Status 0% Sun 2010/10/10 06:37:37 PM System – BACK TO LIGHT BD-Sensor / BD-Dusk/Dawn Status 100% Sun 2010/10/10 06:42:42 PM System – 2ND DARK BD-Sensor / BD-Dusk/Dawn Status Query Sun 2010/10/10 09:54:50 PM System Was this Log with Jumper 5 removed or in place? There is no motion indicated in the Log. Lee Quote Link to comment Share on other sites More sharing options...
Candide Posted October 11, 2010 Share Posted October 11, 2010 This log is with jumper 5 OFF - local settings no ISY control. I only sent the dusk-dawn settings from a sorted log in excel, there were many (hundreds) of other messages over several days. I can post more if it would be helpful. I usually clear the log on each new firmware update. There are no lights near the 2420 - except the one it controls - but this had been working well before, as with 2.7.15. I do not think interference is the cause here. I will set jumper 5 ON tonight and control with the ISY, including the DUSK setting. I also updated to 2.8.4 last night, so I will hope for the best. Thanks ... Candide Remember when Jumper 5 is installed the pot that was being used to set the Dusk/Dawn transition point (Dark) is no longer being used. The number specified in the Darkness Sensitivity field will be the controlling factor. Specifying a value that is not Dark enough could cause the MS to cycle between Night and Day if the Night indication is turning on some outside lights that are increasing the light level around the MS or the general lighting in the area does not stay Dark enough. Was this Log with Jumper 5 removed or in place? There is no motion indicated in the Log. Lee Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Candide Thanks for the update. Having mined the Log makes perfect sense. Assuming the Motion Sensor cycles the Dusk/Dawn indication look for something in the Log that happens approximately 3.5 minutes before it goes from Dusk to Dawn (MS signals an Off for Group 2). The Dusk (Night) message will change nearly every day as the sun angle lowers. This can put the sun in more direct contact with the MS but also can cause trees to block the sun earlier. If it is an Insteon device coming on affecting the ambient light around the MS it takes approx 3.5 minutes for the MS to issue the change in light level indication. They do this so the MS does not cycle every time a car drives by etc. Particularly being wireless and going to sleep shortly after each motion is sensed it is not likely a direct command to the MS as the RF circuitry is not on to receive any communication from the ISY or any other device for that matter. Lee Quote Link to comment Share on other sites More sharing options...
LeeG Posted October 11, 2010 Share Posted October 11, 2010 Candide When you get the email indicating the MS has signaled Dark turn on the Event Viewer with Change Level 3. That way if the MS does go back to Light we will have the actual commands (if any) the motion sensor sent at the time. Lee Quote Link to comment Share on other sites More sharing options...
Candide Posted October 11, 2010 Share Posted October 11, 2010 Thanks for the info and possible troubleshooting steps. So far only one Dusk-on has been sent. I'll leave level 3 up and see what happens from here. I set jumper 5 on, set the timeout to 2.5 minutes, night only, On and Off sent, LED brightness low (11) and darkness for 128 (perhaps a bit too light ?). Are there any rough guidelines or experience with the darkness numbers - I do not need the light on if it is "light enough" to see... I appreciate all the assistance... Candide When you get the email indicating the MS has signaled Dark turn on the Event Viewer with Change Level 3. That way if the MS does go back to Light we will have the actual commands (if any) the motion sensor sent at the time. Lee Quote Link to comment Share on other sites More sharing options...
Candide Posted October 12, 2010 Share Posted October 12, 2010 Another evening and the motion detector is working 100% - one dusk event and all motion events processed properly. Looks good! =============================== Last night was good - only one Dusk-Dawn and all motion detections worked as they should have. Maybe 2.8.4 is the charm... I'll give it a couple more days to observe and will update status here. Quote Link to comment Share on other sites More sharing options...
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.