Unable to install WeatherflowCloud integration

I have a Weatherflow Tempest station with the local integration installed. All works well in that area. I am able to capture the local Tempest data into Home Assistant. However, I am unable to installl the WeatherflowCloud integration which what I would like to use for Weatherflow forecast data. I have two Weatherflow data authorization tokens. I get the same error when attempting to install the integration using either token. In the UI I just get “An unknown error has occurred”. In the Home Assistant Core logs I get the error below, again when attempting to use either token to install the integration.

This did work at one time, but it stopped working. Unfortunately I didn’t keep track of the Home Assistant version in which it was working. I just deleted the integration and tried to reinstall.

Any insights into what is causing this would be helpful.

Logger: weatherflow4py.rest
Source: components/weatherflow_cloud/config_flow.py:20
First occurred: 4:12:04 PM (2 occurrences)
Last logged: 4:12:36 PM

Unable to convert data || {“stations”:[{“created_epoch”:1779989512,“devices”:[{“device_id”:1225189,“device_meta”:{“agl”:1.8288,“environment”:“indoor”,“name”:“HB-00218125”,“wifi_network_name”:“”},“device_type”:“HB”,“firmware_revision”:“342”,“hardware_revision”:“2”,“location_id”:219022,“serial_number”:“HB-00218125”},{“device_id”:1225190,“device_meta”:{“agl”:7.62,“environment”:“outdoor”,“name”:“ST-00209965”,“wifi_network_name”:“”},“device_settings”:{“show_precip_final”:true},“device_type”:“ST”,“firmware_revision”:“192”,“hardware_revision”:“1”,“location_id”:219022,“serial_number”:“ST-00209965”},{“device_id”:1241092,“device_meta”:{“agl”:1.8288,“environment”:“outdoor”,“name”:“HB-00000000”,“wifi_network_name”:“”},“location_id”:219022}],“is_local_mode”:false,“last_modified_epoch”:1780700717,“latitude”:41.4915,“location_id”:219022,“longitude”:-81.69691,“name”:“Collins”,“public_name”:“Carter Rd”,“state”:1,“station_id”:219022,“station_items”:[{“device_id”:1225190,“item”:“air_temperature_humidity”,“location_id”:219022,“location_item_id”:1659328,“sort”:0,“station_id”:219022,“station_item_id”:1659328},{“device_id”:1225190,“item”:“barometric_pressure”,“location_id”:219022,“location_item_id”:1659330,“sort”:1,“station_id”:219022,“station_item_id”:1659330},{“device_id”:1225190,“item”:“diagnostics”,“location_id”:219022,“location_item_id”:1715489,“station_id”:219022,“station_item_id”:1715489},{“device_id”:1225190,“item”:“light”,“location_id”:219022,“location_item_id”:1659332,“sort”:5,“station_id”:219022,“station_item_id”:1659332},{“device_id”:1225190,“item”:“lightning”,“location_id”:219022,“location_item_id”:1659329,“sort”:2,“station_id”:219022,“station_item_id”:1659329},{“device_id”:1225190,“item”:“rain”,“location_id”:219022,“location_item_id”:1659331,“sort”:4,“station_id”:219022,“station_item_id”:1659331},{“device_id”:1225190,“item”:“wind”,“location_id”:219022,“location_item_id”:1659333,“sort”:3,“station_id”:219022,“station_item_id”:1659333}],“station_meta”:{“elevation”:181.0064086914062,“share_with_wf”:true,“share_with_wu”:false},“timezone”:“America/New_York”,“timezone_offset_minutes”:-240}],“status”:{“status_code”:0,“status_message”:“SUCCESS”}} || to || <class ‘weatherflow4py.models.rest.stations.StationsResponseREST’> – ‘device_type’

Home Assistant

  • Installation methodHome Assistant OS
  • Core2026.8.3
  • Supervisor2026.07.5
  • Operating System18.2
  • Frontend20260729.7
  • Companion app2026.7.4 (2026.2715)

I’m not a Weatherflow user but some suggestions:
Get a new token, maybe by changing password etc. Try again. If the error is exactly the same, then the issue is elsewhere.

Check if all the values passed in the code in your log are valid ones on both ends. Do they match, string for string, number for number? Exactly? You may try temporarily turning on debugging in your integration to check those.

Is UDP working? Is DNS working well? Networking problems are always a risk with cloud integrations.

Check the existing errors on GitHub.

and more generally

If nothing is common, raise a new GitHub report as the person responsible to update the code may not see this thread, and may frequent Discord instead. Your code may be working correctly but the vendor may have changed their API since it was last updated - a frustratingly common occurrence for some vendors and a simple tweak of a variable definition on the code may be all that is needed for everything to match up again.