Update node requirements to satisfy the current Node.js version of v22.12.0

Minor change as title suggests

v8.0.2

Hi all,

This minor change fixes a bug in homebridge v2 where old accessories were not being deleted. Thanks to Wong for the fix. It was the most elegant solution when I looked at different possibilities.

take care,
John Talbot

v8.0.1 bug fix for accessories removed after upgrade

Hi all,

Cached accessories and those not defined in your config.json no longer need to be explicitly removed as the homebridge plugin template skips over them. The result was it looked like accessories were being added and removed, but they really were not. If anything, the last known state over a restart was lost of your accessories. This has been corrected with this release.

ttyl,
John Talbot

v8.0.0

Good day fellow homebridge users

Cmd4 v8.0.0 makes changes that support the upcoming homebridge v2. Their release deprecates a few device types, namely bridging devices that I'm pretty sure nobody uses. There are a couple of associated characteristic settings that they also deprecated. The only one I found odd was the characteristic named "category"; not that HomeKit actually used this recommendation to change the icon.

take care,
John Talbot

Add new accessories and characteristics

Hi all,

Please note that in the upcoming Cmd4 version 8.0 only Platform defined Cmd4 accessories will be allowed. (No worries. This is probably everyone). This is because of Homebridge deprecated templates.This will also make homebridge-ui easier to implement. In short this is allowed:

"platforms" :
   [{
         "platform": "Cmd4",
         "accessories" :
         [{
              "type":                      "Switch",
             ...

This will not be

"accessories": [
       {
          "accessory":                "Cmd4",
          "type":                     "Switch",
         ...

Now onto the good stuff ...
Cmd4 version 7.1 now supports the following new accessory types:

• AccessCode
• FirmwareUpdate
• TapManagement
• WiFiTransport

Cmd4 also now supports the following new characteristics:

• AccessCodeControlPoint
• AccessCodeSupportedConfiguration
• AirPlayEnable
• CharacteristicValueActiveTransitionCount
• CryptoHash
• FirmwareUpdateReadiness
• FirmwareUpdateStatus
• HardwareFinish
• MetricsBufferFullState
• MultifunctionButton
• SelectedDiagnosticsModes
• SelectedSleepConfiguration
• SiriEnable
• SiriEngineVersion
• SiriLightOnUse
• SiriListening
• SiriTouchToUse
• SiriTouchToUse
• StagedFirmwareVersion
• SupportedMetrics
• SupportedFirmwareUpdateConfiguration
• TapType
• Token

Enjoy,

John Talbot

Full Changelog: v7.0.3...v7.1.0

fix: setProps for those who redefine their own characteristic properties

This is a very minor fix as nobody has used this feature in a long time.
If you redefine your characteristics properties they must be formatted like:

    props: { 
         currentTemperature: { maxValue:32, minValue:1}, 
         targetTemperature: {maxValue:32, minValue:1}
    }

There was a bug that predefined the object and this feature was not documented properly. Also a unit test was implemented to test if the actually properties were changed.

Note: while Cmd4 allows you to change the properties and Homebridge accepts this; That is not to say that the HomeKit GUI will respect them.

v7.02 Change for AdvantageAir users of this plugin

v7.02 Change for AdvantageAir

This change is for the AdvantageAir plugin only which uses Cmd4. It puts double quotes around the accessory names instead of single quotes. It allows them to put single quotes in their accessory names; However they accept the responsibility that moving away from single quotes means the shell can interpret the names within.

v7.0.1

Hi,

The reason for the major version numbering update was to for deprecation warnings to throw an error. These warnings have been there for years. Otherwise there was just one major bug fix for an accessory not going unresponsive and not showing it recovering afterwards.

I don't have much time to play with homebridge lately so please be patient if you find issues. The beta of the above fix has been available for months and people have been using it.

take care,
John Talbot

remove annoying running message & update docs

there was an annoying update message left in that has been removed. a test case was created so this cannot re-occur.
v7.0.0 documentation was updated

Resolve accessories not going unresponsive & deprecations removed

The reason for the major version numbering change was for some deprecation warnings to be removed and to now throw an error.
A bug to fix accessories not going unresponsive was resolved and now a "Get" retry count can be set, the default is zero (No retry)