Jason

From the documentation, the `command` property is only in beta. @me once the app is out of beta, I'll add a new property for `command`.

Is this something that happens on every boot? or randomly? This will be hard to track unless you can find what HA is sending NR at the time of the...

Looking for what happened before the first line in HA log ``` 2022-07-11T23:10:08.707061245Z 2022-07-12 00:10:08 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [139777827339520] Received {'type': 'unsubscribe_events', 'subscription': 7, 'id': 40} ```

You could try placing this at the top of the `settings.js` in your NR config directory. ``` process.on('unhandledRejection', (reason, p) => { console.log('Unhandled Rejection: ', p, 'reason:', reason); }); ```

> Does anyone know whether there has been any update on this issue? I had to downgrade to 2022.5.5 to make NR stable. Seems like it's been abandoned? Short answer:...

That was me making a random guess.

You can edit HA websocket lib to output the message that causes this error. Inside the NR config directory there should be a `node_modules/home-assistant-js-websocket/dist` directory. If you edit the `haws.cjs`...

@coltoneshaw if you do not see `Received event for unknown subscription 3. Unsubscribing.` in your logs. Your issue is not related to this one. Try turning on the heartbeat option...

https://github.com/zachowj/node-red-contrib-home-assistant-websocket/commit/6c6421298acd176a9632d01ec34356417e163fda

Yes, it's very outdated. I'll see about getting something written up.