V3.7.4

For Queued polling, put Related "Get" into queue instead of calling it asynchronously.
Fix Homebridge throwing error about invalid data which had an invalid return code anyway during Queued Polling.

If you have some ideas about what else Cmd4 could do; Please let me know. I'd really like the config.schéma to be the next high priority, but all thoughts are welcomed.

Take care,
John Talbot

Performance improvements

Good day to you all,

This release delivers some much needed performance improvements with the churn as of late. More setup is done before the critical stage of adding the characteristics to the service and polling is no longer critically parsed during the "Set" events for related characteristics.
The related characteristics are now defined per device as some some characteristics are optional in different devices or have no "Target" characteristic like Temperature Sensors compared to Thermostats.

Take care,
John Talbot

v3.7.2

Myself and Mitch Williams have been hard at work on this feature for months in our spare time. Unfortunately he is the only one with an AirCon that really needs it, even though all could benefit from it in the end. My apologies for the many releases as it has been difficult to attempt testing without the device.
We did do Betas for awhile and private branches, but it is a lot of extra work trying to maintain multiple streams.

Thank you for your patience,

John Talbot

Fix PriorityPollingQueue Polling timer merge issue

I believe something went wrong with a branch merge. This fixes the priority polling queue timer not firing.

Priority Queue Polling - WoRm

Priority Queued Polling is nice Sequentially, but is even better with Write Once, Read Multiple ( WoRm ). This means that only one "Set" can occur and nothing else, but multiple "Get"s can occur at a time across a device, which could comprise many accessories attached to a device; As is the case with an AirCon.

If you continue to use Cmd4 as previously configured without Priority Queued Polling, nothing changes.

v3.6.1

Correct a message of the number of staggered polling characteristics were displayed if PriorityQueuedPolling is also configured in another accessory. As well as ensure the stateChangeResponseTime was obeyed during PriorityQueuedPolling.

Priority Queue Polling

This release introduces Priority Queue Polling; A welcomed feature that resolves the issue of simultaneous queries to an accessory with a queued system. For any accessory with a Cmd4_Mode of "Polled" or "FullyPolled", by tagging the polling characteristics with a "queue": < queueName >, all requests of that characteristic will be put into a consecutive queue. The priority of the queue is given to all IOS requests and polling second.
Further documentation of this feature can be found in the Cmd4 Developers Guide and from the Cmd4 Portal at https://ztalbot2000.github.io/homebridge-cmd4

Custom characteristics and bug fix for polling interval

This release picks up the new Cmd4 Capability of creating custom characteristics, documentation forthcoming. The update is mainly to fix a polling interval issue.

Take care,
John Talbot

One day one bug unveils another

Nobody noticed the first one I found, but the fix revealed the second. Sorry,

John Talbot

polling timeout fix

Day 1 bug, the timeout used was always the default (6s) or that defined by the accessory, not that of the characteristic being polled.