[savageautomate]

Absolutely. Moving conversation to Github issue:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/issues/321

(no further comments here…)

Thanks, Robert

[savageautomate]

From: https://opensprinkler.com/forums/topic/announcing-opensprinkler-unified-firmware-2-2-10/#post-79779

For that reason, we didn’t add ‘master off’ but this can be added in the future.

Can we please add that as a feature request?

I am sending ON and OFF signals to a remote location to control my master pump … far beyond hard wiring or WiFi distance. I need a reliable method from OpenSprinkler to know when the master pump is supposed to turn ON or shut OFF. Currently I am using my own long distance radio hardware and I’m polling the OpenSprinkler system against the API method to get the status of all stations every 5 seconds — but this is unnecessarily taxing the OpenSprinkler MCU and sometimes it becomes unresponsive for short periods.

Another helpful feature (at least for me …) would be to flag all the “opensprinkler/station/##” topic MQTT messages as RETAINED. If I had this I could use MQTT as the single source for existing station states. Well .. on second thought, maybe even better than retaining the message would be to set the message expiry on the MQTT message to equal the length of time the station is expected to run for ON states This way the message will remain available to MQTT subscribers while the zone is actively running. This handles a use case where the subscriber connects to the MQTT broker after stations are already actively running and the subscriber would have missed the ON notification message.

Thanks, Robert

[savageautomate]

Just tested this in the the latest firmware (v2.2.1) and I am getting MQTT events for master stations when turning ON stations configured to use the master.
However, I’m not getting the MQTT events for master stations when turning the same stations OFF.

Reported here:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/issues/321

[Author]

Posts