So, it looks like there were two separate issues. The API has two methods to get the status. One returns the alarms, active mode and last water flow rate but can only be called every 5 minutes. The other only contains data while the water is flowing but can be called every 30 seconds. This has the time remaining, flow rate, etc. It also has a parameter that I thought was volume, but it’s not documented and seems to always return 0. So that was one problem. The other was me setting the wrong capability in the 5 minute data and updating the volume instead of the flow rate.
So I fixed the issue with the wrong capability and I now attempt to calculate the volume. Unfortunately, 30 seconds is a bit course so the volume calculation is very much an approximation.
I have asked LinkTap if they can add that into the next update so we shall see if that appears.
I woke up this morning and the first thought that came into my head was “m³ is not L”
The water_meter capability is a standard Homey option with units of m³ but the value I calculate is based on the flow rate in L/min, so the number is actually in L.
As m³ would be a very small number for the LinkTap, I have changed the units text in v0.0.7 to L to match the number.
Hi Adrian,
thanks for this fix. The tag values are corresponding with the device capability now.
The amount of water ist the amount while the last timeslize of 30 sec? The overall amount of last watering would be better. But you can only provide the API data…
Perhaps this will be possible with local API - perhaps with callback at end of watering. So I will wait for coming updates from Linktap.
Bye
Ronny
The amount of water should be the total for each session, but something is not working properly.
In theory I sum half the flow rate every 30 seconds. It was working but not now, so it seems I fixed it and then broke it again.
I also found a bug in the new LinkTap firmware while testing it and reported that at the same time that I asked if the volume used could be reported. They replied this morning to say its fixed and it is so great support from them.
I have been investigating a bit more and found that the vol parameter is documented, so I wasn’t going completely mad before. The only problem is it is just accumulated over the on time and is only updated once per minute. So if the on cycle is only 1 minute long then it will likely never get updated due to the 30 seconds polling interval. When I was testing the other day I was using eco mode with 1 minute on and 2 minutes off, hence not seeing a value and thinking it was not working.
Today I set it going for 4 minutes without eco enabled and it was updating.
There is another API call to get the watering history over the last 30 days, so maybe I will look into using that to show the volume used over the last 24 hours.
I have also emailed my observation to LinkTap to see if there is anything the can do in the short term.
That’s interesting as it sounded like it would be in the EU before the UK.
I have had a reply to my observations / wish list for the API. They said they are starting to work on the local API so won’t be changing the server API for now. But if the local API doesn’t work out then they will take the wishes into account. No timescale was given as you would expect so we will have to be patient but I’m sure it will be worth the wait.
I have published a new test version 0.0.8. I have added the On / Off capability so the valve can be switched on and off in instant mode more easily. The Advanced Setting are still used to determine the watering period, etc.
The On / Off state is also altered when the valve state changes via the app ot when the on-time ends.
I haven’t seen that one before.
Which version are you trying to install (normal or test)?
You will probably have to contact Athom support and send them a Diagnostics report from your Homey.
I will ask around to see if anyone else has any suggestions.
That’s normal for installing from the app store. It means “will be installed soon”. The german translation ist no so exact
The installation starts in background and a refresh of the app screen should show the app.
If the version is not compatible, another message would appear in the app store.