I think that there is a bug in the plug-in.
I am using a leopard controller with SECU16 (8 inputs and 8 outputs), SECU16I (16 inputs) and RLY8XA (8 outputs) modules. The plugin GTS CPUXA has no problem upgrading the status of the inputs or drive and update the status of the outputs on module SECU16. SECU16I works fine too.
RLYXA outputs doesn't work properly: If you act on the outputs through homeseer, the system activates or deactivates the outputs and represents the real state of the outputs correctly. But if you act on the outputs by another way, by program running on the leopard, the state of the output on the homeseer device is not updated. In fact, when you start Homeseer, the state of the outputs of the RLY8XA modules is not updated to the true state of the same, remembering the state in which they were left when you activate or desactivate them through homeseer.
I am using a leopard controller with SECU16 (8 inputs and 8 outputs), SECU16I (16 inputs) and RLY8XA (8 outputs) modules. The plugin GTS CPUXA has no problem upgrading the status of the inputs or drive and update the status of the outputs on module SECU16. SECU16I works fine too.
RLYXA outputs doesn't work properly: If you act on the outputs through homeseer, the system activates or deactivates the outputs and represents the real state of the outputs correctly. But if you act on the outputs by another way, by program running on the leopard, the state of the output on the homeseer device is not updated. In fact, when you start Homeseer, the state of the outputs of the RLY8XA modules is not updated to the true state of the same, remembering the state in which they were left when you activate or desactivate them through homeseer.
Comment