Hello all,
Today I decided to throw caution to the wind and upgrade from AHP 3.204 to 3.228.
I immediately noticed a change in the LM14a interface performance - not a good change. Here's the recap:
Ver 3.204:
- When a LM14a is activated from the desktop the desktop status is correct and Activity Monitor shows the outgoing extended Code command
- When a macro that uses a LM14a is executed - if the macro uses a dim or bright command (extended code) the outgoing command is not shown in activity monitor and the desktop status is not updated. Note that the LM14a status is updated if you issue a simple ON/OFF command (uses standard command formats). The upshot is that if you are using a dim/bright command with a LM14a (extended code) in a macro, you cannot use the "device status" command in smart macros to qualify macro execution.
Now I've lived with the above for a number of years now using the LM14a interface with my Leviton units. It's become second nature to use flags and dummy modules to indicate the status since AHP couldn't monitor the extended codes.
Over the last couple of months, I started playing with the Marmitek X10 Pro interface and found that it could interpret extended codes and correctly indicated the status of LM14a units. I decided to give 3.228 a try -
Ver 3.228:
- When a LM14a is activated from the desktop the desktop status is correct and Activity Monitor shows the outgoing extended Code command - so far so good
- When a macro that uses a LM14a is executed - if the macro uses a dim or bright command (extended code) the outgoing command is shown in activity monitor, but it is shown at the module address +1.. To be more specific, if a macro issues a bright 90% to A1 the desktop icon for A2 will turn on and indicate 90%. Activity monitor also shows the A2 module extended code command. Meanwhile, the lamp at A1 responds properly and my testerlinc indicates an extended code command to A1 (as it should).
The above could at best be referred to as "backward progress". The incorrect interpretation of the extended codes now affect other units that were functioning properly.
On to 3.236:
- LM14a Desktop functions properly - so far so good
- LM14a Macro functions are indicated properly within activity monitor and display properly on the desktop.
Unfortunately, although the desktop status is updated, the "monitored status" for the LM14a remains "off" when using bright commands. This means that you won't be able to use the smart macro "device status" command with the LM14a interfaced modules.
Nonetheless, 3.236 is an improvement. I am not sure what other changes were made in going from 3.228 to 3.236, but if you are using LM14a interfaces, the 3.236 seems to function far better.