That relies on WU, can it integrate into Netatmo?
Not quite...
WS will work with any weather driver or device that presents the correct attributes
Which specific attributes do you want to switch with?
I can possibly add a few if WS doesn’t work for you.
If you have the driver code for Netatmo, why not just change the attribute to ‘standard’ ones that all the apps (inc WS) use?
Andy
I don’t mind adding a couple of missing attributes but your drivers just use different names for most of them.
I’m sorry but I don’t have the time to completely rewrite the app just for you
Why don’t you just rename the attributes that the driver presents?
Ok. Tell me how they lineup with tour attributes?
Rather than hijack this thread any more than we have done.
I have created a new thread here:
4 Likes
This bug was fixed in the last release, 1.1.2.
How would I make rule that :
Turns Kitchen light off if there is no Motion from kitchen motion sensor for 15 minutes and if the Kitchen Light switch is on ?
2 Likes
Thanks
1 Like
Thanks Bruce,
I was thinking this was not going to work since I reverted my firmware 2/2 my lock issues. To my happy surprise both the cloud and local endpoints are working great. This should allow me shutdown the final piston I am using in webcore.
I also should now be able to trigger presence based automatons through tasker, since Life 360 has been giving me trouble this is doubly great news.
Thanks to everyone at the Hubitat team. Not that my opinion matters so much but, what you guys have created here in such a short time is very impressive.
2 Likes
@bravenel Actions are an awesome feature of RM, it has allowed me to create a rule once and reuse it multiple times. I noticed that actions have the restrictions available when creating/editing however they don’t appear to be evaluated. I was hoping to have a trigger rule that calls 2 actions but I only want one of the actions to run if a virtual switch is on. I would prefer not to setup 2 trigger rules and just use the restrictions of the action.
Any chance you would be willing to make this work? Thanks in advance for your consideration.
Restrictions should work for Actions if specified in the action itself. If that's not the case, it would (a) be surprising, and (b) be a bug.
You didn't define the Rule, just as the error states.
A rule must have conditions, and define the logic to apply to those conditions.
For this use case, you should use a trigger instead of a rule.
Your rule is incomplete. Need to define the rule. Right now you just have conditions and actions for true but you are missing how the conditions are use to evaluate the rule.
Thanks, i will change it to a trigger! Im so used to webcore haha
I've just updated to 1.1.3.114, and still getting used to RM. I have set a a rule for presence and departing / arriving etc. as per below. This is triggering as I get the pushover message, and I see my virtual Cams switch set on or off.
However, the mode is never set to Away, and I'm seeing an error in the IFTTT trigger to set my cams to Auto detection. Now this was working earlier prior to upgrading, not the Rule, thats new, but the turning on / off of the Cams virtual switch.
Any tips for whats happening here?
TIA
**Edit - Current Mode has now just set to Away.
1 Like
I have recreated the rule and actions and now I am a happy camper. The action restrictions are working. Thanks for including this feature.
How can i check if it's raining with a weatherunderground device? Want to check if it's raining and if any windows are open.
