Peter Wahlberg

I just stumbled over this [issue](https://github.com/awslabs/aws-deployment-framework/issues/449) and [PR](https://github.com/awslabs/aws-deployment-framework/pull/450), and i think this change would solve this issue.

Hello @ayush987goyal No, that project was unknown to me, and seems to be more complete than cdk-watchful. Is cdk-watchful going to be replaced by https://github.com/cdklabs/cdk-monitoring-constructs?

Already on it, it looks quite good. :) The sad part is that i spent quite some hours on this PR. Would probably be a good idea to link to...

No worries, things are changing all the time. :) As i said, it looks more complete, future-proof and extensible. I'll check it out and see if anything could be improved....

I'm currently trying to implement this and will open a PR soon.

I have an ongoing discussion about this with Thermo floor, and they have finally involved their firmware developer to look into the underlying issue. I've seen packet captures from the...

> * "If I don't remember incorrectly, a customer in another ticket said HA were also working on a fix for it." I've told them on multiple occasions that yes,...

Got an update today from the support. `We're working on it, but have no fix yet.` - It sounds to me that they've acknowledged this to be an error on...

Absolutely. I've attached them here. The file contains two different inclusions and i don't remember which one the screenshot is from, but i think they both contain the issue. [Zniffer-traces-ZTEMP2.zip](https://github.com/zwave-js/node-zwave-js/files/15023794/Zniffer-traces-ZTEMP2.zip)...

Just upgraded to the latest version of the `zwave-js-ui` addon which includes the fix, and the inclusion now works fine again. Thanks for the fix/workaround @AlCalzone