-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weather-Station Enhancement #1
Comments
this is a known issue. Weather station (eco or pro) support is currently limited to receiving weather broadcasts and publishing temperature and illuminance. I would however suggest to use the native Warema features to avoid wind damage - WMS Studio can be used to program that. Given the hackish status of this add-on, I wouldn't rely on it to prevent damages. Also, the native Warema function will "lock" shades in the open position when strong wind is detected, as an extra safety. |
That's exactly what I didn't know. I thought that a control via addon "overrides" the wind function in the WMS Studio and the blinds could be damaged. But if they are then locked, that's totally ok for me! |
hm, haven't tried using HA to be honest - I've only seen the "lock" in action using the wall remotes. Will give it a try next time it's windy around here. DISCLAIMER do not rely on this add-on to prevent your blinds/shades from being damaged by the wind - use the native function of WMS |
I read the documentation now - and you were right! It's written there
therefore I'm with you. We should not rely to this function for avoiding damage. Anyhow it would be interessting to have this data in HA for information. |
Hi,
it would be nice to get more information from the weaterstation. Currently only lux (lumen) is reported.
Weatherstation eco also reports wind for example.
Would be essential - at least for me - because blinds should go to open position at a windy day to avoid damage - and the most weather-internet-services are really unreliable on that topic.
Cheers
The text was updated successfully, but these errors were encountered: