Closed TheBinaryLoop closed 2 years ago
Hi @TheBinaryLoop , thanks a lot for your contributions. As you can see the component is still in early development stage, but any help is well welcomed. In this case I guess the problem is that the Meross Component Integration does not necessarily puts the "application/json" header. Since the idea behind the Meross Component is to mimc the exact API calls that the Meross App does, I think I omitted such header. The quickest (and probably dirtiest) WA would be to force the addon to treat all requests as JSON (at least the ones coming from /v1).
I'll have a look at the network capture I stored about the app to double checks this still applies. In case things have changed, I might simply release a new version of the Meross Integration library, which adds the application/json header.
Solved with latest versions of the integration and local addon. Please update and let me know if that's now working as intended.
I am closing this as no further info was provided. Feel free to reopen if needed.