I don’t know since it hasn’t actually had any number in it, but seems to be meters since the visibility, elevation and cloud level are also in the same unit. I’m going to say they report precipitation in meters, which, on the one hand doesn’t make sense when you’re talking about weather but does make sense if you’re trying to standardize to base SI units. But then they also report km/hr which should be m/s in base SI.
A driver update will be pushed out soon, but before I do I want to give everyone a heads up that this update will likely cause your existing devices to have errors. You will have to create new weather devices (with the new driver) using the button at the bottom of the Controls screen. Copy and paste your URLs to the new device and set up the rest of the device Settings (weather source, proxy address & type, and unit conversions).
I apologize for the inconvenience but there will be some benefits to do this such as the new fields I’ve added, plus immediate fixes to all the field labels on the device Controls screen.
Here is a summary of the changes:
Support for Weather Undergound
Correct labels on all fields
Addition of low and high temperatures (current conditions & forecast)
Addition of wind gust (current conditions & forecast)
More consistent setting of fields to 0 when no data is available
Changeout of dew point field to use SmartThings stock capability
Addition of unit conversion option of Pascals for received barometric pressure data (needed for US Gov)
Addition of unit conversion option of meters/hr for received precip data (needed for US Gov)
Removal of Refresh button: manual refresh can now be initiated with a standard swipedown gesture on the Controls screen
Removal of Dark Sky as Settings option
Removal of UV index field
One outstanding issue is that some fields are still not showing the units value. This is related to the SmartThings platform change that caused the labels to no longer work. Fix is TBD.
I will post again once I push the driver out, but be forewarned that once you have the new driver, you’ll need to create new devices.
You’re asking specifically about edgebridge. And the answer is that there should be no problem running it along side other server apps on your Pi- regardless of whether you are running it inside Docker or not. Just make sure there are no conflicts in the ports being used. And if running inside Docker, be sure to configure your Docker container to enable the port for edgebridge (which defaults to 8088).
Once you confirm the new driver version is on your hub, you can create new devices, and when you have finished copying over your device settings from your prior devices, you can delete the prior devices.
Please report any problems or anomalies you see in reported values.
OK guys, something fishy is going on. You are not doing anything wrong. I checked the channel and it still was showing the previous driver version! I’ve just pushed out again the updated driver and confirmed that it is showing up on the channel now: