@Matthew
The illuminence and humidity should have been there already!
They are sent by the ‘capabilities’ and should already be in the lowercase format
Did I miss the ‘sendEvents’ for these?
I did miss lowercase humidity (it was there in your code). However, the sendEvent for lowercase illuminance is not. If you want to add that, I have no other changes. Thanks! Appreciate your work.
I was not getting the Humidity (either upper or lower case) values to show in several dashboards (HousePanel and SmartTiles). Those dashboards show the humidity value as ‘null.’ In looking at examples that did work, it appeared that the humidity being reported by the driver was just the number and did not include the ‘%’ symbol. I altered the driver on lines 163 and 212 to the following:
That just removes the “%” symbol that is included in WeatherUnderground’s relative_humidity attribute. With that change my dashboards now are showing the humidity correctly.
I don’t know if this is unique to my use case or if it should be changed for other’s general use, but thought I would report on what I found.
They both just showed ‘%’ with no number. Those dashboards (HousePanel and SmartTiles) apparently need just the number and they add their own ‘%’ symbol as they both show correctly now (a number with a single ‘%’ at the end) after I removed the ‘%’ from the driver result.
@Matthew
Good find- thanks for that
I have the same issue with this on another thread.
I’ll make the same change to the lowercase setting (I use the uppercase one as my app does not add the %
Yes, the way it is supposed to work is the value should be a number and then a separate “units” setting for “F” or “C” or “%” would get passed to the device event state
That way when retrieving the attribute, you get {value:“58”, unit: “%”}
but most just put the unit in the value… Or override the unit (or ignore it)
I have realised that I can store Illuminance into a variable which means I do not have to define lots of Virtual switches for light levels.
Here is a piston I use to do it.
@bravenel - Any discussions about RM custom commands from weather drivers? For example, I can user @Cobra 's Weather Switch app to pull from a weather driver to trigger a virtual switch, to then trigger a RM rule for TTS to get the condition, but very restrictive and a lot of components for that one action. If we could create Custom Commands to poll any weather driver, and then use the result for TTS or notifications, it would really simplify things.