AlCalzone

nope

Are you talking about Blockly?

This is the metadata I'm getting when zwave-js parses the received command for supported events I found in your log: ``` // value ID {"commandClass":113,"endpoint":0,"property":"Home Security","propertyKey":"Cover status"} { type: 'number',...

> "it discovers the supported events (cover tamper and motion), but thinks they're "unknown"" That's a bug in the code for logging. The events are correctly supported but the logging...

Transferring this here for further investigation. Driver-wise this seems to be fine.

In this particular case there should be a `"metadata updated"` and a `"value updated"` event, since these are statful notification variables.

You are querying the metadata after the node is ready, right?

If you look at my comment above, the metadata seems to be correct. I can only imagine that the fallback metadata is being cached before the interview sets the correct...

Can we have this? Pretty please? @rsms

I like having this in repo files :+1: . We should avoid hardcoding stuff (like unsafe-perm for zwave) in the future.