Someone has gone forward with the HTTP rest api? i’m trying to perform the equivalent of activateInstantMode with a chosen duration (just to prevent the eventual case HA dies during the irrigation and water keeps going indefinitely), locally.
I often find some refers to a “LinkTap Gateway MQTT Client Interaction Messages_x.x.pdf” in the MQTT document, but I’m unable to find it online.
You have to create under helpers two numbers namely input_number.backyard_linktap_duration & input_number.frontyard_linktap_duration.
Then use the following subtituting the “x” with your information
rest_command:
backyard_linktap_manual_override:
verify_ssl: true
timeout: 10
url: https://www.link-tap.com/api/activateInstantMode
method: POST
payload: '{"username": "x", "apiKey": "x", "gatewayId": "x", "taplinkerId": "x", "action": "true", "duration": {{ states("input_number.backyard_linktap_duration")}}, "autoBack": "true"}'
content_type: 'application/json; charset=utf-8'
headers:
User-Agent: Home Assistant
Content-Type: application/json
frontyard_linktap_manual_override:
verify_ssl: true
timeout: 10
url: https://www.link-tap.com/api/activateInstantMode
method: POST
payload: '{"username": "x", "apiKey": "x", "gatewayId": "x", "taplinkerId": "x", "action": "true", "duration": {{ states("input_number.frontyard_linktap_duration")}}, "autoBack": "true"}'
content_type: 'application/json; charset=utf-8'
headers:
User-Agent: Home Assistant
Content-Type: application/json
Anyone having issues with LinkTap entities becoming unavailable in MQTT after a HA restart? Only way I have of getting them back is to restart Mosquitto broker, and then they are accessible with no issues
Nevermind…just read all the doc. and included the uplink/ downlink cmds - all working directly after a reboot 
Actually it’s still requiring a manual restart after rebooting HA - any and all suggestions appreciated!
Hey, someone posted a solution to this somewhere here, but I will try to summarize it:
You need this rest command with the linktap hub IP:
rest_command:
reboot_linktap:
url: 'http://192.168.1.209/index.shtml?flag=0'
method: GET
and an automation:
alias: HA Startup
description: Reset LinkTap server on startup.
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: rest_command.reboot_linktap
data: {}
mode: single
I think the linkTap people said they would fix it, but it seems they didn’t do it yet.
I think MQTT + HTTP rest api works great. I think a integration would make it easier to setup. Would love to see how it’s done.
Just MQTT got a bit complicated for me. Overall you can do everything with MQTT except setting a irrigation duration. Instead you would use the link-tap as a normal valve with a start / stop signal.
Edit: It is now possible to set a watering duration, watering volume and fail save watering duration through MQTT.
Thanks for the response - all working now!!
In case its useful for someone, i originally wrote this before i started on my HA journey, and still use this to implement linktap in HA (via rest calls to a local web server hosting the php app)
Could be a really good starting point if someone wanted to write their own custom component. I was always planning on doing it as a learning exercise but never made it that far!
1 Like
I DO use MQTT, but i dont use MQTT discovery (long story), but i did manage to get a simple MQTT switch up and running.
The good new is, if the tap is enabled via the cloud API, the local MQTT switch replicates the local state.
If anyone wants the manual MQTT config, hit me up.
I am currently using the cloud API to control the tap, but using MQTT for status of the tap (via 2 different switches)
@cecche The “LinkTap Gateway MQTT Client Interaction Messages_x.x.pdf” document you refer to is available from their support team, although its VERY complicated.
With spring watering season upon me, turned the Linktap gateway back on.
According to Linktap the MQTT capability is in the current released firmware, hence you do not need to contact them to enable.
Am i reading correct that he Linktap G2S will hook up nicely with HomeAssistant?
If yes then its exactly what i need
This thread is a little long and sprawling so thought best to ask
I have both the G2S and G1S running through HA. This is a screenshot of the G2S. The signal is probably at the very limit, but it still works.
The G1S doesn’t have the volume data.
1 Like
Excellent, is it a native integration or do i need coding? I use zigbee/mqtt and zigbee ha plus node red
I have other zigbee in the garden so range should be ok
Uses MQTT and can work with the built in Ha add-on
1 Like
I just noticed there is a gateway as well - do i need the G2S or the G2S with gateway?
You need the gateway and valve. They gateway can support more than one valve
Ok, thanks
And - When I bought the Gateway, I specified HA and Jack loaded the firmware.
This means that once I connected the valves to the gateway, they just appeared in my Mosquito broker. I use Zigbee2MQTT and it was a breeze. Even changing the name of each tap allowed me to automatically change the name of each entity so they have friendly names instead of the serial number.
1 Like
Have ordered a valve