ha-solcast-solar: Solcast update-new uses an unknown action

The problem

I am getting this error- "Solcast update-new uses an unknown action Error ⸱ Reported by Automation The automation “Solcast update-new” (automation.solcast_update_new) has an unknown action: solcast_solar.update_forecasts.

This error prevents the automation from running correctly. Maybe this action is no longer available, or perhaps a typo caused it.

To fix this error, edit the automation and remove this action.

Select Submit below to confirm you have fixed this automation."

I can see the solcast_solar.update_forecasts is still available so not sure why I am seeing this error.

What version of Solcast Integration has the issue?

v4.2.5

What version of Home Assistant are you using?

2024.11.1

Diagnostics information

I am getting this error- "Solcast update-new uses an unknown action Error ⸱ Reported by Automation The automation “Solcast update-new” (automation.solcast_update_new) has an unknown action: solcast_solar.update_forecasts.

This error prevents the automation from running correctly. Maybe this action is no longer available, or perhaps a typo caused it.

To fix this error, edit the automation and remove this action.

Select Submit below to confirm you have fixed this automation."

I can see the

Logs debug/info/error output

I am getting this error- 
"Solcast update-new uses an unknown action
Error ⸱ Reported by Automation
The automation "Solcast update-new" (automation.solcast_update_new) has an unknown action: solcast_solar.update_forecasts.

This error prevents the automation from running correctly. Maybe this action is no longer available, or perhaps a typo caused it.

To fix this error, [edit the automation](http://192.168.1.5:8123/config/automation/edit/1725985653577) and remove this action.

Select Submit below to confirm you have fixed this automation."

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 25 (7 by maintainers)

Most upvoted comments

Someone mentioned on the community forum that they ended up with both oziee and bjreplay installed, and asked for assistance a couple of days ago.

It is not possible to set up two Solcast integrations bearing the same domain. Ozzie checked for that, and we check for that. If the manifest domain were changed however… Maybe. Not tried.

I tried having another custom_components folder solcast_solar_old containing 4.0.23 and it did nothing. HA chose 4.2.6. Tried calling the interloper aolcast_solar, wondering whether it was an alphabetic load thing. HA chose 4.2.6.

So the integration entry must point at the installed folder, ignoring the rest.

Ergo, if an install to a folder named other than solcast_solar had been done then its entry would do the same thing. It would ignore solcast_solar as the interloper.

When you remove a configured HACS repo it does not remove an integration folder. If you then remove the integration, the folder remains. You can re-add it, so removing repo in HACS just makes it unmanageable. I assume no upgrades will then be offered.

I then renamed the “orphaned” solcast_solar to solcast_old, manually put 4.0.23 in it and rebooted the entire VM. Tried to set up Solcast and it bombed with an exception. 4.0.23 is way too old it would seem, but it pre-dates me getting my grubby hands all over the code, and most closely resembles Oziee’s last efforts.

And that begs the question, “How is Oziee’s code even running?” Maybe I did something stupid with that test.

My next step would have been to set up BJ in HACS, download from there and see where things went.

I have been foiled for now.

But what we could not do is to cause a Home Assistant restart to make it stick/work seamlessly.

No, but we can do what HACS does, and that is do the “Restart Required” notification thing that HACS does - which is actually a standard HA call, if I recall what I spotted running in debug mode the other day. Let me find it and get back to you (tomorrow).

Now we are talking. #debug!

You likely still have Oziee’s repo enabled in HACS. Kill it. It is dead to you, and to the world. @BJReplay for the win.

2024-11-11 12:51:45.684 ERROR (MainThread) [custom_components.hacs] <Integration oziee/ha-solcast-solar> GitHub returned 404 for https://api.github.com/repos/oziee/ha-solcast-solar
2024-11-11 12:51:45.820 ERROR (MainThread) [custom_components.hacs] <Integration oziee/ha-solcast-solar> No manifest.json file found 'custom_components/None/manifest.json'
2024-11-11 12:52:01.307 ERROR (MainThread) [custom_components.hacs] <Integration oziee/ha-solcast-solar> GitHub returned 404 for https://api.github.com/repos/oziee/ha-solcast-solar
2024-11-11 12:52:01.430 ERROR (MainThread) [custom_components.hacs] <Integration oziee/ha-solcast-solar> No manifest.json file found 'custom_components/None/manifest.json'

The API count is seemingly pegged at 5/5. We’re a while away from UTC midnight reset, so that will come.

Some questions: Why is 5 set as the limit? You have two Solcast sites. You have ten API calls as a hobbyist, so why not use them all? The integration works this stuff out, because two sites.

Solcast dropped an API call that gave us the current state of play re. API usage on a plate. We now have to ‘guess’, which is why the integration now has a config option for the limit. If you have two sites, set to ten. Each update will use two, because two sites and the integration will keep track of this.

something changed after that and it . [trails off…]

saw a red door, and wanted it painted black? 🤣