This will make it possible to configure the tx_count from HA without reinitializing the PIM, or accessing private state.
In addition to making encoder tx_count public, I'm also still taking tx_count as a constructor parameter to the PIM -- this is because, as far as I understand the code, PIM's loop starts running before the constructor terminates, and it should have the "correct" tx_count value.
gwww
commented
2 years ago
This will make it possible to configure the tx_count from HA without reinitializing the PIM, or accessing private state.
In addition to making encoder tx_count public, I'm also still taking tx_count as a constructor parameter to the PIM -- this is because, as far as I understand the code, PIM's loop starts running before the constructor terminates, and it should have the "correct" tx_count value.