-
Notifications
You must be signed in to change notification settings - Fork 22
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
State is not on when event is active #84
Comments
Hi @albinmedoc! Looks like the event is on until the calendar updates from the internet? |
@albinmedoc I haven't seen this before. Can you share a sample ICS file (it's OK if the dates/times are in the past)? Just please remove any sensitive information from the file before sharing it. If you don't want to post it to GItHub, you can also send it to me in a private message to franc6 on https://community.home-assistant.io/ |
Down is a small sample ICS file. (I have shortened it and removed sensitive information)
|
This is how i add the calendar in configuration.yaml
|
Thanks for the info. I hope to be able to look into this next month. I'm sorry for the delay. |
I'm having this issue as well. The calendar is not 'on' even if have some events. |
Same issue her. I'm using the Holiday Calendar for Germany from Apple iCloud. It's located here: https://p05-calendars.icloud.com/holiday/DE_de.ics This is how I integrated it:
There are only all-day events in this calendar. State for Christmas Eve switched to on at 00:00 a.m. and swichted back to off 15 minutes later. |
any plan to fix this problem soon? basically this integration is useless unless you create additional sensors to overcome this bug... |
@albinmedoc The sample file doesn't cover the time in your initial report. |
@albinmedoc @LPirro @bearpawmaxim @papperone Please also enable debug logs. To do this, you'll need to edit your configuration.yaml. Look for a section named "logger". If you don't have such a section, add it to the bottom of the file, along with a subsection named "logs". Under that subsection, add: custom_components.ics_calendar: debug So, your yaml should look something like this: logger:
logs:
custom_components.ics_calendar: debug Then, next time you notice it, download your home assistant core log file (or go for it directly, if you can), remove all lines that don't contain: "[custom_components.ics_calendar]", and post it here. If you see something that should be kept private, please redact that only by changing the private data with a single letter 'X'. If you remove any lines from the log output, it won't be very useful. I might need to add some more debug logging if that doesn't help track down the problem. Thanks! |
here's my config:
today (and probably tomorrow) I had the issue, despite the entry in the calendar is "all day" the event stay ON only a bit more than 1h (see below) event for tomorrow seems again correct in the calendar but the behaviour is that the calendar stays on 1h or more and then turn off; I'm expecting to stay ON whole day accordingly to caledar event start/end time: |
Thanks, @papperone! Every data point might be helpful. I did eventually see this once with my own calendar, but only once so far. It’s frustrating since I haven’t been able to reproduce it reliably, or at all under test conditions (unless I’ve got something backwards in the tests). When I get some more time again, I’ll be looking into it more. That will likely be a while. I didn’t even get back to this last month, and the next few don’t look much better for my time. Thanks for your patience. |
thanks for your work, at the moment I've put a workaround to read the state of the calendar every day at 00:15 and copy it on a boolean that than I use in my automation, but unfortunately if my HA reboots on a Bank Holiday (this is why I use this addon) the boolean is of course restored to "false" and I loos all my automation that are based on the fact that day is/isn't a public holiday :( |
any chance to have this fixed? sorry to say but with this bug ongoing since literally months I will probably drop this integration to move to something different (manually done probably) that al least can work properly... still available to run test but if you import the calendar I'm using just for test I'm sure you should be able to replicate the issue |
still this bug is there and noone seems to care, if this is the case please close this issue and I will look for another solution as this is clearly not working for me; below again what happened today, it's BH, the calendar went ON at midnight (that's correct) but exactly 1h later it went OFF so all my automation failed the check as I obviously need this flag during the day and not just for 1h!! |
@papperone It's not that nobody cares, and I'm sorry you feel that way. Please understand that I'm only one person, and this project is done in my spare time, and for my own entertainment. This means that when I do have time to work on it, I work first on things that affect me personally, and second on things that I can reproduce reliably. I've seen this happen exactly once, even using calendars provided by others, including you. There's a unit test that checks this specific behavior, including checking that it shows as on multiple times throughout a day. The tests always pass. I even used a provided calendar and ran the tests with it for the same times of day in the same time zone, and the tests always passed - the behavior of showing "off" never happened. When I've addressed all of the open issues that are easier to work on, I'll work more on this. It could be years, especially if I have as little time to work on it as I have this year. Please remember, too, that since I don't work on it daily, half of the time I do work on it is spent re-learning how the code works in order to find and fix a problem. Please also remember that HA is a constantly moving target with far more people working on it, and working on it full-time. That means it's also a very fast moving target compared to this project, and most of the time I do spend on this is just making it compatible with the latest version of HA. |
Hello!
Using other calendar integration the state of the entity is 'on' when there is an ongoing event.
When using ics_calendar integration the state is only active some minutes, even if the event is multiple hours.
See the attached images.
The event is between 11:30 - 14:50 but the state was only 'on' between 11:30:40 - 11:34:41 (4 minutes)
The text was updated successfully, but these errors were encountered: