[ISSUE] custom_interval_invalid on 1.0.6

[shtrom]

Home Assistant version

2026.4.1

ChoreOps integration version

1.0.6

Installation method

HACS

Prerequisites

• I checked for existing open and closed issues
• I updated ChoreOps (or confirmed the issue still occurs on the latest version)
• If this is a dashboard issue, I updated dashboard dependencies such as button-card and confirmed the issue still occurs
• I enabled debug logging and can share logs

Issue scope

Not sure

Steps to reproduce

1. Create a new chore
2. Set its schedule to Custom (Reschedule ...
3. Set Custom interval to, say, 4
4. Set Custom interval unit to, say, Months
5. Submit

Issue description

Following #100, I upgraded to 1.0.6.

When setting a custom interval, I now get a custom_interval_invalid error.

Relevant entity IDs (optional)

No response

Logs

Additional context

[ccpk1]

When I released 1.0.6, I realized that there were a few of my changes that didn't get properly pulled in, so 1.0.7 was released a couple hours later. This should be fixed in there.

[Neflhiem]

ok so is this option just gone? im setting up a new chore and i can set the time unit (months) but not how many i need after completion (24).. i know ive done it on my others but that block is gone

[ccpk1]

There was an issue with version 1.0.6. Go to HACS and download 1.0.7 and it should work properly. You might have to update information on the HACS page and refresh the browser for 1.0.7 to show up if it's cached.

[Neflhiem]

Thanks, that did it!

[shtrom]

On 12 April 2026 1:55:35 am AEST, ccpk1 ***@***.***> wrote: ccpk1 left a comment (ccpk1/ChoreOps#105) There was an issue with version 1.0.6. Go to HACS and download 1.0.7 and it should work properly. You might have to update information on the HACS page and refresh the browser for 1.0.7 to show up if it's cached.

Ah, I didn't see 1.0.7. Yep, that fixed it. Thanks! -- Olivier Mehani ***@***.***> Sent from my mobile, please excuse my brevity. Please consider the environment before using AI on this email.

[ccpk1]

Looks like 1.0.7 is working as expected, so I will close this.