I have used all the versions of FW 3 with my remote and not had a single issue. I'm currently using 3.0.2 and all is good. I would recommend updating to this FW and running the remote with 3.0.2 when it arrives 
I'm running the latest as well with no issues.
I think that most of the issues are hardware related. Mine will be replaced soon. My problem was at boot up, sometimes the remote started and sometimes not, but once it started everything just worked fine with 3.0.2.
When you first connect the Remote, make sure the KPA is turned off. Then, boot up and be patient. The first time you boot them together, there are long pauses as the firmware in the Remote is updating. If you get impatient, and interrupt the FW update (it's going on in the background), it will potentially really mess up the Remote. I have had zero problems.
When you first connect the Remote, make sure the KPA is turned off. Then, boot up and be patient. The first time you boot them together, there are long pauses as the firmware in the Remote is updating. If you get impatient, and interrupt the FW update (it's going on in the background), it will potentially really mess up the Remote. I have had zero problems.
Don't worry I knew about some issues with the remote and I took care to do it right. But it is a hardware bogus on some units.
When you first connect the Remote, make sure the KPA is turned off. Then, boot up and be patient. The first time you boot them together, there are long pauses as the firmware in the Remote is updating. If you get impatient, and interrupt the FW update (it's going on in the background), it will potentially really mess up the Remote. I have had zero problems.
the firmware in the remote never will be messed up when the update procedure is interrupted: it's buffered completely, validated and only written if everything is OK. This has been tested very, very extensively. so: no worries here, but indeed be patient to wait for the complete update...
the firmware in the remote never will be messed up when the update procedure is interrupted: it's buffered completely, validated and only written if everything is OK. This has been tested very, very extensively. so: no worries here, but indeed be patient to wait for the complete update...
to Kemper engineering methodology. This is how you make the update process very robust.
Totally agree
