[RELEASE] CoCoHue: Hue Bridge Integration (including scenes!)

[bertabcd1234]

Yes, I believe it is this issue again:

@bertabcd1234

Yes, I believe it is this longstanding issue mentioned above:

@bertabcd1234

If a large number of events are received all at once (e.g., if turning off an "All Hue Lights" group--whether inside or outside of Hubitat), either the Hue Bridge or Hubitat (haven't figured out which yet) seems to cut off the data, usually resulting in malformed JSON and the inability to parse the events. Thus, I do not recommend completely disabling polling at this point.

As far as I can tell, this is something odd with how Hubitat's eventstream library is handing this incoming data or perhaps with how the connection options are being specified on my part, though if it's the latter, I haven't been able to figure out anything that works (there are very few combinations that do; I suspect this might be a side effect of specifying rawData: true, but it doesn't work at all without that). The issue is that the eventstream data gets split up among multiple calls to parse() in the driver instead of coming in all at once, and then each chunk is generally invalid (on its own) and causes this error when trying to parse it.

I've only seen this when large amounts of data are sent at the same time, e.g., when turning off or setting color/CT on all Hue lights or at least large room or zone. Data should eventually catch up via polling (which I recommend keeping enabled still for this reason) or, should they happen on affected devices, other changes on the eventstream interface.