Hi, sensor.community.
Would you be interested in adding API support for integration with Weather Underground?
Our sensor boxes already have temperature + humidity sensors, which is useful for weather forecasting. It is very easy to send this data to Weather Underground API. I’ve found it very convenient to see my own weather conditions and forecast through WU by setting up a “personal weather station” with them.
I have added a new area on the sensor API page:
While doing that I found mentions of things like custom mqtt not being supported due to limited available memory on the sensor board. So I will understand if you declare WU support out of scope as well.
Thank you.
We have implemented MQTT.
We need/use MQTT for VOC and NOX (SEN55) and for LTE (SIM7000)
Thank you.
MQTT was just an example in my message, how the upstream project refused to add more connectivity due to constraints.
WU actually uses just one simple GET request to report temperature and humidity.
i think that firmware should support both MQTT and WU.
Why should we support WU. It’s a commercial platform, selling your data for what? That you have very limited access to their data? It was sold to IBM in 2016. They sold it last year to Francisco Partners, a private equity firm.
And in general: there is a config option to use an own “api” endpoint. This you can use to send your data to whom you want in the format they need. Even via MQTT …
we already use the option for our own API.. 
will you include us to next firmware version ?
we are definitely open source, crowd funded, and we offer sensor data to download.
why dont you add MQTT support ?
MQTT? Every service needs another string for the values. So we would need an option for every service that our users request. And this will definitely need too much memory (beside the pure mqtt support). Just look at more than one of the services and their API/MQTT description.
People only see their single case, which may be possible to implement. But we have more than 10.000 users.
Again: write a mapper script for your users or extend the existing script that you use for your own API.
i thought that MQTT was better for: IoT, remote monitoring, real-time sensor data, low-power devices, unreliable networks.
i tried it with SEN55’s and the other firmware and works fine (in the same hardware).
one way or another, some API’s are not working, right ?
like [Feinstaub-App] and [aircms.online]
i have no problem with my API, the only problem is that sometimes sensors send null data and i am trying to debug it. wifi signal, cable, power supply, different nodemcu, we will find it..
