Glad it’s working for you. I did make a minor change a while back that should detect trends more quickly, but it’s still a very simplistic algorithm (which I think is intentional).
I would loke to translate in Italian pressure trend with transformation, can you please let me know all values that pressure trend can display in english so I can made my transformation file.
The values are -2, -1, 0, 1 and 2
I need to know numeric values at witch trend correspond
-2=Rapidly Falling -1=Slowly Falling 0=Steady 1=Slowly Rising 2=Rapidly Rising
I’ve posted a new version of the Weather Calculations binding built for OpenHAB 2.4.0 to the download site above. I’ve been running it for about 2 weeks and it seems to be stable.
There are no new features from the previous release in September, this is just a recompile against the 2.4.0 release.
This is basically the level of functionality that I’d hoped to achieve when I started working on this binding. If anyone has any further feature requests, please let me know.
As always, feel free to let me know if you have any questions or comments!
Thank you, have you considered publishing the binding in the market place?
I have been trying to decide what the best approach is: continuing to prepare builds myself and use the marketplace, or contribute the binding directly to OpenHAB (assuming they’d have it). The latter is probably the best approach but I don’t really have much time to devote to that process and the inevitable changes that would be required before it could be contributed.
I have an implementation of dew point implemented in rules, is this something that can be done with this binding? I consider code for calculating stuff like this library functionality, but maybe that is most easiest implemented as a binding? I don’t know.
But in addition to calculating dew point from temperature and humidity sensors, I also calculate entalpy, specific entalpy and mixing ratios, in Python with help from the metpy.calc module. This might also be something the binding could support?
The Weather calculations binding includes dew point calculation, so you’d be able to use it directly.
The idea of this binding is to have a centralized place to generate derived weather calculations so that weather station bindings don’t individually have to recreate these data points; they can simply focus on providing the sensor data they have access to. When you set this binding up, each of the derived calculations (like dew point, or sea level pressure) becomes available as an item you can use in any way you want. The values are updated only when one of the values that are used to calculate it are updated, so the experience is very seamless once you set everything up.
Right now, these are the calculations that are available (assuming you have temperature, pressure humidity and optionally wind speed items):
Sea Level Pressure
I don’t see any problem with adding additional calculations, provided that there’s a good reference for how the calculation is made. Suggestions are welcome!
I like the sound of this - looking to exploit dewpoint calculation. It’s in a storage business, monitoring separate warehouse spaces. For example, internal humidity + external temperature tells us when there’s a risk of condensation on metal walls.
More normal OH users may want this kind of thing for e.g. garage and greenhouse spaces.
For this (ab)use, I’d want multiple Things (“stations”) which may not be what you have in mind of course
Also no pressure sensor channel, i.e. that should be optional for me.
It’s moving away from the original weather station concept but I think has utility for OH users with common temp/RH sensors.
In my particular use, there are “alarm” thresholds of course. Such things can be done by rules fairly easily, and the user then gets to choose the tuning like hysteresis. It’s just a thought to incorporate high/low alarms.
I think right now that pressure is a required field; I can look into making it optional, though that may take a little time for me to get around to. Alternately, you can create a dummy pressure item to satisfy the requirement that there be one… since it’s not used in the dew point calculation, the fact that it isn’t a real value and never changes shouldn’t be a problem.
It should certainly be possible to support multiple stations: just create a weather calculation thing for each station and assign that station’s sensor items to the proper weather calculation thing.
Once you have a dew point item, you can do any of the normal things you want with the data (i.e. have rules against the value). I like the idea of pre-canned rule triggers, but I’m not sure the infrastructure is in place to make that happen easily. For now, making your own rules is probably the way to go.
Aha, I should give it a try with multiple Things then
Yup, it was just a future idea. There would be a fair amount of overhead setting it up, because folk would inevitably want adjustable hysteresis as well as adjustable target in-flight, more targets than just max/min levels, etc.
I’ll make an Enhancement Request for pressure to go optional. At any future tinkering - as you say, easily circumvented for now.