Patrick Fiaux

Correct, that's probably left over from when the SDK only ran 1 driver, it should be server name.

I see the use case for this, that makes sense. As you mentioned if we go this way it's more important to add this in the neeo-sdk-toolkit/cli since it will...

I like the idea! Currently we don't use pull to refresh in the mobile app. Once we do I think this would be a nice feature.

Thanks for the details. Looks like an issue with transparency of images but on the Brain firmware side not on the SDK side.

No need, I think we already know what the problem is. The images for the remote are preprocessed (resized, optimized, ...) as part of that we should have transparent background...

As @bdauria mentioned we're also considering a switch to typescript for the neeo-sdk (driver/server). I would also put that in the short/mid term plan.

Another element of the current NEEO SDK that should be split off to the tools repository is the recipe API component which gets some recipes and lists power states.

@Shepless regarding your comment in https://github.com/NEEOInc/neeo-sdk/issues/100#issuecomment-394511801 on the best way to run multiple drivers (single vs multiple servers and process forking), if you don't mind I think it fits better...

Small update we've published some SDK examples update in the next branch (we'll updated them again when we decouple driver/server components of the SDK). We're also working on splitting off...

The new @neeo/cli is now available here: https://www.npmjs.com/package/@neeo/cli https://github.com/NEEOInc/neeo-sdk-toolkit/tree/master/cli