All being well with the storm of recent changes, Gas tariff work should start soon. Fingers (and most other things) crossed.
Progress Update
It finally feels like the mass of changes introduced by the architectural refactoring is settling down - at last.
On the credit sideā¦ The caching of the big event data to feed the small events is working well. The timezone problems exposed by the change to DST have been resolved. Pretty extensive testing of the complexities around Intelligent Octopus Go dispatches shows these are working very well too. A bug related to having only an import tariff and no export tariff has also been exposed and squashed (thanks @Carl).
On the debit sideā¦ There remains a small āaccountingā problem around the calculation of time spent in dispatch (so that the App can report against the daily limit). It sometimes comes up a minute short at the end of a dispatch. There is a fix in place, but testing takes a whole day. 
On the āthings are getting betterā frontā¦ I finally bit the bullet and paid the lifetime license on Homey SHS. My server is now up and running and it is making things so much easier for development and testing. Testing is a little slower because the App runs with a heartbeat of 2 minutes instead of 1 (so I can run two installations). Once I get a feature to the point where I think it is stable I will continue the practice of installing on my Pro for extended soak testing purposes. But I will never let test data lose on my Pro again - the data is becoming too important for that.
Next Steps
I feel dubious about mentioning any, given the delays around the deep changes that have been made. But what the hell. IF tomorrowās testing goes well THEN I expect to publish a new test version on Thursday evening.
Nice Feature
Lookā¦ I set the Homey webapp up as a Progressive Web App. On a Chromebook you set these up as tabbedā¦ Here I have my Homey Pro and my Homey SHS side by side into two tabs. Nice! All that and multiple tabs for my Homey Pro - different insight charts, or flows or the favourites tab all tab-by-tabā¦
The image is pretty rubbish. Sorry.
)
Version 1.2.7 Published
Morning all. Version 1.2.7 has been published as a test release. I have all my fingers and most other parts of my body crossed 
. More seriously I am quite hopeful that this release represents a return to the quality of earlier releases around 1.2.2 and 1.2.4. It has been performing very well on both my real and test data.
As a small ārewardā to the IOG users who have been so helpful in defragging the mess that was 1.2.6, I have bundled a couple of small (and very simple) changes into the Smart Energy Device. If you delete and re-create your Smart Energy Devices (at a convenient time), you will see new capabilities:
- Total Energy - the total energy currently planned for dispatch
- Plan End Time - when the last dispatch in the current plan will end
I have a question that I hope the IOG community will respond to. I am unsure of how these capabilities will behave because it depends on what Kraken does with the list of dispatches. I can see two scenarios:
- The list is kept fully populated until the plan is complete - these capabilities will NOT change value during the plan delivery
- The list is truncated each time a dispatch completes - these capabilities will change value each time a dispatch is completed
Either way the capabilities are working, but the title of the first can be changed to āTotal Energy Remainingā. Also Energy is given as a negative value by Kraken - so thatās shown on the UI. I am happy to change the sign - let me know.
Next Steps
- Monitoring 1.2.7 - obviously - please let me know how you get on.
- Gas tariffs.
Thanks as always David. This app is a game changer for me.
One User Canāt Upgrade
Evening. Since 1.2.7 was released, I have one user who is unable to upgrade. The App V1.2.7 installs, but doesnāt seem to run correctly. I am unable to reproduce anything like this result on my test rig.
Anyone else out there experience ānothing happening after upgradeā?
Installed and working here. Also recreated devices so monitoring.
OK. Did a bunch of install/uninstall/stop/start/restart whatever. Things seem to be normal again now. End of sweatā¦
Version 1.2.7 Usage Analysis
Been a while since I published one of these - been down in the weeds trying to get things working smoothly again. Feels like āhead above waterā again now. So here goesā¦
| Version | Status | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|---|
| 1.2.7 | Test | 26 | 0 | 0 | Published test 2026-04-10 07:00 |
| 1.2.5 | Superseded | 1 | 0 | 0 | |
| 1.2.4 | Live | 49 | 0 | 0 | Published 2026-03-31 16:30 |
| 1.2.3 | Superseded | 5 | 0 | 0 | Published live 2026-03-16 08:30 |
| 1.2.0 | Superseded | 2 | 0 | 0 | Published 2026-03-04 11:00 |
| 1.1.0 | Superseded | 6 | 999 | 1 | Defect upgrading from prior releases, resolved by deleting and re-adding any device |
| 1.0.39 | Superseded | 3 | 0 | 0 | Published 2026-01-11 17:25 |
| 1.0.38 | Superseded | 3 | 246 | 1 | Affected user upgraded |
| Totals | 95 | 1245 | 2 | Older versions all retired with 0 users |
181 Kraken Devices
I have just updated to 1.2.7 and recreated my devices. Some repair work was required to the flows so be careful if you do this.
I have an unrelated issue that I cannot update from iOS anymore. It worked in the past but lately when I click the link it goes to a webpage for Homey. Not linked directly to this release.
Version 1.2.8 Published To Test
Version 1.2.7 caused problems for some users upgrading from 1.2.4 - a reminder that I need to test the upgrade path before publishing. With a SHS as a test environment I now have somewhere to do that - so no more excuses.
An unfortunate ālast mileā problem in what I think will become a good outcome for all the architectural changes that have been made. I encourage all users to take the jump and move to the new version.
Other Tweaks
For IOG users I took the opportunity to tweak a couple of capabilities on the Smart Energy Device Homey Device. Energy planned for dispatch is now shown as positive values and the āPlan Energyā capability is now titled āRemaining Energyā because it sums the energy to be dispatched across the remaining dispatches currently planned.
Any Problems
Please do let me know - I really want to make the Kraken App the best it can be.
Version 1.2.8 Usage Analysis
| Version | Status | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|---|
| 1.2.8 | Test | 25 | 0 | 0 | Published test 2026-04-11 18:55 |
| 1.2.7 | Superseded | 0 | 0 | 0 | Upgrade problems from 1.2.4 |
| 1.2.5 | Superseded | 1 | 0 | 0 | |
| 1.2.4 | Live | 55 | 0 | 0 | Published 2026-03-31 16:30 |
| 1.2.3 | Superseded | 5 | 0 | 0 | Published live 2026-03-16 08:30 |
| 1.2.0 | Superseded | 2 | 0 | 0 | Published 2026-03-04 11:00 |
| 1.1.0 | Superseded | 5 | 999 | 1 | Defect upgrading from prior releases, resolved by deleting and re-adding any device |
| 1.0.39 | Superseded | 3 | 0 | 0 | Published 2026-01-11 17:25 |
| 1.0.38 | Superseded | 3 | 246 | 1 | Affected user upgraded |
| Totals | 99 | 1245 | 2 | Older versions all retired with 0 users |
185 Kraken Devices
Updated 2026-04-14 12:00
Gas Tariffs
Starting to investigate Gas Tariffs. It seems that the meter read is pretty reliably on a 30 minute heartbeat (but not on the half-hour). As a result, it feels natural to integrate the Gas Live Meter read with the LARGE transaction.
The LARGE transaction occurs on the hour/half-hour - so that could mean a delay between the reading being published and the data being absorbed by the app. To avoid this, I think it best that the timing of the LARGE transaction be adjusted IF there is a gas tariff present to minimise the time between publication of readings and the large transaction.
Algorithm: When a Gas Tariff device is added, read the most recently published live Gas data and its publication timestamp. Reset the timing of the LARGE transaction to the next SMALL transaction time after the (publication timestamp found previously + 30 minutes).
If the smart read fails, it isnāt going to affect the overall integrity of the Gas data very much. The app relies only on the Meter Reading value - on the next successful read that will just jump by a bigger increment than it would have otherwise. There might be some impact on end of day readings - but thereās not a thing that can be done - if the data isnāt available itās not availableā¦
Looking at prices, it seems that there is a single price per day - even on Agile the price only changes at midnight.
Conclusion - Gas Tariff seems to be much more about gathering, refining and analysing data than it is about smart control of devices. Price is fixed during the day, so thereās not a lot of point varying the timing of things based on price.
These are the capabilities of a non-varying price electricity tariff - I think the capabilities of a gas tariff will look very much the same:
Agile Gas might add a āTomorrowās Price Presentā indicator - there might even a flow trigger for that capabilityā¦
Tentative Conclusion
On this basis a Gas Tariff device looks doable and reasonable.
Feedback Please
Very tentative conclusions for now. If there is anything that any Gas user disagrees with, based on their experience, please shout out!
As I read down through your message you covered all the points I had in mind.
For most, if not all, the only change in price is daily.
The only use case I could imagine would be to use the next day price do decide if you want to heat water with gas or electricity.
Appreciate the contribution, thanks @Stu_F
Version 1.2.8 Usage Analysis - 100 Installs 
| Version | Status | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|---|
| 1.2.8 | Live | 73 | 0 | 0 | Published live 2026-04-15 19:45 |
| 1.2.7 | Superseded | 0 | 0 | 0 | Upgrade problems from 1.2.4 |
| 1.2.5 | Superseded | 1 | 0 | 0 | |
| 1.2.4 | Superseded | 8 | 0 | 0 | Published 2026-03-31 16:30 |
| 1.2.3 | Superseded | 5 | 0 | 0 | Published live 2026-03-16 08:30 |
| 1.2.0 | Superseded | 2 | 0 | 0 | Published 2026-03-04 11:00 |
| 1.1.0 | Superseded | 5 | 999 | 1 | Defect upgrading from prior releases, resolved by deleting and re-adding any device |
| 1.0.39 | Superseded | 3 | 0 | 0 | Published 2026-01-11 17:25 |
| 1.0.38 | Superseded | 3 | 246 | 1 | Affected user upgraded |
| Totals | 100 | 1245 | 2 | Older versions all retired with 0 users |
199 Kraken Devices
Updated 2026-04-15 09:50
Iām wondering if thereās a bug in the Import Tariff @David_Piper.
When Octopus decides to play silly buggers with the slots, it seems that tonight the Kraken apl missed a change to PQ 0. It went PQ 0 at 22.05 until 22.30, at 22.30 Octopus looks to have pushed a PQ 3 followed by a PQ 0 immediately after. I can see that I should be in dispatch in my Octopus App, my Hypervolt App, and my Octo Aid App. Kraken Device (Hypervolt) shows in dispatch however Kraken Import Tariff is showing PQ 3
