June 21, 2017 at 1:42 pm #46864
Just curious: How’s the plan for v2.1.8 or how the next version will be called? Currently it seems to me that the plans are sorted concerning the upcoming platform. IMHO a basic board with extensions for all communications standards or a fully featured board with all of them is being thought of.
Otherwise 2.1.7 on HW 2.3 just works for me with no hangs or so. Just great.July 22, 2017 at 11:44 pm #47220
Sorry about the delay. I am planning to work on 2.1.8 soon and currently the high priority is to address some of the issues in the firmware for OS 3.0 (such as losing support of static IP, which are not issues for OS 2.3 and earlier versions). There are also bug fixes such as the handling of remote stations when ‘special station auto-refresh’ option is off. In the long term, we do have an extensive todo list (for both OS 3.0 and OS 2.3), which includes features like pause station runs, integration of ET-based weather algorithm, improvements to push notifications and logging, integration with other sensors (including pbecchi’s sensor server) etc. etc. Of course not all can make it to firmware 2.1.8 but we will try to get as much done as possible in a reasonable amount of time.August 21, 2017 at 4:01 am #47484
Sounds good. I’m right back from vacation and in the last weeks my garden was watered by OpenSprinkler and mowed by Robomow. It’s never been more relaxing to return from vacation 🙂
As written, I don’t have any complaints or urgent feature requests so I was just curious about the upcoming features.August 24, 2017 at 3:00 am #47514
I wonder if it would be possible to add the possibility to triggar the rain sensor through the api?
I have My home automation system and a Netatmo weather station with rain sensor. dont want to buy another rain sensor to connect to OpenSprinkler.August 24, 2017 at 3:25 am #47515
“Just” publish your weather data to wunderground.com where OpenSprinkler gets its information from.
The Netatmo stations are natively supported by wunderground and it should be more than easy to include yours:August 24, 2017 at 6:38 am #47517
Cool. Didn’t know that!
Lots of thanks i´ll look into that right away!August 30, 2017 at 4:46 am #47560
I’m keen on the ability to send a web request to IFTTT such that it can be used as a trigger.
i.e. I want a station start/stop to send a web hook to IFTTT to be used as a trigger to control a WeMo switch. Tried using the HTTP station and putting in an IFTTT URL but it didn’t work.
I’ve played with the current IFTTT integrations but they are geared primarily at notifications. Unfortunately the Value1 that is sent is a string of text rather than just a value like StationName. I could probably modify the firmware so that it just sends StationName which might get me the functionality I need, however doing this as a station type of IFTTT (or a modified HTTP station to support IFTTT webhook) would be much cleaner… beyond my coding skills though.September 5, 2017 at 6:51 pm #47593
While you are working towards 2.18, would you mind integrating the Beagle
PIN_FREE_LIST fix (see your post on topic Unable to build Firmware 2.1.7 on OSBo)
No expectation to test (I know Beagle is not longer supported), but there are some 2.17 features I’d really like to see for Beagles in the Unified firmware (without trying to figure out a custom compile 🙂
Thanks!September 18, 2017 at 8:25 am #47757
@metalrooster: you are right that the current IFTTT support in the firmware is mainly geared towards notifications. The reverse direction (i.e. using IFTTT to send commands to OpenSprinkler) actually just requires port forwarding and doesn’t really require firmware support. More specifically, that just relies on the ability of IFTTT server to reach OpenSprinkler, and currently the only way is to go through port forwarding. We actually have a blog post about how to get OpenSprinkler to work with Amazon Echo, through IFTTT:
@wheelw: I believe the PIN_FREE_LIST fix for OSBo is already integrated into the repository:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/commit/b3782487b55416d84910f0a03f32b05497c80b45September 20, 2017 at 12:05 am #47808
@Ray the functionality that I am looking for is a trigger, or the “This” aspect of IFTTT. Port forwarding would result in an action – the “That” functionality of IFTTT. I don’t want to control OpenSprinkler with IFTTT, I want to use OpenSprinkler to control a WeMo switch. IF<Station10 = Start>THEN<WeMo = On>, and IF<Station10 = Stop>THEN<WeMo = Off>October 8, 2017 at 11:21 am #47953
@metalrooster: what you described sounds like is already supported by the HTTP station feature. Specifically, you can set a zone to be an HTTP station, giving it a custom HTTP command to send out upon opening or closing the zone. The physical valve connected to the zone will operate normally, but in addition, the controller will send the HTTP command specified. The HTTP commands are limited to ‘GET” commands — you need to check WeMo’s API to see if you can use HTTP GET commands to turn it on/off.January 1, 2018 at 5:55 pm #48635
Hi Ray – happy new year. Sorry to be a pain, but I was wondering if there is any news on a version with the ET functionality ?February 18, 2018 at 5:18 am #48953
- You must be logged in to reply to this topic.