Repository navigation
BloomSky stopped in 2022 #87
Description
BloomSky shut down in 2022 and was bought by Nubila Network, which has no documented API compatible with the old api.bloomsky.com/api/skydata/ endpoint. The integration cannot work for new users.
Piste : hide it from the add-station screen, mark existing stations as not working, and remove it in a later version. Nubila support could be a separate request once a stable API exists.
Activity
jaz-on commentedon Oct 2, 2026
Checked on 2026-10-02: api.bloomsky.com no longer resolves in the DNS (the plugin calls https://api.bloomsky.com/api/skydata/ from includes/libraries/bloomsky/BSKYApiClient.php), so BloomSky stations cannot be updated any more. Plan: remove BloomSky as a provider in a release announced in the changelog and the readme. Concretely: the BloomSky client and library, the connection screen and its options (live_weather_station_bloomsky_key, _connected, _auto_manage), the collection task, the help links (dashboard.bloomsky.com) and the extra module types only BloomSky produces; keep the stored measurements and the stations already created so that history remains readable, and show an admin notice on sites that still have a BloomSky station explaining that collection has stopped because the service did. The Nubila Network, which took over the BloomSky users, could be a replacement provider if it has a public API; to be investigated separately.
jaz-on commentedon Oct 2, 2026
Nubila Network as a replacement provider, checked on 2026-10-02 in its public API documentation (nubila-1.gitbook.io/api-docs): the Nubila Weather API is GET https://api.nubila.ai/api/v1/weather?lat=..&lon=.. with an X-Api-Key header and returns the current conditions for a position (temperature, humidity, pressure, rain, wind, uv, is_online...). It is a position based query, not an endpoint to read the data of one's own BloomSky device, and the documentation does not say how to obtain a key, nor the rate limits or the price. Its terms of use limit the API to internal development, prototyping and testing, forbid commercial, production or client-facing use and any redistribution of the API or its output without written consent from Nubila, which an open-source plugin where each user brings a key would need. So it is not a drop-in replacement and cannot be added as a provider as things stand. Lead: ask Nubila whether they plan a documented API for BloomSky device owners and whether such a plugin integration can be authorized in writing; until then BloomSky is removed as described above.
fix: hide the BloomSky connection box and drop BloomSky from the supp…
jaz-on commentedon Oct 3, 2026
Done in release/3.9.0 as the piste says: BloomSky is hidden from the add-station screen and existing stations are marked (#97), and now the connection box of the services settings is only shown to disconnect a stored account and BloomSky is no longer in the list of supported devices of the readme (#189). The code removal (library, classes, options, task) is left to a later version.