Nice list, but I would carefully evaluate the options here.
Not all integrations should be cloud based. E.g. a Philips Hue integration should really be based on a plugin / local integration. A local Meshbot can then interact with the lightning without relying on Internet connectivity. Trust me, I hate it if I cannot control my lights if that is caused by an issue with my telco.
Furthermore, a lot of the integrations make perfect sense from an IFTTT competition point of view, but have little to do with domotica. Those integrations should have a low priority. Think of Insta, LinkedIn, Discord, GitHub etc.
Android is on the list, which might point to ‘tasker’ integrations. On iOS, it would make sense to be able to integrate with ‘shortcuts’. This way, I can turn on my coffee machine if I turn off my alarm on my phone (I already have this running on Vera).
For Netatmo specifically, again I would prefer local integration through a plugin, but if integration comes from NuCAL, make sure to include the Netatmo Smart Indoor Air Quality Monitor range as well, the API for that is slightly different from the Thermostat and Weather Station range.
Whatever can be done locally we will also do locally…
NuCAL only does Cloud integrations…for example its ok for NuCAL to provide phillips Hue integrations, while we at Ezlo might also build a plugin for Hue to operate locally…
So the idea is: to give that option to users. they are not mutually exclusive to us.
That makes sense, it allows the user to select the method that best reflects the use case. If I have two houses, and I want to signal the lights in my primary house if there is a fire alert in the second house, NuCAL integration might work, or a global Meshbot, or meshene.
Might be confusing for some users, so the documentation should reflect the options and pro’s/cons.