Release 13.1.148 1. The visual programmer DIM element didn't work correctly when provided a object parameter for the device, group, or room to dim. Not resolved. 2. The schedule entry wizard when invoked from the schedule category on, off, dim, scene, thermostat, and IR buttons when the display was in list mode could behave oddly. Now hopefully better behaved. Release 13.1.144 1. Changed DDNS support to work with either the HCA implemented DDNS or other systems. This changed the DDNS configuration dialog. Release 13.1.142 1. A problem with displays that have icon positions that use a different size display theme in development mode and control mode when viewed by the Windows client has been resolved. Requires use of client version 13.1.34. 2. In some cases a status request initiated by a program and sent to a UPB device could cause the command to be transmitted with a packet count of 4 rather than the default. This could cause devices that don't contain generation 2 firmware to respond too soon and have that reply lost due to a collision of messages on the power line. 3. Logging for UPB commands has been improved. It now attempts to show in the log entry the button or rocker that sent the command. 4. Support was added for the changes to the PulseWorx KPC7 keypad to handle the case where the Dim/Bright button was replaced by a 6th scene button. 5. WARNING: INCOMPATIBLE CHANGE! The PulseWorx 7-button keypad buttons are now referred to as "B1", "B2", "B3", "B4", "B5". If the keypad bottom button is used as a split up/down button those buttons are referred to as "UP" and "DN". If the keypad bottom button is used as a single button it is referred to as "B6". This may effect any expressions where you used the keypad name with a button qualifier. For example, "Kitchen - Keypad:B1". In previous versions of HCA the buttons were referred to as "S1", "S2", etc. and so has to be changed. Release 13.1.139 1. Minor changes made in support of connection to Global Cache ITach units. 2. When configuring the IR interface when running in client-server mode sometimes the client and server get out of sync on how the interfaces were configured. Now resolved. 3. When connecting to an IR interface in client-server mode and the connection wasn't made - using the wrong IP address for example, the client to server connection would time out and be reported as that rather than the correct message of "Can't connect". Now resolved. 4. In some circumstances making a change to the weather provider or IR interfaces when in client-server mode, had those chanages correctly sent to the server but if the server was terminated - perhaps due to a Windows update - the HCA portion of the system registry wasn't updated so the settings wouldn't "stick". Now resolved. 5. In some circumstances - having the display pane contents changed by a program - a right-click on an element in the design pane (left pane) could perform an incorrect action or, in the worst case, terminate HCA. Now resolved. 6. Changes to both the Windows client and the HCA Server: If you have a display with an image background and icons positioned on it at selected locations, the icon placement is now shown when connected by the Windows client. This isn't supported on the iOS or Android mobile applications. 7. If you used the option to watch for an interface to be powered down or disconnected - imprecisely described as "power fail detection", this didn't work if you were using a UPB interface. That function has been restored. 8. In UPB installations with a split-phase repeater installed it was possible in some situations for HCA to send a command at the wrong time. It could start a transmission between messages sent in a multi-packet. This has now been corrected. 9. The control UI popup keypad for UPB keypads could show the wrong button state in some circumstances. Now corrected. 10. In some circumstances when connecting to the server from a mobile device the connect would happen but the display would be nearly blank. This is a password problem. The server is not correctly returning an error when the mobile app tries to connect with the wrong or empty password. Now corrected. 11. A new warning is given in the Alexa support if a device name contains characters that may be a problem for Alexa device discovery. 12. The Protocol bridge setup dialogs were not drag resizable. They now are. A boon for all those with really long device names. Release 13.1.128 1. If a program used the new "Automatically run again after