New AHP Version 3.296 Released 11/06/2010

[phongluu]

I have about 20 sensors: half of them giving me trouble.
Do I really have to re-install all and test each to make sure no more M MTCDDVD?

I'm gonna do it one by one, starting by most critical....yet, is there a fix?

Thanks,
P.L

[ErikP]

I didn't actually delete the module from AHP as far as I remember.

The method you used should also work, though I did not test it myself.  As long as the corrupted security code entry gets overwritten with a correct value is the important part.

I'm gonna do it one by one, starting by most critical....yet, is there a fix?

Unfortunately no  .  The corruption is just incorrect security codes being stored for some modules.  The codes are valid, just not correct.  There is no way the software can know what code is correct other than you telling it what is correct, which is what re-adding the module or changing the security code does.

[phongluu]

Ok, tried to reinstall few sensors and ran for a day. They are still giving a lot of M and (perhaps) misfire Macros again last night. Dawn it!
Was previous version better? Or I don't recall seeing a lot of M craps in the even log and misfire the macro to send me txt msg in middle of the night!

P.L

[phongluu]

I beleive that this version also has bug with Dusk and Dawn timer.
None of my Timer trigger after the clock change last weekend.

Also, would anyone looking into the bug where sensor NOT triggering a macro with conditon, please? (Email using Onalert)

P.L

[ErikP]

They are still giving a lot of M and (perhaps) misfire Macros again last night.

There does appear to be some M MTCDDVD commands appearing in the log still.  It is extremely rare in the test systems however (twice in almost a week of running multiple systems) so it will probably take some time to track down the cause on my end.  Any information you can give me will help me find the bug

Is there a pattern when you see these in your log?  For example do you still see them every time certain door/window sensors are triggered?

Does the M MTCDDVD have a time stamp after the entry below it, or before the entry above it?

I believe that this version also has bug with Dusk and Dawn timer.
None of my Timer trigger after the clock change last weekend.

There was an old bug where if the system time was changed back in time, such as falling back, it would mess up the timers for a bit.  Restarting the X10net service and re-syncing the hardware was a workaround for this at the time.  This should have been fixed, but I will take a look at it and make sure it didn't get broken again somehow.

Also, would anyone looking into the bug where sensor NOT triggering a macro with condition, please? (Email using Onalert)

This appears to be working on all my test systems.  Can you send me a copy of your ahx file, or post an image of your macro that’s not working in the editor?

[Tuicemen]

I to see M MTCDDVD commands which seem to be right after  a particular security motion sensor trips or resets.
I replaced the batteries and the signals stopped occurring but now I'm getting them after a different sensor (Not a motion sensor) I thought these modules were suppose to show in AHP when batteries were failing?

Is the check for new release fixed with this version? (not working since 3.228)

Update to interface fails from the hardware configuration screen.

[anthonylavado]

I thought these modules were suppose to show in AHP when batteries were failing?

In my short experience with X10 (1.5 months), that is still the case. The M MTCDVD commands are unrelated (as seen in other threads and posts by Erik P and AHP Dev).

Is the check for new release fixed with this version? (not working since 3.228)

Still not working (as far as we know). The updates have been consolidated, so you only need to download the ActiveHome Pro file from the Support site, and it will update all the plug-ins you have at the same time. The separate installers are only if you're adding a plug-in for the first time.

Update to interface fails from the hardware configuration screen.

Haven't run into that yet. CM15A?

[mike]

M MTCDDVD here seems random - could be after a security sensor triggered, but definitely comes 1 sec to 20 MINUTES after it.... so I question it totally coming from DS10s here,

My emailing text to cellphone after DS10 trigger AND if FLAG 1 ON has been working since like 3.27x so not sure why some folks dont.  Unless your condition is DUSK, dawn,day, nite - they havent worked for me for a couple years;  why I set/clear flag 1 based on timer of a lite sw instead.

[kevinwheeler]

This is what I see for the MTCDDVD entries - here is a short sample of a log riddled with them and the A 00TV codes. They are almost always around door sensor or motion sensor events. If it matters, besides the CM15A, CM19A, and VA12A for video, I have an RR501 near the computer, a TM751 a floor up from the computer, an SR731 in the house near the TM751 and an XPCR in a circuit box next to the main breaker box bridging the two legs of my electric service.

734    11/15/2010 9:45:54 PM    Receive RF    M MTCDDVD
735    11/15/2010 9:45:54 PM    Receive RF    A 00TV
736    11/15/2010 9:45:54 PM    Receive RF    M MTCDDVD
737    11/15/2010 9:45:54 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
738    11/15/2010 9:45:54 PM    Receive RF    A 00TV
739    11/15/2010 9:45:54 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
740    11/15/2010 9:45:54 PM    Receive RF    A 00TV
741    11/15/2010 9:45:54 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
742    11/15/2010 9:45:54 PM    Receive RF    A 00TV
743    11/15/2010 9:45:54 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
744    11/15/2010 9:45:54 PM    Receive RF    A 00TV
745    11/15/2010 9:45:54 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
746    11/15/2010 9:45:54 PM    Receive RF    M MTCDDVD
747    11/15/2010 9:45:54 PM    Receive RF    M MTCDDVD
748    11/15/2010 9:45:55 PM    Receive RF    A 00TV
749    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD
750    11/15/2010 9:45:55 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
751    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD
752    11/15/2010 9:45:55 PM    Receive RF    A 00TV
753    11/15/2010 9:45:55 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
754    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD
755    11/15/2010 9:45:55 PM    Receive RF    A 00TV
756    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD
757    11/15/2010 9:45:55 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
758    11/15/2010 9:45:55 PM    Receive RF    A 00TV
759    11/15/2010 9:45:55 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
760    11/15/2010 9:45:55 PM    Receive RF    A 00TV
761    11/15/2010 9:45:55 PM    Receive RF    Bookcase MS10A #7 - Motion Reset
762    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD
763    11/15/2010 9:45:55 PM    Receive RF    M MTCDDVD

I have not removed all the security sensors and re-added them, but I will give that a try. I just don't want to generate new codes or else I have to totally reset my DS7000 and that's a pain.

Kevin

[Tuicemen]

kevinwheeler
In my case simply replacing the batteries for the sensor that was showing a status prior to the  Receive RF    M MTCDDVD signal fixed the error.
anthonylavado
the battery indicator shows when the sensor fails to send any info such as dead batteries.
in my tests the worse the batteries in the sensor the more RF    M MTCDDVD seen.
New Batteries don't always mean good ones!
Of coarse my units are all older and it may be just a fluke that it was a battery issue but when it happens more then once the chances of a fluke go down.

ErikP
One other long time bug that you may wish to look into is the windows command macro options bug.
The thing is if you create one  it works fine.
but if AHP shuts down via a PC restart or you restart AHP manually the macro will fail when AHP reopens.
However if you create another windows command  macro then all macros with a windows command work until a AHP restart.
I have a work around posted Here to get by this bug but many users are uncomfortable with writing scripts (no mater how easy)

[phongluu]

Also, would anyone looking into the bug where sensor NOT triggering a macro with condition, please? (Email using Onalert)

This appears to be working on all my test systems.  Can you send me a copy of your ahx file, or post an image of your macro that’s not working in the editor?

[/quote]

Try using a door sensor TRIGGER a macro that SENDING email with CONDITION: during business hour. It will not work.

[phongluu]

They are still giving a lot of M and (perhaps) misfire Macros again last night.

There does appear to be some M MTCDDVD commands appearing in the log still.  It is extremely rare in the test systems however (twice in almost a week of running multiple systems) so it will probably take some time to track down the cause on my end.  Any information you can give me will help me find the bug

Is there a pattern when you see these in your log?  For example do you still see them every time certain door/window sensors are triggered?
it seems like all of them giving me the M MTCDDVD even after reset it. I can send you a log if needed.
Does the M MTCDDVD have a time stamp after the entry below it, or before the entry above it?
Yes, it does.

I believe that this version also has bug with Dusk and Dawn timer.
None of my Timer trigger after the clock change last weekend.

There was an old bug where if the system time was changed back in time, such as falling back, it would mess up the timers for a bit.  Restarting the X10net service and re-syncing the hardware was a workaround for this at the time.  This should have been fixed, but I will take a look at it and make sure it didn't get broken again somehow.

I tried it : reboot comp, reset/clear/reload CM15A, still didnt work.

Also, would anyone looking into the bug where sensor NOT triggering a macro with condition, please? (Email using Onalert)

This appears to be working on all my test systems.  Can you send me a copy of your ahx file, or post an image of your macro that’s not working in the editor?

I can send you my ahx file. Email? or PM? Thanks

[phongluu]

FYI, this is within on emitute of my log:



608   11/16/2010 11:08   Receive RF   A 00TV
609   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Detected
610   11/16/2010 11:08   Receive RF   A 00TV
611   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Detected
612   11/16/2010 11:08   Receive RF   A 00TV
613   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Detected
614   11/16/2010 11:08   Receive RF   A 00TV
615   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Detected
616   11/16/2010 11:08   Transmit   E12 (F.Gara.M.Phantom)
617   11/16/2010 11:08   Transmit   E On (F.Gara.M.Phantom)
618   11/16/2010 11:08   Macro   B1 (B1.Front.Chime)
619   11/16/2010 11:08   Macro   B On (B1.Front.Chime)
620   11/16/2010 11:08   Macro   E12 (F.Gara.M.Phantom)
621   11/16/2010 11:08   Macro   E Off (F.Gara.M.Phantom)
622   11/16/2010 11:08   Macro   E12 (F.Gara.M.Phantom)
623   11/16/2010 11:08   Macro   E Off (F.Gara.M.Phantom)
624   11/16/2010 11:08   Receive RF   A 00TV
625   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Reset
626   11/16/2010 11:08   Receive RF   A 00TV
627   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Reset
628   11/16/2010 11:08   Receive RF   A 00TV
629   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Reset
630   11/16/2010 11:08   Receive RF   A 00TV
631   11/16/2010 11:08   Receive RF   16.F.Gara.Motion - Motion Reset
632   11/16/2010 11:08   Receive RF   A 00TV
633   11/16/2010 11:08   Receive RF   M MTCDDVD
634   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Triggered
635   11/16/2010 11:08   Receive RF   A 00TV
636   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Triggered
637   11/16/2010 11:08   Receive RF   A 00TV
638   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Triggered
639   11/16/2010 11:08   Receive RF   A 00TV
640   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Triggered
641   11/16/2010 11:08   Receive RF   A 00TV
642   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Triggered
643   11/16/2010 11:08   Receive RF   M MTCDDVD
644   11/16/2010 11:08   Receive RF   M MTCDDVD
645   11/16/2010 11:08   Transmit   E1 (1.F.Door.Module)
646   11/16/2010 11:08   Transmit   E On (1.F.Door.Module)
647   11/16/2010 11:08   Receive RF   A 00TV
648   11/16/2010 11:08   Receive RF   M MTCDDVD
649   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Closed
650   11/16/2010 11:08   Receive RF   A 00TV
651   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Closed
652   11/16/2010 11:08   Receive RF   A 00TV
653   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Closed
654   11/16/2010 11:08   Receive RF   A 00TV
655   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Closed
656   11/16/2010 11:08   Receive RF   A 00TV
657   11/16/2010 11:08   Receive RF   1.Front.Door - Sensor Closed
658   11/16/2010 11:08   Receive RF   M MTCDDVD
659   11/16/2010 11:08   Receive RF   M MTCDDVD
660   11/16/2010 11:08   Receive RF   A 00TV
661   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Triggered
662   11/16/2010 11:08   Receive RF   A 00TV
663   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Triggered
664   11/16/2010 11:08   Receive RF   A 00TV
665   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Triggered
666   11/16/2010 11:08   Receive RF   A 00TV
667   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Triggered
668   11/16/2010 11:08   Receive RF   A 00TV
669   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Triggered
670   11/16/2010 11:08   Transmit   E1 (1.F.Door.Module)
671   11/16/2010 11:08   Transmit   E Off (1.F.Door.Module)
672   11/16/2010 11:08   Transmit   F3 (L.Room.M.Phantom)
673   11/16/2010 11:08   Transmit   F On (L.Room.M.Phantom)
674   11/16/2010 11:08   Receive RF   A 00TV
675   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Closed
676   11/16/2010 11:08   Receive RF   A 00TV
677   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Closed
678   11/16/2010 11:08   Receive RF   A 00TV
679   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Closed
680   11/16/2010 11:08   Receive RF   A 00TV
681   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Closed
682   11/16/2010 11:08   Macro   F3 (L.Room.M.Phantom)
683   11/16/2010 11:08   Macro   F Off (L.Room.M.Phantom)
684   11/16/2010 11:08   Receive RF   A 00TV
685   11/16/2010 11:08   Receive RF   Living.Room.Motion - Sensor Closed

[Tuicemen]

Well so much for the "Battery Idea" though there is a correlation of some sort.
I put bad batteries in a spare sensor  and triggered it now all sensors are sending strange M signals
One thing I have noticed is AHP doesn't always report the correct signals received.
Using a program created with the SDK will show the correct signals 99% of the time
and the signals are  M1 SOCIALITE,01,F3,51,0E,0C-1 followed by the date/time
Note: the numbers corespond to the security sensor sending it.
So your M1 signals will vary! the last digits before the date will be a -1 or 0 indicating a open or closed state
Even Active CView available in the AHP SDK will so these

[mike]

I beleive that this version also has bug with Dusk and Dawn timer.
None of my Timer trigger after the clock change last weekend.

Also, would anyone looking into the bug where sensor NOT triggering a macro with conditon, please? (Email using Onalert)

P.L

PL, this version still does not work on duck,dawn,day,nite.  accept that.  I use a switch with timer I SET to turn ON at 7am, OFF at 1800hours and have a DAY macro that just sets flag 1, a nite Macro for when this sw goes off to clear flag 1.  this continues to work for day/nite/dusk/dawn triggers on all my macros.

and this version also continues to work for sending an email if macro triggers AND condition is flag 1 off.  My old test macro watching same trigger with condition day and nite continue to NOT work with this version.

Please just change your dusk/dawn to a flag YOU set with a timer and your email alerts will work like mine have for years and still do with this new version.