yes indeed!ben wrote: I saw MeteoBridge has a live data interface that can be polled, it sounds like push services are preferred but I don't think there's any harm in polling once every minute (or a user-defined interval greater than 1 minute).
http://wiki.meteobridge.com/wiki/index. ... n_Services
Does weewx have something similar?
option 1) add one template file to the weewx reporting system so that weewx emits data to a file in csv or json or whatever format. make that file accessible to a local web server. the dashbox would then make an http GET request for that file, and there's your weather data!
option 2) install the weewx-csv extension. it will emit all sensor data to a designated file every time any sensor is updated. make that file accessible to a local web server. the dashbox would then make an http GET request for the file.
option 3) write a weewx service that listens on a designated port, then responds with current sensor values in json/csv/whatever format. the dashbox would make a network connection to the port whenever it wants data.
option 4) install the weewx-mqtt extension so that weewx sends live sensor data to an mqtt broker on the local network. make the dashbox subscribe to the mqtt broker. now you have up-to-the-second data with all the transport goodness of mqtt.
you can run any webserver you like. nginx works really well, especially on low-end hardware. but lighttpd and apache are fine as well.
option 1 is probably the quickest path to having something running. option 2 has more unit-conversion capabilities built-in. option 3 requires some python coding.
however, if you make the dashbox know how to become an mqtt consumer, then you open up a world of possibilities. provide an option for running an mqtt broker on the dashbox itself and you've really got a powerful tool. (the mosquitto broker has a small footprint, is easy to install, and works on many platforms)