search

sfeakes / SprinklerD

Sprinkler controller for use with home automation hubs, HomeKit & MQTT
Other
25 stars 5 forks source link

Step by step raspberry pi and HomeKit #2

Closed toshibochan closed 5 years ago

toshibochan commented 5 years ago

Hi thanks for developing this great sprinkler system! I be very happy if you can do step by step installation for raspberry pi and HomeKit. Plus if have YouTube video to. I don’t know much coding so be super super helpful for me. Thank you.

toshibochan commented 5 years ago

I was able to install the sprinkler but scheduled not working. And I’m trying install homebridge but give me error. Please help.

sfeakes commented 5 years ago

The schedule is done through linux cron. cron will take a minute or two to sort out it's schedule, so while testing don't schedule it to do something 1 minute in the future. Make sure it's at least 3 mins in the future. If that doesn't fix it can you post information from /var/log/messages from the time when the schedule was supposed to run.

toshibochan commented 5 years ago

When I run sudo ./release/install.sh Give this: Please enabled cron.d support, if not the calendar will not work Edit /etc/default/cron and look for the -l option Created symlink /etc/systemd/system/multi-user.target.wants/sprinklerd.service → /etc/systemd/system/sprinklerd.service.

I did enable cron but I don’t understand what to do with:

Created symlink /etc/systemd/system/multi-user.target.wants/sprinklerd.service → /etc/systemd/system/sprinklerd.service.

toshibochan commented 5 years ago

I post a question on homebridge-sprinkled page please take look when you have time please.

toshibochan commented 5 years ago

Schedule is working now thanks

toshibochan commented 5 years ago

For HomeKit work I need to install mqtt in my pi?

sfeakes commented 5 years ago

Yes, you do need to install MQTT / Mosquitto. I've updated the instructions.

toshibochan commented 5 years ago

Thanks for update! Have on error in there:

Install HomeBridge-SprinklerD

See https://github.com/sfeakes/homebridge-sprinklerd for package content

sudo npm install -g homebridge-aqualinkd

Is not aqualinkd.

toshibochan commented 5 years ago

After install mosquito how to setup mosquito and start the mosquito?

toshibochan commented 5 years ago

this message just show and show and never stop:

Notice: Starting MQTT client to trident:1883 Info: Connected to mqtt trident:1883 with id of: sprinklerd_b827eb94711c Warning:MQTT Connection closed Notice: MQTT client stopped

I have to open port 1883 on the router?

sfeakes commented 5 years ago

Thanks, I've fixed the aqualinkd vs sprinklerd typo.

The MQTT client stopped is not normal if it doesn't re-start again. MQTT connection can break when wifi connection stops and starts again, so if you see the MQTT connection disconnecting and re-starting that's normal as long as it doesn't do it too often. (Once every 5 or 10 mins).

toshibochan commented 5 years ago

this message just show and show and never stop:

Notice: Starting MQTT client to trident:1883 Info: Connected to mqtt trident:1883 with id of: sprinklerd_b827eb94711c Warning:MQTT Connection closed Notice: MQTT client stopped

I have to open port 1883 on the router?

sfeakes commented 5 years ago

No, your router is to the outside world, you shouldn’t open that port since it’s all local. Arr, you are trying to connect to mosquitto on a machine named trident, that should probably be localhost. Look at the sprinklerd.conf file and change the MQTT settings to the machine running mosquitto.

toshibochan commented 5 years ago

You can share your sprinklerd.config file?

toshibochan commented 5 years ago

I was able to connect to mosquitto but now new error: Debug: MQTT: topic sprinklerd/zone1/set 1 Debug: MQTT: pt2 zone1/set1ngduration0@ Debug: Request to turn zone 1 on for 0 min requesttype 1 Info: Stopping! And crash

sfeakes commented 5 years ago

Can you post config and complete log file. Looks like there is a buffer overflow reading the topic from MQTT that’s causing the issue. I’d need to see the log to confirm and fix if necessary.

toshibochan commented 5 years ago

Where log file is storage?

toshibochan commented 5 years ago

[SPRINKLERD] PORT=105 NAME=My Sprinklers DOCUMENTROOT = /var/www/sprinklerd CACHE = /var/cache/sprinklerd.cache

The log level. [DEBUG, INFO, NOTICE, WARNING, ERROR]

LOG_LEVEL = DEBUG LOG_LEVEL = NOTICE

mqtt stuff MQTT_ADDRESS = 10.0.1.107:1883

MQTT_USER = username

MQTT_PASSWD = password

MQT_TOPIC = sprinklerd

MQTT_DZ_PUB_TOPIC = domoticz/in

MQTT_DZ_SUB_TOPIC = domoticz/out

DZIDX_CALENDAR = 197

DZIDX_24HDELAY = 198

DZIDX_ALL_ZONES = 199

DZIDX_RAINSENSOR = 48

Options for the below ZONE and GPIO configuration

#

LOW 0

HIGH 1

#

PUD_OFF 0

PUD_DOWN 1

PUD_UP 2

NAME = name of zone

GPIO_PIN = GPIO Pin # This is WiringPi Pin#, not Raspberry Pi board pin#.

WPI_PIN = use instead of GPIO_PIN if compiled with USE_WIRINGPI flag

GPIO_PULL_UPDN = setup pull up pull down resistor PUD_OFF|PUD_DOWN|PUD_UP

GPIO_ON_STATE = State GPIO reads when relay for zone is on. HIGH or LOW 1 or 0

DOMOTICZ_IDX = Domoticz IDX 0 or remove entry if you don;t use Domoticz (only if you use domoticz)

MASTER_VALVE = YES=1 NO=0 // turn on with any zone

Don't use ZONE:0 for anything other than master valve, if you don't have a master valve simply delete it and start from ZONE:1

[ZONE] [ZONE:0] NAME=Master Valve MASTER_VALVE=0 GPIO_PIN=17 WPI_PIN=0 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0

[ZONE:1] NAME=Island DEFAULT_RUNTIME=10 GPIO_PIN=18 WPI_PIN=1 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=200

[ZONE:2] NAME=Driveway DEFAULT_RUNTIME=10 GPIO_PIN=27 WPI_PIN=2 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=201

[ZONE:3] NAME=Diningroom Flowerbeds DEFAULT_RUNTIME=10 GPIO_PIN=22 WPI_PIN=3 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=202

[ZONE:4] NAME=Front Flowerbeds DEFAULT_RUNTIME=10 GPIO_PIN=23 WPI_PIN=4 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=203

[ZONE:5] NAME=Backgarden Left DEFAULT_RUNTIME=10 GPIO_PIN=24 WPI_PIN=5 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=204

[ZONE:6] NAME=Backgarden Right DEFAULT_RUNTIME=10 GPIO_PIN=25 WPI_PIN=6 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=205

[ZONE:7] NAME=Garage Flowerbeds DEFAULT_RUNTIME=10 GPIO_PIN=5 WPI_PIN=21 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=206

[ZONE:8] NAME=Golfcart path DEFAULT_RUNTIME=10 GPIO_PIN=6 WPI_PIN=22 GPIO_PULL_UPDN=1 GPIO_ON_STATE=0 DOMOTICZ_IDX=207

toshibochan commented 5 years ago

Debug: Config mqtt_topic 'sprinklerd' Debug: Config mqtt_dz_pub_topic '' Debug: Config mqtt_dz_sub_topic '' Info: Name = My Sprinklers Info: Port = 105 Info: Docroot = /var/www/sprinklerd Debug: Found 8 ZONES Debug: ZONE = 0 Debug: Zone Config : Master Valve PIN : 17 Set pull up/down : 1 ON state : 0 Master valve : 0 Domoticz IDX : -1 Debug: ZONE = 1 Debug: Zone Config : Island PIN : 18 Set pull up/down : 1 ON state : 0 Master valve : 111 Domoticz IDX : 200 Debug: ZONE = 2 Debug: Zone Config : Driveway PIN : 27 Set pull up/down : 1 ON state : 0 Master valve : 84 Domoticz IDX : 201 Debug: ZONE = 3 Debug: Zone Config : Diningroom Flowerbeds PIN : 22 Set pull up/down : 1 ON state : 0 Master valve : 97 Domoticz IDX : 202 Debug: ZONE = 4 Debug: Zone Config : Front Flowerbeds PIN : 23 Set pull up/down : 1 ON state : 0 Master valve : 73 Domoticz IDX : 203 Debug: ZONE = 5 Debug: Zone Config : Backgarden Left PIN : 24 Set pull up/down : 1 ON state : 0 Master valve : 100 Domoticz IDX : 204 Debug: ZONE = 6 Debug: Zone Config : Backgarden Right PIN : 25 Set pull up/down : 1 ON state : 0 Master valve : 10 Domoticz IDX : 205 Debug: ZONE = 7 Debug: Zone Config : Garage Flowerbeds PIN : 5 Set pull up/down : 1 ON state : 0 Master valve : 35 Domoticz IDX : 206 Debug: ZONE = 8 Debug: Zone Config : Golfcart path PIN : 6 Set pull up/down : 1 ON state : 0 Master valve : 79 Domoticz IDX : 207 Notice: Starting sprinklerd version 1.0b Debug: regexp no match (1) Debug: Read from cron Day 6 | Time 22:53 | Zone 1 | Runtime 1 Debug: Read from cron Day 6 | Time 22:54 | Zone 2 | Runtime 1 Debug: regexp no match (1) Debug: regexp no match (1) Debug: regexp no match (1) Debug: Read Calendar 'OFF' from cache Debug: Read delay24h 'OFF' from cache Debug: Read delay24h endtime '0' from cache Debug: Read Chance of Rain delay '0' from cache Debug: Read Rain 1d delay '0.000000'in from cache Debug: Read Rain 2d delay '0.000000'in from cache Debug: Read default_runtime '10' for zone 1 Debug: Read default_runtime '10' for zone 2 Debug: Read default_runtime '10' for zone 3 Debug: Read default_runtime '10' for zone 4 Debug: Read default_runtime '10' for zone 5 Debug: Read default_runtime '10' for zone 6 Debug: Read default_runtime '10' for zone 7 Debug: Read default_runtime '10' for zone 8 Debug: Running sprinklerd with options :- daemon=0, verbose=0, httpdport=105, debug2file=0 configfile=/etc/sprinklerd.conf Debug: Setting up GPIO Debug: piBoardId: Revision string: Revision : a020d3 Debug: Setting up Zone 0 Debug: Set GPIO 17 to OUTPUT Debug: Setting up Zone 1 Debug: Set GPIO 18 to OUTPUT Debug: Setting up Zone 2 Debug: Set GPIO 27 to OUTPUT Debug: Setting up Zone 3 Debug: Set GPIO 22 to OUTPUT Debug: Setting up Zone 4 Debug: Set GPIO 23 to OUTPUT Debug: Setting up Zone 5 Debug: Set GPIO 24 to OUTPUT Debug: Setting up Zone 6 Debug: Set GPIO 25 to OUTPUT Debug: Setting up Zone 7 Debug: Set GPIO 5 to OUTPUT Debug: Setting up Zone 8 Debug: Set GPIO 6 to OUTPUT Debug: GPIO setup complete Debug: Starting HTTPD Notice: Starting web server on port 105 Debug: MQTTaq 1 | MQTTdz 0 Debug: MQTTaq 1 | MQTTdz 0 Notice: Starting MQTT client to 10.0.1.107:1883 Info: Connected to mqtt 10.0.1.107:1883 with id of: sprinklerd_b827eb94711c Info: MQTT: Subscribing to 'sprinklerd/#' Info: MQTT: Published id=1: sprinklerd/zone0 0 Info: MQTT: Published id=2: sprinklerd/zone0/duration 600 Info: MQTT: Published id=3: sprinklerd/zone0/remainingduration 0 Info: MQTT: Published id=4: sprinklerd/zone1 0 Info: MQTT: Published id=5: sprinklerd/zone1/duration 600 Info: MQTT: Published id=6: sprinklerd/zone1/remainingduration 0 Info: MQTT: Published id=7: sprinklerd/zone2 0 Info: MQTT: Published id=8: sprinklerd/zone2/duration 600 Info: MQTT: Published id=9: sprinklerd/zone2/remainingduration 0 Info: MQTT: Published id=10: sprinklerd/zone3 0 Info: MQTT: Published id=11: sprinklerd/zone3/duration 600 Info: MQTT: Published id=12: sprinklerd/zone3/remainingduration 0 Info: MQTT: Published id=13: sprinklerd/zone4 0 Info: MQTT: Published id=14: sprinklerd/zone4/duration 600 Info: MQTT: Published id=15: sprinklerd/zone4/remainingduration 0 Info: MQTT: Published id=16: sprinklerd/zone5 0 Info: MQTT: Published id=17: sprinklerd/zone5/duration 600 Info: MQTT: Published id=18: sprinklerd/zone5/remainingduration 0 Info: MQTT: Published id=19: sprinklerd/zone6 0 Info: MQTT: Published id=20: sprinklerd/zone6/duration 600 Info: MQTT: Published id=21: sprinklerd/zone6/remainingduration 0 Info: MQTT: Published id=22: sprinklerd/zone7 0 Info: MQTT: Published id=23: sprinklerd/zone7/duration 600 Info: MQTT: Published id=24: sprinklerd/zone7/remainingduration 0 Info: MQTT: Published id=25: sprinklerd/zone8 0 Info: MQTT: Published id=26: sprinklerd/zone8/duration 600 Info: MQTT: Published id=27: sprinklerd/zone8/remainingduration 0 Info: MQTT: Published id=28: sprinklerd/calendar 0 Info: MQTT: Published id=29: sprinklerd/24hdelay 0 Info: MQTT: Published id=30: sprinklerd/cycleallzones 0 Info: MQTT: Published id=31: sprinklerd/status OFF Debug: MQTT: topic sprinklerd/zone0 0 Debug: MQTT: pt2 zone001 Debug: MQTT: Unknown topic sprinklerd/zone0 0 Debug: MQTT: topic sprinklerd/zone0/duration 600 Debug: MQTT: pt2 zone0/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone0/duration 600 Debug: MQTT: topic sprinklerd/zone0/remainingduration 0 Debug: MQTT: pt2 zone0/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone0/remainingduration 0 Debug: MQTT: topic sprinklerd/zone1 0 Debug: MQTT: pt2 zone101 Debug: MQTT: Unknown topic sprinklerd/zone1 0 Debug: MQTT: topic sprinklerd/zone1/duration 600 Debug: MQTT: pt2 zone1/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone1/duration 600 Debug: MQTT: topic sprinklerd/zone1/remainingduration 0 Debug: MQTT: pt2 zone1/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone1/remainingduration 0 Debug: MQTT: topic sprinklerd/zone2 0 Debug: MQTT: pt2 zone201 Debug: MQTT: Unknown topic sprinklerd/zone2 0 Debug: MQTT: topic sprinklerd/zone2/duration 600 Debug: MQTT: pt2 zone2/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone2/duration 600 Debug: MQTT: topic sprinklerd/zone2/remainingduration 0 Debug: MQTT: pt2 zone2/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone2/remainingduration 0 Debug: MQTT: topic sprinklerd/zone3 0 Debug: MQTT: pt2 zone301 Debug: MQTT: Unknown topic sprinklerd/zone3 0 Debug: MQTT: topic sprinklerd/zone3/duration 600 Debug: MQTT: pt2 zone3/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone3/duration 600 Debug: MQTT: topic sprinklerd/zone3/remainingduration 0 Debug: MQTT: pt2 zone3/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone3/remainingduration 0 Debug: MQTT: topic sprinklerd/zone4 0 Debug: MQTT: pt2 zone401 Debug: MQTT: Unknown topic sprinklerd/zone4 0 Debug: MQTT: topic sprinklerd/zone4/duration 600 Debug: MQTT: pt2 zone4/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone4/duration 600 Debug: MQTT: topic sprinklerd/zone4/remainingduration 0 Debug: MQTT: pt2 zone4/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone4/remainingduration 0 Debug: MQTT: topic sprinklerd/zone5 0 Debug: MQTT: pt2 zone501 Debug: MQTT: Unknown topic sprinklerd/zone5 0 Debug: MQTT: topic sprinklerd/zone5/duration 600 Debug: MQTT: pt2 zone5/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone5/duration 600 Debug: MQTT: topic sprinklerd/zone5/remainingduration 0 Debug: MQTT: pt2 zone5/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone5/remainingduration 0 Debug: MQTT: topic sprinklerd/zone6 0 Debug: MQTT: pt2 zone601 Debug: MQTT: Unknown topic sprinklerd/zone6 0 Debug: MQTT: topic sprinklerd/zone6/duration 600 Debug: MQTT: pt2 zone6/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone6/duration 600 Debug: MQTT: topic sprinklerd/zone6/remainingduration 0 Debug: MQTT: pt2 zone6/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone6/remainingduration 0 Debug: MQTT: topic sprinklerd/zone7 0 Debug: MQTT: pt2 zone701 Debug: MQTT: Unknown topic sprinklerd/zone7 0 Debug: MQTT: topic sprinklerd/zone7/duration 600 Debug: MQTT: pt2 zone7/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone7/duration 600 Debug: MQTT: topic sprinklerd/zone7/remainingduration 0 Debug: MQTT: pt2 zone7/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone7/remainingduration 0 Debug: MQTT: topic sprinklerd/zone8 0 Debug: MQTT: pt2 zone801 Debug: MQTT: Unknown topic sprinklerd/zone8 0 Debug: MQTT: topic sprinklerd/zone8/duration 600 Debug: MQTT: pt2 zone8/duration6001% Debug: MQTT: Unknown topic sprinklerd/zone8/duration 600 Debug: MQTT: topic sprinklerd/zone8/remainingduration 0 Debug: MQTT: pt2 zone8/remainingduration01 Debug: MQTT: Unknown topic sprinklerd/zone8/remainingduration 0 Debug: MQTT: topic sprinklerd/calendar 0 Debug: MQTT: pt2 calendar01 Debug: MQTT: Unknown topic sprinklerd/calendar 0 Debug: MQTT: topic sprinklerd/24hdelay 0 Debug: MQTT: pt2 24hdelay01 Debug: MQTT: Unknown topic sprinklerd/24hdelay 0 Debug: MQTT: topic sprinklerd/cycleallzones 0 Debug: MQTT: pt2 cycleallzones01 Debug: MQTT: Unknown topic sprinklerd/cycleallzones 0 Debug: MQTT: topic sprinklerd/status OFF Debug: MQTT: pt2 statusOFF1 Debug: MQTT: Unknown topic sprinklerd/status OFF Debug: MQTT: topic sprinklerd/active Zone 1 Debug: MQTT: pt2 activeZone 1@ Debug: MQTT: Unknown topic sprinklerd/active Zone 1 Debug: Message publishing acknowledged (msg_id: 1) Debug: MQTT: received (msg_id: 1), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 2) Debug: MQTT: received (msg_id: 2), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 3) Debug: MQTT: topic sprinklerd/zone0/remainingduration 0 Debug: MQTT: pt2 zone0/remainingduration0@ Debug: MQTT: Unknown topic sprinklerd/zone0/remainingduration 0 Debug: Message publishing acknowledged (msg_id: 4) Debug: MQTT: received (msg_id: 4), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 5) Debug: MQTT: received (msg_id: 5), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 6) Debug: MQTT: received (msg_id: 6), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 7) Debug: MQTT: received (msg_id: 7), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 8) Debug: MQTT: received (msg_id: 8), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 9) Debug: MQTT: received (msg_id: 9), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 10) Debug: MQTT: received (msg_id: 10), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 11) Debug: MQTT: received (msg_id: 11), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 12) Debug: MQTT: received (msg_id: 12), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 13) Debug: MQTT: received (msg_id: 13), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 14) Debug: MQTT: received (msg_id: 14), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 15) Debug: MQTT: received (msg_id: 15), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 16) Debug: MQTT: received (msg_id: 16), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 17) Debug: MQTT: received (msg_id: 17), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 18) Debug: MQTT: received (msg_id: 18), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 19) Debug: MQTT: received (msg_id: 19), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 20) Debug: MQTT: received (msg_id: 20), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 21) Debug: MQTT: received (msg_id: 21), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 22) Debug: MQTT: received (msg_id: 22), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 23) Debug: MQTT: received (msg_id: 23), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 24) Debug: MQTT: received (msg_id: 24), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 25) Debug: MQTT: received (msg_id: 25), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 26) Debug: MQTT: received (msg_id: 26), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 27) Debug: MQTT: received (msg_id: 27), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 28) Debug: MQTT: received (msg_id: 28), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 29) Debug: MQTT: received (msg_id: 29), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 30) Debug: MQTT: received (msg_id: 30), looks like my own message, ignoring Debug: Message publishing acknowledged (msg_id: 31) Debug: MQTT: received (msg_id: 31), looks like my own message, ignoring Debug: action_web_request / type=homebridge Debug: Request type homebridge Debug: MQTT: topic sprinklerd/zone1/set 1 Debug: MQTT: pt2 zone1/set1P/1.1 host: 10.0.1.107:105 accept: application/json Connection: close

rd/statusOFFsOFFleallzones0@ Debug: Request to turn zone 1 on for 0 min requesttype 1 Info: Stopping! Debug: Turning off Zone 0. Setting pin 17 to state 1 Debug: Turning off Zone 1. Setting pin 18 to state 1 Debug: Turning off Zone 2. Setting pin 27 to state 1 Debug: Turning off Zone 3. Setting pin 22 to state 1 Debug: Turning off Zone 4. Setting pin 23 to state 1 Debug: Turning off Zone 5. Setting pin 24 to state 1 Debug: Turning off Zone 6. Setting pin 25 to state 1 Debug: Turning off Zone 7. Setting pin 5 to state 1 Debug: Turning off Zone 8. Setting pin 6 to state 1 Info: Wrote cache

toshibochan commented 5 years ago

In the web interface all work good.

What is working on homekit: Cycle all zone ON and OFF 24h Rain Delay ON and OFF Run on calendar schedule ON and OFF When switch ON cycle all zone the relay work okay

What not working on homekit: All other sprinkler button not working. Every time i try to switch ON sprinkler the sprinklerd crashes.

sfeakes commented 5 years ago

Thanks for this. There was a bug in the code. I've posted a fix, so if you update to the latest SprinklerD version it should be fixed. (No need to update homekit-sprinklerd).

toshibochan commented 5 years ago

Yay it works!!!!! Thank you! Thank you! Thank you! Just one request. On HomeKit now only can set time 5 min 10 min 15 min...... is possible to change the code for every 1 min?

sfeakes commented 5 years ago

Great, glad it's all working. I'll update the documentation to make the install & config easier, thanks for sticking with this to get it going.

The 5 min increment is specified Apple. That's couldn't be changed in the last version, I'm still looking to see if there is a way round it in the latest version. If you set the default runtime in the web UI, then HomeKit will give that as an option, but still no 1 min increments.

toshibochan commented 5 years ago

I see. Let me know if you find way to do every min. One more think I was looking for do schedule on HomeKit app but I wasn’t able to select any sprinkler.

sfeakes commented 5 years ago

I posted information in the other thread. It's a limitation of the apple HomeKit app.

https://github.com/sfeakes/SprinklerD/issues/1

sfeakes commented 5 years ago

Looks like scheduling on HomeKit app, is again limitation of HomeKit app.

toshibochan commented 5 years ago

Apple have to stop all this limitations! I test with eve app and work

sfeakes commented 5 years ago

I agree. Other apps have a lot more control over HomeKit accessories than the Apple app does. But the Apple app is still the most user friendly / easy to use.