Candide

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.

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...

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 ...

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...

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.

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 ...

It's not working right with the 2420M Motion detector. Dusk-Dawn is being set multiple times and motion-off does not seem to be processed. I'll try reverting to 2.7.15 for now. Thanks...

Upgraded to 2.8.3 from 2.7.15 - so far so good. I'll let you know how the Motion Detector actions are after a couple days/nights. Thanks...

Sure, that's no problem, thanks for the reply. It seems to work correctly on 2.7.15 Also, the 2420 is set to only trigger motion when dark and is running on a 9v transformer (no battery) and the jumper "to allow it to be managed" (jumper 5) is not set. Thanks...

I just tried it again - upgrading from 2.7.15 to 2.8.2 - and the same thing happens. The ISY logs show that thge desk/dawn setting is being triggered at the same time as motion. When I drop back to 2.7.15 everything is normal. Are there any steps I can take to troubleshoot this? Thanks...

I upgraded to 2.8.2, from 2.7.15 and all appeared to be fine. Programs ran and all devices functioned - except a Motion Detector (2420M). Dusk was not reported properly, read 'off' when dark. Dusk was also triggered simultaneously with any detected motion, when dark. I have reverted to 2.7.15 and, so far, it is functioning as it should. I will let it go for a couple days and see how it goes, but 2.7.15 was functioning properly for a long time.

Upgraded ISY 99 pro from 2.7.13 - no issues, so far all is good.

Upgraded from 2.7.11 - no issues, all statuses OK so far.

I upgraded from 2.7.6 to 2.7.9 and so far it seems good. Programs run fine. I have noticed that sometimes when I enter back into the admin console the mouse cursor is a hourglass - but clicking still works. One error I get is when setting LED Brightness from the Main tab i get "request failed" all the time on every button (KPL 2486). Also, in the programs details tab, when accessing a KPL button under "action" there are two numbers listed "On 0/ Off 0" to "On 15 / Off 7" - what do these numbers represent, the controlled device level and the LED level ? Thanks ...

I upgraded to 2.7.7 alpha and the Excel export works now, and the text export also works - thanks.

I am also running Win7 64 Ultimate, Excel 2007 Sp2 - but ISY firmware 2.7.6. How have your experiences been with the alpha code, stable? Interestingly the text file UDReport.txt is in my temp folder (c:\temp, when I do the excel export) - with all the data. I can open it in an editor or Excel, just the export to Excel fails. If I do a direct export to a text file it fails with a file length of zero.

Thanks for the suggestion, I enabled macros and can now see the log data in XP - Excel 2007. In Win 7 there is an error: Run time 1004 UDReport.txt could not be found...

Michel - Thanks for the reply. Perhaps I said it un-clearly. When I export to a text file the length is zero with no data. When I export to excel I see the drop downs for the columns, but there is no data. If I telnet into the device and look in the log folder there are three logs - with lengths about 1MB (1046528) or 620KB (619264). I have one machine with Windows 7 and a laptop with XP. As I said I am looking to review overnight events to see what events are happening with the motion detector (and other devices). Thank you,

I have added a motion detector to my devices and want to see what events happen overnight (without staying up). The event viewer provides "realtime" info - but doesn't record. When I go to export the log files they are always empty - zero bytes. Is there a way to record the events so I can look at them in the morning? Am I missing something with the logs, because they are always empty? Thanks...

The IP address was/is the same. I deleted and reentered the exception in the Trend console, for inbound and outbound traffic (for that specific address) and it is now working as it was. I can update and save properly. Thanks for the reply.

I noticed that my Anti Virus program (Trend Micro) prevents the newer versions of the ISY from saving programs. I have tried this with versions 2.6.12 and 2.6.13 . Previously 2.6.7 was able to save with Trend loaded. If I try to modify or create a program with Trend loaded it will not save. It does delete the program - it just does not write the updated version. As soon as I unload Trend the ISY program can be saved, updated, etc. Are there any ports of exceptions that can be entered into Trend to allow the ISY software to save? I am using an ISY 99i pro and software 2.6.13 currently. Thanks...

I had downloaded the file with a different name - Insteon.2.6.5.Zip. The upgrade worked after I renamed it back to just Insteon.zip.

I am unable to upgrade to 2.6.6 (from 2.6.4). I get the "upgrade failed" message about incompatible file type. This also happens when I open admin console with the suggested link: http://www.universal-devices.com/27 I cleared my Java cache and unloaded my AV program - just to be sure. Any suggestions or other actions I can try?

Thanks for the post - I had reset each of the RL's numerous times, full reset as well as individual button resets. I had also tried moving the 2443 AP's to different outlets - with no luck. Today I moved the PLM and ISY to another outlet - and that also did not change anything. I am migrating to Insteon from X-10 and still have a few X-10 devices left, like ApplianceLincs and Lamplincs. The ISY supports these and I have a couple of these X-10 devices programmed in to it. I also I was using a 4827 BoosterLinc - for better X-10 signal transmission over both phase legs of my electrical system. I read that some older X-10 BoosterLinc's interefered with Insteon - specifically version 2.0 and 2.5. I have version 3.0. According to SmartHome rev 3.0 of the 4827 "Does not interfere with INSTEON signals" As soon as I removed the 4827 the problems with the RL's stopped. I verified this by plugging it back in and removing it again (permanently). This has been a long and frustrating issue - but I believe it has been resolved once and for all. Thanks to all for posting here and trying to help, it is appreciated. ----------------- Separately - a question: Do the 2443 Insteon AP's communicate over the power line or only on RF?

I moved each access point twice to other outlets, using the proper linking process. This did not change anything. I had also been corresponding with Smarthome and have received a new replacement RL. I removed one existing RL, linked in the new replacement and set all the buttons to the same scenes as the original. The new RL is working fine - with no flashes. The existing second RL still has the rapid flashing. I have tried to count the flashes and it appears to vary. There is the delay one flash, delay 10-15 flash sequence. There also is a straight quick-flash sequence - that varies between about 13 and 20 quick flashes. I think this rules out a device communications problem - unless it is with the second RL itself. I also turned off nearly everything in the house - fans, lights etc. but that had no effect on the flashing. My next test will be to remove the second RL and completely re-link it. Stay tuned...