Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dispatching ending before 30min timeslot #793

Closed
2 tasks done
Reddax opened this issue Mar 11, 2024 · 3 comments
Closed
2 tasks done

Dispatching ending before 30min timeslot #793

Reddax opened this issue Mar 11, 2024 · 3 comments
Assignees
Labels
bug Something isn't working stale The issue has not had any activity for a while

Comments

@Reddax
Copy link

Reddax commented Mar 11, 2024

Describe the bug

With the 'Octopus Energy Intelligent Dispatching' sensor, when I unplug my car, i'd expect the dispatching to end at the end of the 30 minute block, but instead, it ends immediately. I believe this should have been fixed in the current version 10.1.4 as in the release notes there's 'Fixed issue when dispatching sensor would not stay on during full half hour when planned dispatch is active'

image

Reproduction steps

  1. Plug car in to get it charging, Dispatching turns on.
  2. Unplug car, dispatching ends within the next 5mins, rather than end of the 30min block.

Expected behaviour

I'd expect dispatching to run until the end of the 30min block, 00 or 30 min past the hour.

Tariff Code

E-1R-INTELLI-VAR-22-10-14-M

Integration Version

10.1.4

Home Assistant Version

2024.1.6

Fresh Install?

Not specified

Home Assistant Logs

Don't think is required, but can do if needed.

Confirmation

  • I confirm that I cannot find my solution within the documentation
  • I confirm that I cannot find my solution within the FAQ
@Reddax Reddax added the bug Something isn't working label Mar 11, 2024
@BottlecapDave
Copy link
Owner

Hello and sorry for the late response.

The dispatching sensor turns off when there isn't a pending or completed dispatch for the 30 minute period and matches the rate information that is available. It could have been that upon the update of dispatching data, OE removed the pending dispatch but didn't add a completed record (I've had reports of this happening from time to time). The next time this happens, could you please review your rate information and see if the block is reverted back to a peak rate?

Copy link
Contributor

github-actions bot commented May 7, 2024

This issue has become stale because it has been open for 30 days with no activity. If you still think it's an issue, please respond soon.

@github-actions github-actions bot added the stale The issue has not had any activity for a while label May 7, 2024
Copy link
Contributor

This issue has been closed because it has been inactive for 14 days since being marked as stale. This is done to help keep on top of active issues. If you still think it's an issue, please respond to this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale The issue has not had any activity for a while
Projects
Development

No branches or pull requests

2 participants