Have a look at this document. This is how I installed it when I set my openhab2 install.
You don’t have to use the new rules engine, it’s a module that just sits along side the existing rules engine. I haven’t had any problems having it enabled myself.
Thanks very much Bill, this works!
I will try now to map the other forecast.
The only thing that i miss still very much is method for -live- wind direction and spee data, to be able to make 360deg compass/wind rose, that would look similiar like in the WF app.
You should be able to use the “rapid wind event” trigger to create a rule that updates some item when the hub broadcasts the update. I don’t have the exact code to do it, but here’s an example that sends a notification when the momentary wind exceeds a threshold:
You’d probably just need to modify this rule to update your desired wind speed and direction items (note that the sky/tempest doesn’t have momentary wind, as that’s not sent from the observation data). A quick search of the community website has lots of examples of how to do that in a rule. Maybe the long term solution is to add new items for that, but the downside would be a lot of extra data if you’re persisting that, such as for graphing purposes.
I found a typo in the current version of the binding that would prevent the rule from triggering. I’ve fixed that and tested that it works now. I also added an example that updates an item with the wind speed every time a rapid wind event is received. You can do the same with the wind direction, it’s in the field called “windDirection”.
I’ve been having an issue that may be self inflicted. While my Tempest reports rain (and so does the binding), the accumulation never rises above 0.0 in. It could be that I have set the wrong item type to the channel, but I would think that even in that case, I would still see what the channel thinks the current accumulation is, and I would also expect there to be a message in the logs about a failed conversion. The interesting thing is that I see rain accumulation data hit the logs in openhab, so I’m wondering if there is a disconnect between the reception, and storing/reporting of the data in the binding.
I also have no information (null) for all of the weatherflow hub channels, but that is less of a concern to me personally. Finally, I have also noticed that the lightning strike count will go up, but it seems to zero itself out pretty quickly (I think today it was gone within an hour). This may be why others are not seeing their strikes go up.
If you have any advice or thoughts, I’d be happy to try whatever you suggest. I’d also be happy to guinea pig any code. I’m hoping to get to the point where I can help debug, but my Tempest is on a separate VLAN from my dev machine so I still need to get the networking set up before I can be any use there.
Hi all,
So have had this binding installed for about a week or so, and it seems to work great. But I saw today, that my log spits out this twice every minute. Haven’t seen them before, which is strange.
14:03:35.549 [WARN ] [eatherflowsmartweather.util.UdpServer] - UdpServer.Listener org.openhab.binding.weatherflowsmartweather.internal.SmartWeatherUDPListenerServiceImpl$1@3357cac6 threw an exception: Task java.util.concurrent.ScheduledThreadPoolExecutor$Schedul
edFutureTask@64b2f18e[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@703bc783[Wrapped task = org.openhab.binding.weatherflowsmartweather.handler.SmartWeatherTempestHandler$1@361e06cc]] rejected from org.openhab.core.internal.common.WrappedS
cheduledExecutorService@49581c3e[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 560]
The Weatherflow local API reports rainfall increments but not totals; it’s a bit confusing because it looks like the data is provided, but it’s always just zero. To get a useful value, you need to total things up. There are a bunch of ways to do that, but the easiest is probably to use the WeatherCalculations binding that I wrote. It provides a number of “calculated” observations including total rainfall amounts for today and yesterday. If you look back through this thread or do a search, you should find a link to that.
It’s possible that the lightning strike data is similar; to be honest I haven’t really looked at it. One thing you might not be aware of is that there are some custom rule triggers supplied with this binding. These triggers can be used to fire rules when, for example, a lightning strike is reported. I think I’ve got a post further up in the thread that talks about this, and I’ve got an example using the RapidWind trigger here:
I don’t have a good answer for your hub channels having no data; I’m pretty sure my pre-Tempest setup is reporting data and I don’t think the hub changed. Are you getting any data in the logs? I think you should at least be getting log entries showing that the messages are being received.
Do you have the full exception in your log files? I think that will be needed to know exactly what’s happening, but I suspect it has to do with the online/offline handler:
Every time a message is received from your tempest, we set a timer a few minutes out that will mark the Tempest unit offline. If a message is received before that (normally they arrive every 30-60 seconds), we remove that timer and set a new one. It’s possible something there is going wrong. I don’t think I get those in my Sky/Air setup, but I’ll look this weekend.
If you’re not seeing any other side effects, it’s probably not a major problem, just that the online/offline indicator might not work properly. Still, I’d like to get it sorted out. If you happen to be able to capture more data from the logs, that’d be helpful!
So for me, it got worse in other places of OH, same/similar issue, but no longer a warning. I googled, and found other having had the same issue, where a restart of their boxes/VMs cured the problem. While it sounded so-so to me, I also tried this, and it went away(!). I suppose some update made some kind of incompatibility in the java subsystem.
Anyway I have not seen this since the restart so I think we can put this issue to sleep.
Thanks!
i’ve created a rule to fire when precipitation starts. but the rule wont fire.
when i change the trigger to rapid wind it will work. i already installed your newest addon file on your git.
It looks like a piece of identifying information was left out of those events, causing them to be ignored by the rule trigger. I’ve posted a new version that works again. Please give it a try and let me know if you still have problems.
Unfortunately, the ability to trigger on these events is only available with the new rules engine. I’m not sure if/how you can specify new rules using text configs (other than saying that there’s a code tab in the UI that allows you to modify the rule configuration textually. There might be some information in the forums elsewhere that covers this topic.
I am running OH2.5.12 and after a couple power downs in our House, I have problems to get data from my weather station.
In the Log file it say:
2022-04-24 21:01:15.791 [WARN ] [ather.handler.SmartWeatherHubHandler] - rapid wind observation but not for us.
2022-04-24 21:01:15.847 [WARN ] [ather.handler.SmartWeatherHubHandler] - device status but not for us: weatherflowsmartweather:tempest:HB-00041084:ST-00023261
2022-04-24 21:01:15.980 [WARN ] [ather.handler.SmartWeatherHubHandler] - tempest observation but not for us.
What does it mean: Not for us ??
It worked in the past and I did not change any settings on my weather station.
any ideas ?
Just set up my Tempest station today, and trying to get this plugin working. It auto-finds the hub and station perfectly, but after I add the found “SmartWeather Tempest” Thing, I get a bunch of channel errors logged:
I haven’t seen this sort of error before; those are all standard channel types that are defined in the binding configuration. Technically, I suppose using a 3.3.0 binding on a 3.2.0 installation could cause problems.
I built a copy of the binding against the 3.2.0 release and have uploaded it here:
You’ll need to remove the existing version by removing the file from your adding directory and then doing a “bundle:uninstall” with the bundle id (you can find this by using bundle:list). Once that’s done, you should be able to drop the new version in your addons directory. For good measure, you may want to restart openhab before you do that last step.
Let me know if you have any better luck with the 3.2.0 version.
Thanks Bill! Tried out the 3.2 version, but got the same results (unable to add channels).
But after adding the Hub Thing, I either got a new set of channel-related errors or I missed them the first time:
2022-06-21 15:14:58.308 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'temperature', because channel type 'weatherflowsmartweather:airTemperature' could not be found.
2022-06-21 15:14:58.313 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'pressure', because channel type 'weatherflowsmartweather:pressure' could not be found.
2022-06-21 15:14:58.317 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'humidity', because channel type 'weatherflowsmartweather:humidity' could not be found.
2022-06-21 15:14:58.322 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'strike_count', because channel type 'weatherflowsmartweather:count' could not be found.
2022-06-21 15:14:58.326 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'strike_distance', because channel type 'weatherflowsmartweather:distance' could not be found.
2022-06-21 15:14:58.331 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'illuminance', because channel type 'weatherflowsmartweather:illuminance' could not be found.
2022-06-21 15:14:58.335 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'uv', because channel type 'weatherflowsmartweather:uv' could not be found.
2022-06-21 15:14:58.340 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'rain_accumulated', because channel type 'weatherflowsmartweather:rain_accumulated' could not be found.
2022-06-21 15:14:58.344 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'wind_lull', because channel type 'weatherflowsmartweather:wind_lull' could not be found.
2022-06-21 15:14:58.349 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'wind_avg', because channel type 'weatherflowsmartweather:wind_avg' could not be found.
2022-06-21 15:14:58.353 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'wind_gust', because channel type 'weatherflowsmartweather:wind_gust' could not be found.
2022-06-21 15:14:58.358 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'wind_direction', because channel type 'weatherflowsmartweather:wind_direction' could not be found.
2022-06-21 15:14:58.362 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'report_interval', because channel type 'weatherflowsmartweather:report_interval' could not be found.
2022-06-21 15:14:58.366 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'solar_radiation', because channel type 'weatherflowsmartweather:solar_radiation' could not be found.
2022-06-21 15:14:58.371 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'precipitation_type', because channel type 'weatherflowsmartweather:precipitation_type' could not be found.
2022-06-21 15:14:58.375 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'wind_sample_interval', because channel type 'weatherflowsmartweather:wind_sample_interval' could not be found.
2022-06-21 15:14:58.383 [WARN ] [re.thing.internal.ThingFactoryHelper] - Could not create channel 'battery_level', because channel type 'weatherflowsmartweather:battery_level' could not be found.
Then, when I added the Tempest Thing I got the same errors I first reported.