Hi Marius,
Did you change anything when copying this error message?
I was wondering about lat=lat6&lon=4lon3 in the error message.
Anyway, this is an irritating error to fix, as it only shows when there is a connection issue to Weatherbit - which fortunately - does not happen that often.
I have now made a catch all errors, and these will be returned to Home Assistant and put in the Log. If you get any, let me know what it says, so I can try to, either filter them away, if they are insignificant or at least categorise them as Warnings instead of errors if relevant.
You are right Marius, I forgot I renamed this also. The release notes are now updated to reflect this change. But same logic applies. As the Unique_id does not change, the sensor names stay the same as before the update, unless you delete and re-add the Integration.
No, unfortunately that is not available in the API. The High/Low temperatures are for the whole day (6AM to 6AM)
Canāt you use the Current Temperature as a guidance? You can get that when adding the sensors to your installation.
Its definitely possible. It would just be a more complicated automation. Having a night time high letās me set the thermostat once for a sleep mode. Iāll have to figure out some other way of handling it.
in other threads the unit for windspeed popped up again. Weather bit now uses m/s but some prefer km/h (in the metric system of course). would it be possible, call it even a cool feature, to be able to select the unit in the integrations options?
It would prevent the need for some to have to write extra template sensors.
also, and that wouldnāt need any option at all: could you add āKnopenā (Dutch for) or āKnotsā
thanks for considering !
Added option to set Wind Unit
If you are using the Metric Unit System in Home Assistant, there is now an option to set the Wind Unit to either m/s, km/h or knot in the Config Flow. You will be asked during installation, or you can change it, if the Integration is already installed, by going to the Integrations tab and select Options.
Note: If you are using the Imperial Unit system, changing this has no effect.
Agree - But I never had a request from an Imperial user to change Wind Units, and Marius was asking for it, so I made it. For Wind Speed 1 m/s equals 1.9 knot
Thanks! Though I fear I might have caused some confusion here, for which I am sorryā¦
the Dutch word I mentioned (Knopen) is for the English āKnotsā. I asked if it was possible to add that, by which I meant add a dedicated āKnotsā sensor. This would be of added value certainly. And make your component stand out even more, since not many (if any) weather integrations offer that.
Got it. I will remove the knot conversion from the regular Wind Speed, and add a new sensor. With that, also the users with Imperial unit system, will have access.
And yes, the difference in data is a timing issue.
cool, thanks, youāre a champ!
working nicely as it stands, must say. Love these options in integrations that have effect immediately without requiring a restart
need to find a correct icon for Knots:
fear mdi:sign-direction comes closestā¦ or flag-variant maybe
