Read sensor values from your Quatt Commander-in-Chief and act on changes. Note that nothing can be changed in the Quatt heatpump, as this is unsupported by Quatt.
Current features:
Fetch Quatt Commander-in-Chief data
Supported Languages:
English
Dutch
Contributions
If you appreciate this app, contribute to future development by making a paypal contribution
or buy me a coffee on Ko-Fi
Hi Trietsch in the Quatt app you can add your energy price and gas price, now I have dynamic pricing and not fixed. Would it be possible to change the price for gas and electricity by this homey app on a hourly base?
Hi, nope that’s not possible, as I’d have to reverse engineer the app API, whereas this Homey app focuses on the local data feed.
Also, I doubt that Quart actually supports dynamic prices, since this requires keeping prices at multiple points in time.
The Homey device stats showed numbers of three months ago, so wanted to repair / re-add the device, but now can not find it anymore. Did the Quatt local API possibly change?
Edit: retried just now, after having had a reboot because we’ve installed the latest Homey update (likely not related), and the Quatt device now correctly shows up again and properly shows the right numbers again. This probably was related to a changed IP address somewhere, but there is no warning shown related to this.
How I’ve configured the app, is that it assumes that the Quatt device is in the same subnet as the Homey. This is not always beneficial, but it works in most scenarios.
Were you potentially also able to adapt the polling frequency in the app? It’s currently at 30 sec, but I also use it for detecting the use of warm water, for which I would like 5 sec or lower polling frequency.
Was mentioned on the dutch version of the quatt discussion
@Patrick_Van_Deursen I have added the interval to the settings UI, since Quatt updates its values every second. Default polling was already at 5 seconds (at least in the code) but now you can set it between 1 and 60 seconds.
@trietsch I have created a pull request for this update
Hmmm, I don’t have this problem but I’m running my patched Quatt app which also has null/undefined checking for params (comes with the fix for the null value for the boiler)