[APP][Pro] Misol and Ecowitt (Release 0.2.24, Test 0.2.24 )

Ok!

Thank you Adrian!

BR
Manni

hello Adrian,

i am considering to buy a optical rain sensor because the bucket rain sensor i have now is collecting debris to often and when i place the bucket rain sensor on a pole 2meters above the ridge of the roof then the accuracy drops a lot with heavy wind.

is there a optical rain sensor who can be connected by the misol and ecowitt app?

greating Jan

I’m not aware of an optical sensor, but there is a haptic sensor using the WS85 or WS90. These use piezo sensors. Compared to a bucket type. these are faster to respond and don’t suffer with clogging up. I have both and the average readings are similar, currently the bucket type shows the monthly rain as 1mm and the haptic sensor shows 0.99mm.

thanks for the responce, i did a little google work and i see the ws90 has a lot of sensors, i don’t need more then just a rain sensor because that is the only one that is not working correcly on my current wheaterstation when there is a lot of wind.

so i considder the ws85 for the moment.

on both(ws85 and ws90) i need a ecowitt gateway for so far i can find online ore is there a way to connect the sensor directly on homey?
ore maybe as a second device on currend ventus w830?

greatings Jan

Correct, both need a gateway, but they are small and inexpensive.

small and inexpensive, i think i have something to learn.
i just did a google search and you mean something like a gw1100?
can i just oreder the cheapest one on alliexpress ore do you reconmend another?

The only thing to make sure is it on the correct frequency. The systems have to use different frequencies around the world, so make sure the gateway uses the same one as the sensor.

I got my first one from Aliexpress and it’s still working fine after about 5 years or more.

I have a GW1100 for about 2,5 years and is still working without any problems with Homey. I have the 433MHz version. Also have 4 garden humidity sensors and a lightning sensor.
It hangs in the shed, where temperatures can reach as high as 30 degrees Celsius in the summer and drop below freezing in the winter.

Since the last update, my Homey flows based on wind speed from my GW2001 haven’t been working correctly. The trigger is set to ‘wind above 15 km/h’. According to the app, there hasn’t been any wind like that all day, but the flow triggers anyway—several times a day.

It worked perfectly for over a year before this. I’m not sure what the issue is. Perhaps the values are being read incorrectly? Thanks for any advice!

Today the same mistake: wind 4,5, gust 9,5 and the trigger (wind above 15 km/h) starts. So perhaps the value added both?

I have checked the changes and I can’t see anything that would suggest an error in the code. I even used AI to check and that couldn’t find any issues either.

Could you add a log to the timeline that shows the windspeed when the Flow is triggered:

Could that gust value of 9.5 be miles? Converted, 9.5 miles is equal to 15.29 kilometers, making the trigger “true”.

Can you check the app settings to see what units are selected for wind speed and maybe change them to something else and save then change them back.

Maybe the app is confused about the setting

Thanks for your Idea. But if this is the mistake, than the app translate “gust” into “wind”. The Trigger ist only “wind”.

Thanks, i will test this the next days.

My flow looked like this:

The flow starts even, when wind is under 6 in the stats for wind in android and homey app.

In the Homey App “Widsoll and Ecowitt” and in the android App “Ecowitt” I set “km/h” bei “Windgeschwindigkeit”. There is no setting for gust.

The stats for wind in android and homey app are not over 6 km/h.

But in the Homey App i read:
“windspeedmph”: “3.13”,
“windgustmph”: “4.03”
Is this okay?

Where do you see those?

Gust uses the same units as it is still a wind speed.

I am wondering if it’s the section where the wind speed changes and is > 10 that triggers the flow. I can’t tell from the image if the variable is the Flow tag or the global tag. If it is the Flow tag then it will still be the same value after the delay. So it would only take one reading over 10 to trigger the Flow. If you are trying to detect a constant speed > 10 then you would be better using one of the timer apps and resetting the timer if the speed drops below 10.

I want to close “Markise” when it is longer >10 km/h wind or one time >15 km/h wind. Thanks for the nice flow, i will change to it.

But in the stats there ist the whole time no wind >6 but the “Markise” closed with tag “windy”. Even my flow is wrong with the delay, I dont unterstand while the trigger starts.

I mean the report from the app. There ist wind in mph:

The app expects the data to be in MPH and it then converts it to the selected units for Homey.

The values in the log are just a snapshot that’s updated every 15 seconds. Can you log the speed that triggers the Flow in the status.

Also, look in the insights, but make sure you select the the shortest time scale as Homey averages the data for longer scales, which will smooth out peaks.

I have tested a Flow setup like yours and it’s working as expected for me.

To test if the windspeed was higher for a certain amount of time it can be done with one flow card like this:

( I have windspeed set to m/s).

I keep forgetting the automatically added cards with the timer :grin: