Already turned on debug logging. All errors in the logs are above (unless there is another log I need to find).
Errors might have something to do with the tap being added previously to the first gateway maybe?
Apologies, i replied before i saw your post with the logs.
I know what the issue is :: the unique_id thats generated doesnt take the gateway into account.
So because you have moved it, its seeing the old one.
I thought deleting the integration and restarting would take care of that, but apparently not.
Ive just pushed a beta release of 0.1.5, which should fix the issue.
Apply it and restart.
Its entirely possible it will break everything horribly, and you will need to delete both integrations and re-add them, but that will get you out of trouble for right now.
Unfortunately my test HA instance doesnt currently have the integration configured, so I wasnt able to do a good real world test.
Thank you for such a quick update and fix. Iāll report back after I apply the update tomorrow.
Just tried the beta and same errors unfortunately.
Happy to try other fixes so let me know if there is anything I can do.
Hi all,
i am planning on getting a Linktap device. But in parallel I have a big zigbee network with 50 devices.
I read about interference with zigbee networks, causing them to crash as the G2S is in permanent Join Mode. Is this still the case and how did you work around that? Thanks for any hint!
I have a LinkTap setup with four outlets and about 10 Zigbee devices and havenāt noticed an issue. Maybe because I have a lower number of devices it might be different.
I am using Z2M and a Sonoff coordinator and have found that combination works for me.
1 Like
I have 50+ zigbee on z2m, devices and 4 linktap devices and havent noticed an issue.
2 Likes
Great thank you guys! Then I can have peace of mind!
Ok so now i got it working thanks to you guys! I use MQTT - someone else aswell? Does anyone use the water consumption in some energy dashboards? The HTTP API was sadly not enough for me, as for example I could only enter the duration in Minutesā¦ 
The API description describes that there is a second parameter for the seconds.
durationSec: Optional. Number type. The second portion of the watering duration (unit is second). It is used for the G1S and G2S models only. Its value is between 0 and 59. An example: if you want to water for 10 minutes 30 seconds, then the duration field will be 10, and the durationSec field will be 30.
I think by now MQTT, http and the integration from sh00t2kill all work very well. The integration is probably the easiest to get started.