Regarding the approval option not showing up for you in the dashboard, do you see the chore changing status from pending to claimed? Keep in mind that single approval chores can only be claimed once per day, although I don’t think that is the issue here.
The best way to troubleshoot is to take the dashboard out of the equation and just click the buttons for that chore from the developer tools. Sounds like you started to do that, but once click the claim button, check that the _chore_status sensor changes to claimed, as well as checking that the _global_chore_pending_approvals sensor is named as expected, and shows the claim was made. At that point, as long as the claim shows in that sensor, it should be showing on the dashboard unless somehow the dashboard name is still not matching with the name on your sensor.
If it’s still not working after checking these things, take a couple screenshot similar to the one below as you go through the process so I can see the entity values change and post them over in the github issues and I’ll help you troubleshoot further.
Firstly I wanted to say thanks very much for this dashboard, it’s a fantastic piece of work.
This might be an edge case but I’ve figured out why the Approve button wasn’t working for me, it looks like there might be a problem when there are brackets in the name - “Brush teeth (morning)” throws an error (‘dict’ object has no attribute ‘append’) but “Brush teeth in the morning” seems to work fine.
In the first post the link to the github page is an old commit of the README.md file from 5 days ago, you might want to link to the main page of the repository so people are always seeing the latest version.
This morning i reset all data ready to start using with kids and having same problem as others approvals dont show up
followed all comments and fixes but still cant get it to work.
I have just set up HA for this so my knowledge is basic
In my case i can see entity and press
Chore claimed changes to 1 but global pending remains zero
If i click from dashboard log shows claimed sometimes it will change to orange sometines its very slow to update no approval button shows.
At the point where im thinking to remove and start from scratch maybe i did something incorrectly
I have 3 kids 30 chores different dates times was a chore in itself imputting and changing names days dates times etc
I have tried deleting kids and parents and setting up again didnt do anything tried with 1 child to see if it would be easier to identify issue still not working
Thankyou - I think it is because ive never actually used them before - I was tapping it expecting it to bring up the option sbut was taking me into HA just anywhere - but a LONG PRESS was the answer - which is how it is supposed to and always has worked! Thanks for the reply @VaReTaS
I went back and started again from a backup and it is working better so Im not sure and cant replicate any more. Working well now althought the only thing now is the chore approval stays on the screen after approving (or denying) - is this supposed to happen?
i went and started over removed kidschores and started from scratch still chore is marked as claimed kc_global_chore_pending_approvals remains zero
not sure if it explains why but in logs it shows
This error originated from a custom integration.
Logger: custom_components.kidschores
Source: custom_components/kidschores/button.py:263
integration: KidsChores (documentation, issues)
First occurred: 12:56:03 (3 occurrences)
Last logged: 13:14:44
Failed to claim chore ‘Make Bed’ for kid ‘Jasmine’: ‘dict’ object has no attribute ‘append’
Failed to claim chore ‘Laundry’ for kid ‘Jasmine’: ‘dict’ object has no attribute ‘append’
Failed to claim chore ‘Tidy room’ for kid ‘Jasmine’: ‘dict’ object has no attribute ‘append’
@AJErazzor - Does the global_chore_pending_approvals sensor still show the claim listed after approval? If so, next step is probably to enable debug for the integration, click the approve again and then check the logs for errors.
And share there the contents of the file requested?
I will get back on this and check what might be the root cause for the error. This is working fine for me, even on a new installation, so I need to figure out what the issue might be.
Unsure if this fixes all reported `str errors, but having a challenge setup that is missing start and end dates set will definitely cause issues. Currently, the integration does not require challenge dates, but it expects them to be present—which can lead to system-wide issues. (This will likely change in the next release.)
If even one challenge is missing dates, it can cause major problems across the system. I highly recommend checking all your challenges right away to ensure they have both a start and end date specified.
If this fixes the issue for you, please reply to confirm or like someone else’s post who said it worked for them. Thanks!
Dashboard Update – Improved Special Character & Accent Handling!
An update to the KidsChores Dashboard has been released, bringing better support for accented letters and special characters across all areas, including chores, rewards, penalties, achievements, and more.
What’s New?
Chores can now have names like:"Brush Teeth (Morning)" without issues. Thanks to @archer1 for highlighting Expanded support for accented characters & symbols across the system. Fixes for sensor attribute lookups that previously failed on special characters. Various formatting improvements for a cleaner, more consistent display. Simplified setup! The dashboard now only requires one replacement of "Kidname", making installation easier than ever.
Some example special characters successfully tested tested:
I don’t expect any of you to have names this complicated in your setups, but I wanted to make sure that bases were well covered.
**This update is not urgent, but if you are having any issues, or have some accent characters in your configuration, I would recommend it.
Lastly, be sure to check the post above this one if you are having any issues. There is a known issue when challenges do not have start and end date is specified. We know this has quickly resolved a number of open issues and strange behaviour.
so far the fixes made have all worked but i have run into another issue which im hoping you can help me with. i have deleted some chores that were waiting to be approved and they are now stuck in my sensor.kc_global_chore_pending_approvals but they show up as none. i cant find a way to remove them because they are causing the approve buttons to show but theres no action to remove them
That’s a nice catch. I did not think of that that these should vê cleared from claims or approvals. I will add this to the next version, for sure.
If you want, in the meanwhile, you can edit /config/.storage/kidschores_data and remove the chores_ids that you removed from the file. I know it’s and hassle, but I don’t have a way right now to automate that, sorry.
I believe the other thing you could do is recreate those chores showing in the pending sensor with exactly the same name and assign to the same kid. Go ahead and disapprove each claim in question, then delete the chores again. Obviously @VaReTaS approach works well too if you’re comfortable making changes to that file, but thought I’d provide an alternative.
If you do modify the file directly, I think you may need to reload the integration afterword to ensure it picks up all the changes.
Unless he places the same chore_id, this will not work, as all those are referenced by id, not name.
Even though, I believe I found a way to get this sorted and get those removed if the chore_ids do not exist anymore. This is already implemented for the next release.
We’ve added new logic to the dashboard that automatically detects the correct chore pending approval and reward pending approval sensor names. This means you no longer need to manually update sensor names in the dashboard—just grab the latest version, and it will handle it for you!
What’s Next?
At a later point, we may recommend a few minor entity name adjustments to align with the latest standards, but the priority now is ensuring everything is working smoothly for everyone.
Big Thanks to the Community!
We appreciate your patience and feedback as we continue improving the system as quickly as possible. Also, if you haven’t seen it yet, @VaReTaS released a new KidsChores update this morning—lots of great progress and fixes happening fast!
Troubleshooting Guide Now Available!
We’ve also put together a detailed troubleshooting guide to help you diagnose issues independently and provide useful details to those providing support if you need help.
The dashboard update is not required at this time, but if you’re having any issues, please be sure to update to the newest Kidschores Integration 0.2.2 as well as updating to the latest version of the dashboard out on Github- ccpk1/kidschores-ha-dashboard