Hello, this sounds like a fantastic project, thank you @David_Piper for your hard work! I have no coding skills to contribute, I’m afraid, but I’d love to join the testing group if possible, please. I have an Octopus Mini and I’m on the Agile Octopus tariff. Thanks!
Hey Kate
Thanks for getting in touch. An Agile user - not sure we have one of those so this should be an adventure! I will PM a link to the testing forum.
Great, thanks!
Beta Test Release
Morning all. I think most people in this thread are already in the Alpha-test thread too, so how much difference this is going to make I am uncertain. Thanks to everyone who has give their time, effort and feedback in the Alpha testing. It’s been a real struggle at times with the hard “distance programming” problems to crack. Special thanks to @Stu_F who has given time to video calls to help me work out what on earth is going on…
Release Use and Defects
| Version | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|
| 1.0.27 | 9 | 0 | 0 | No crashes so far  |
| 1.0.9 | 1 | 12238 | 6 | Early release with simplistic assumptions |
This table summarises where the alpha test has got to in terms of releases and defects. 1.0.27 has been available for a couple of days, with 9 users working with at least 5 different tariff types. Zero crashes so far and no feedback from the testers about strange looking data. As you can see, one tester has not upgraded for a while from a release that crashes very regularly.
Installation Link
You can download the app from the Homey App Store using the following link:
The app is still in test mode in the App Store, one consequence of this is that your installation will NOT upgrade automatically as new releases are made. When a new release is published, I will continue to publish first in the Alpha channel and only when a stable new release is available will I give the link here. This approach will protect you from my most stupid mistakes 
.
Looking forward to your feedback.
1 Like
Beta Test Release 1.0.28
I shall try not to make too many announcements in this thread about new releases. 1.0.27 has started logging crash reports quite regularly - always the same defect. The reports started at 08:00 this morning, 12th November. If you recognise that installation time please message me here so I can understand what is different in your Kraken data that has caused this defect to suddenly started being reported so frequently.
I have made a fix, but don’t yet fully understand the root cause. You can install the new version using the link below:
Hi David,
Thanks for the work on the app, that might have been me.
I’m in the UK on an Octopus Intelligent Go tariff.
Octopus app seems to have stopped reporting in my usage on 12 when I linked to the kraken app so looks like something may have gone wrong at a higher level.
Thanks
Tom
Thanks, @TomKat, for getting in touch. Have you upgraded to 1.0.28? That release applies a fix that enables the App to carry on working whilst I research a fuller solution. The link in this post will get that version. Let me know your experience.
The better news seems to be that 1.0.28 is not showing any crashes and the crashes on 1.0.27 stopped at about 19:20 yesterday, 12th November. Whether it was you or another user it looks like there has been an upgrade to 1.0.28.
Post V1.0.28 Usage Profile
| Version | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|
| 1.0.28 | 9 | 0 | 0 | So far, so good… |
| 1.0.27 | 2 | 716 | 1 | Intermittent crash gone rogue |
| 1.0.21 | 1 | 13 | 2 | Stupid typo I should have spotted (12/13) |
| 1.0.9 | 1 | 13925 | 6 | Early release with simplistic assumptions |
Updated 14-Nov-2025
Thanks David, apologies I think I may have found my issue.
I didn’t have an octopus home mini just standard smart meter readings. From this setup the billing date correctly populates but everything else was blank.
I have a unit on the way which may solve the problem.
I just installed 1.28 version, if it has caused any errors on your tracking I will uninstall l and wait for my OHM to arrive.
Thanks
Tom
1 Like
Yes you absolutely need an Octopus home mini (OHM). That’s the only way of getting timely data. Anything else is 36 or 48 hours out of date which is no use to man nor beast nor Homey.
There are no errors reported on V1.0.28 so it’s not causing any problems - in fact you helped because the errors made me fix a problem I had been procrastinating over. This information starts to make sense of the error.
Question to help me diagnose further - did the App allow you to pair some Homey Devices? If so then the OHM is already registered on your account (it should arrive pretty quickly after that). If you have succeeded in getting the Homey Devices added, then when you plug in the OHM those Devices should just start picking up the data. I believe that, because I was getting the error, you have actually succeeded in creating the Homey Devices…
If you haven’t been able to create the Homey Devices, then just use Add Devices once the OHM has arrived and you have plugged it in. Everything should pick up from there.
If it doesn’t work as positively as I have described, then just uninstall and reinstall the App once your OHM is pinging data through to the Octopus App or Webapp.
Either way can you let me know your experience - it may enable to me to improve the app further.
Thanks for your enthusiasm…
Hi David,
I was able to ‘add’ the homey virtual devices based on my API key and account number. The billing period does correctly pull through so the linking is correct.
Thanks for the update I will eagerly await my OHM and will give an update on how the install process goes 
Many thanks for the dev work I’m excited to get using it.
Progress Update
V1.0.28 Seems to be very stable. There are 11 installs, most of which have been around for 2 or more days. Conservatively that’s over 20,000 executions of the timing loop. Most of the code in there is very linear, so it’s mostly being executed every loop. Only one crash so far - that appears to be a malformed response from Kraken again. The code there has been made more robust ready for the next release.
Release Usage
| Version | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|
| 1.0.28 | 11 | 1 | 1 | Query returning malformed response |
| 1.0.21 | 1 | 13 | 2 | Stupid typo I should have spotted (12/13) |
| 1.0.9 | 1 | 14925 | 6 | Early release with simplistic assumptions |
Next Steps
Pretty much as before. I am still working on improving the flexibility of how the app manages the capabilities on the different devices - research is finished and it’s just a case of implementing the improvements that have been successful. This and a few other minor changes, including the removal of pre-tax prices and the addition of a Tax Rate capability on the tariff devices, will be released in V1.0.29.
Immediately following that I shall start implementing the Intelligent Dispatches. First there will be a release adding an Intelligent Device (Homey) device [that’s such clunky language, sorry]. Then (at last!) a release that integrates the Intelligent Dispatch Pricing into the calculations of cost on Intelligent Tariffs. Followed, no doubt, by a whole bunch of bug-fix releases. 
.
Then submission to Athom…
V1.0.29
With the relative success of V1.0.28, I have taken the opportunity to make some long-standing changes before I get entangled fully in the implementation of Intelligent Dispatches:
- Untaxed price capabilities removed;
- Tax Rate capability added to Product Tariff devices;
- Date and time formatting improved in Product Tariff and Energy Account devices
In addition to these visible changes, I have refactored “business” logic so that the device classes just focus on UI stuff. The code has been tidied and redundant code removed.
A stub of the new Smart Energy Device class has been created, but not yet hooked into the main App code.
1 Like
V1.0.29 Usage Summary
| Version | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|
| 1.0.29 | 12 | 0 | 0 | OK so far… |
| 1.0.28 | 2 | 1 | 1 | Query returning malformed response |
| 1.0.21 | 1 | 13 | 2 | Stupid typo I should have spotted (12/13) |
| 1.0.9 | 1 | 18924 | 6 | Early release with simplistic assumptions |
Updated 2025-11-22 16:05
V1.0.29 Interesting “Feature”
The billing period on my account just rolled over. For one minute at midnight, the projected bill was over £100,000. Whoops. A bit of smoothing is required at the beginning of the period… Here’s the “interesting” insight…
Documented as bug #9. The correction will be to avoid calculating the estimated bill during the first day of the billing period. Null will be assigned to the capability when the value is not be calculated - displays as “-” in the Homey UI.
1 Like
V1.0.30 Smart Energy Devices
This release is the first release to test Smart Energy Devices for Intelligent Tariffs. I have good reason to believe that these will have NO impact on users consuming other tariffs. I am hopeful that the new devices will be resilient in this first release for those customers using an Intelligent Tariff.
In addition, in this new release there are enhancements to the smart management of Capabilities on Devices. Bug fixes have been applied, including the improvement of the Project Bill capability on the Octopus Account device.
I have started to write a Git Wiki on the Octopus App and how it is used. This can be accessed using the Developer Website link on the App Page in the Homey App Store. Have a read and let me have your comments…
1 Like
V1.0.32 Bug #10 Fix
The initial Smart Energy Devices release erroneously excluded devices that were unplugged at the time of using the App. This version has added a status code to the filter list so that these devices are correctly included in the App.
Zero crashes reported so far.
V1.0.32 Usage Analysis
| Version | Installs | Crashes | Crash Types | Comment |
|---|---|---|---|---|
| 1.0.32 | 7 | 0 | 0 | OK so far |
| 1.0.30 | 2 | 0 | 0 | Robust for non-intelligent tariff customers |
| 1.0.29 | 3 | 0 | 0 | OK so far… |
| 1.0.28 | 2 | 1 | 1 | Query returning malformed response |
| 1.0.21 | 1 | 13 | 2 | Stupid typo I should have spotted (12/13) |
| 1.0.9 | 1 | 19924 | 6 | Early release with simplistic assumptions |
Updated 2025-11-24 21:00
The current code base is behaving very consistently and robustly across the various tariffs in the beta test group. Thanks for everybody’s patience in getting this far!
Next steps:
- Add flow cards for Smart Energy Device - When Dispatch Starts and When Dispatch Ends to give some minimal automation capability (a couple of other minor enhancements for SED will be released alongside).
- Integrate Dispatch slot price changes into the Tariff device (without adding bugs for non-intelligent tariff users).
- Submit to Athom for approval as a Community App.
- Integrate Energy Saving and Free Energy periods after approval
V1.0.33 Dispatch Flow Cards
Just published this version of the app that adds when flow cards for When… Dispatch Starts and When… Dispatch Ends.
Whilst I progress the Intelligent Tariff functionality, there is relatively little going on for the other tariffs. Nonetheless I encourage you all to upgrade because there are some bug fixes in there too.
Trello Board
It’s hard to break the work habits acquired over many years. Having built the Kraken Energy App relying on memory, sticking plaster and string, I am trying to bring a more familiar level of rigour and discipline to the work. I have created a Trello board where you can see what is currently in progress and what is coming next.
It would be great to get your suggestions for new and enhanced features too. The trello board is read only for public access, so please make your suggestions for new stuff here. Click the image to see the full Trello.
