Optimization & Simplification
v5.1.1 - bug #113 Fix Example script for AnyDevice SecuritySystemTargetState and create new example SecuritySystem script
v5.1.0 - As Part of V5 Performance/Optimization release, Cmd4 no longer calls process.exit that could take down the bridge if you had configured Cmd4 incorrectly. Instead Cmd4 uses "throw" which is more widely acceptable.
v5.0.2 - Bug fix for issue #112. Fakegato causes Cmd4 to not start in v5
v5.01 - Bug fix for thrown exception for incorrect use of this; Only encountered when a massive WoRm queue failure is created.
Cmd4 v5 is meant to be a simplification release as per the recommendations by homebridge. See https://git.io/JtMGR. With this major release a lot of options that were developed along the way are now automatic.
Gone are the very confusing Cmd4_Mode and RestartRecovery.
- RestartRecovery is now automatic; Which not enabling could cause your device to turn on/off over a restart
- Cmd4_Mode is as per https://git.io/JtMGR where the callback is immediate to homebridge with the data from your device to follow.
- Demo mode is still available by not defining any polling.
Internally there is a lot of code that was removed, which only contributed to the complexity of Cmd4.
The only impact to you are the warnings that Cmd4_Mode and RestartRecovery are no longer required.
I hope you enjoy the changes
John Talbot