@Emil Thanks for explanation.
Works now...
I also managed to figure out what JSON structure is going for MDM under point 3.
Basically I export pairings from dev hub and if we use those buttons on managed hub I just paste "buttons pairings" json in to the field.

You use the one written on the back of the hub. If you have changed the password however it's the one you have changed to.

@Emil Ok, thanks for info 🙂

Our runtime is not 100% compatible with node.js and you can't directly install npm modules. However you could try copy-paste the source code into our IDE and maybe it will work.

Hi!

This is an interesting koncept which we have elaborated on internally. I can't say much more about this at this time though 🙂

Hi!

I agree that it is not super clear, but if you check the "Restart after crash", it will also restart after reboot!

@Emil
Did the record part work all the time, while the playing part failed all the time? Yes.

Are you using the 1st hub generation or the 2nd (Hub LR)? 2nd.

But my bet is that I might have sent in some bad Array while testing that made the IR-queue never emptying/play never ending? Maybe.

Please add the following line at the top of your file:

Buffer.from = function(v) {return new Buffer(v)};

I think that should work.

Thanks and apologies Emil - you have no idea how many times I read the API details - and missed that aspect. Working now.

Great job with this API - just another vote for MQTT client support in the future