Rob Griffiths

I assume that's the job of the workflow / build step

I tried running it myself but my Debian VM would.hang part way through and the EC2 instance left running doing nothing.

@hooman-myadbox I decided to use container images with the native Alpine Chromium binary installed since this PR didn't seem to get much traction. https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/

You can use `->useFallback(false)`. Seems to be related to when images have corrupt or invalid EXIF data, and exif_read_data throws and exception. I get an exception thrown `exif_read_data(file-20151123-565300d79e623): Illegal IFD...

Thank you From what I can tell, very little as the devices don't seem to keep track of what message I'd has been used. It's more likely to do with...

If you you feel confident you could reconnect the bulb with the cloud and record the messages for a few hours using https://github.com/bytespider/mqtt-debug. More Info on the process I used...

Meross devices typically (I don't know if all do) require TLS so you'll need to set up a certificate and probably port 8883

That's strange. Which branch of the code are you using? Did you `npm install` the dependencies?

@Smilebags @rolfmcduff have you tried `--use-wifi-x`? alternatively there's a beta version that knows to apply it automatically. https://www.npmjs.com/package/meross/v/2.0.0-beta-1 *note that parameter names have changed in v2

Ah yes, that seems possible. Bit of an oversight.