David Bezuidenhout

Well initially I still had issues but noticed I have a log error ``` 2025-02-12 06:10:17.927 ERROR (MainThread) [homeassistant.components.slack.notify] Error getting channel ID: SlackApiError("The request to the Slack API failed....

aha ok. that makes sense, not sure why I missed it. But happy to add the permissions for the fact that it does make life simpler. As for how I...

Now that I think about it. Is there a way one could specify the channel id instead of channel name, to reduce the api calls, so as to make the...

Think this is where the error is from: https://github.com/frenck/action-home-assistant/blob/main/action.yaml#L119 The config path may be sent via the environments file, but maybe the new beta uses something new/different. So my suspicion...

Ah ok I see this is the change. So in the past, it would parse the cli args directly. Now, it uses the script_args parameter passed to the function. Have...

Yeah I still implemented a work-around to get around the notifications that keep reminding me every day its not working. For now, I symlink the workspace config path to `/root/.homeassistant`...

Can confirm I have the same issue. Essentially what happen is, when loadshedding start, the entries are added to the calender correcty. When loadshedding ends, eg. both capetown and eskom...

> > Can confirm I have the same issue. > > Essentially what happen is, when loadshedding start, the entries are added to the calender correcty. When loadshedding ends, eg....

> Yeah, I noticed there's an issue. I'm testing a fix, but need load shedding to test 😂 Maybe downgrade to the previous version if it's critical, otherwise I'll post...