Good spot @sunny. I’ve been in the beta group for this new forecast endpoint, and WeatherFlow are aware that the docs released just before the Christmas break don’t quite match the current functionality of the endpoint. I assume they will fix it first thing after their break ready for the public launch.
Sorry, @sunny. As Peter notes, the docs are slightly ahead of the production implementation. We had hoped to release both at the same time, but that didn’t happen. The update will go out next week.
Yes, after realizing we were not going to be able to push the production changes before the New Year we decided to quietly update the docs so that the developers beta testing the forecast endpoint could comment. Not the smoothest release ever, but a step forward!
aha, as mentioned in the answer above, this is a mismatch between documentation and implementation. As the documentation is ahead of the implementation I assume, that lat/lon is no longer needed, just the station id. But you will have to wait until the implementation catches up.
Could you clarify on the response object (I guess I’m not in the beta program so I can’t test it out myself). It says it returns a daily and hourly forecast, but the docs don’t indicate these objects are arrays, so it does it just return the current day/hour?