Thank you Steve, I am up and running with this. Every module is working as it should.
Sorry about this but your imports don't work. I goto Drivers code, click import, paste, and confirm then nothing.. bound to be something stupid I am doing...
Any ideas?
I have had two reports of issues with the links, however I cannot reproduce at all. The simplest suggestion that I can offer is to make sure the entire link is being copied and pasted. Refreshing the download page generates new URL's.
For those experiencing this issue, If you don't mind, please open a ticket and paste in the non-working URL's so I can examine them and try to determine why they're not working.
I ran into this issue and just downloaded the apps and drivers and used cut and paste to get going.
Steve, Poking around in Rule Machine, I see the usual triggers for temperature, humidity, CO2 etc. What I am not seeing is wind direction, speed and gust speed as a trigger. Is that even possible?
Edit: Inches of rain in tenths would be a nice trigger too.
Those attributes are not part of the standard capabilities, so there's no way to select them for automations in RM.
Have a look at WATO.. It allows actions to be taken when specific attribute change,
That might get you the result that you're looking for.
2 Likes
After reading through that thread and getting to the end of it, I discovered that every device attribute is available in Rule Machine as a trigger under custom attribute.
1 Like
Great work @srwhite! Installed the app and everything seems to work perfect for my base, outdoor and additional modules.
Is it possible to get the time in 24h format?
1 Like
What happens if you change Hubitats time format to 24 hr? Settings > Location and Modes.
I already have 24h format in my HE settings and other devices report in 24h.
My Shelly 1:
It is supposed to follow the time format the hub is using. But I see a minor bug that you can easily fix..
On line 397 in the app code,
String formatTs(ts, ds = false) {new Date((long)ts*1000).format((ds ? "MM-dd-yyyy " : "")+(location.timeFormat == 24 ? "HH:mm" : "h:mm aa"), location.timeZone)}
There should be quotes around the number 24. Like this:
String formatTs(ts, ds = false) {new Date((long)ts*1000).format((ds ? "MM-dd-yyyy " : "")+(location.timeFormat == "24" ? "HH:mm" : "h:mm aa"), location.timeZone)}
That'll get the time format rendering correctly. I'll get an update out shortly.
1 Like
Lovely! Thank you for your fast replay.
This is the correct link..
https://hubconnect.to/download/category/5/HubConnect-Netatmo-Weather-Client.html
If you use the search function you'll also pull up the drivers for the old ported community integration of Netatmo. I'll rename those to be more clear in the future.
1 Like
Did you enable oAuth in the Netatmo Client app? Anything in the event logs?
@srwhite oAuth is enabled and the following is what I received
2020-01-28 02:27:27.963 pm errorhttpPost() failed with error
I can delete code and start fresh if you feel that is a good course?
I would reinstall, keeping the logs open in another tab to see if anything failed during the initial setup. It's got to be something super simple.
completely agree, will update shortly.
