[dannyau]

BTW the fixes to the skin files are likely very easy - just go in to your skin folder and find this file:
OzWeatherTweaks-aeon.xml

...open that in a text editor and muck around with the values (and potentially fonts, looking in fonts.xml for hints) - and reload the skin after each change to check the outcome.  It should not take long to get it looking correct - once it looks right send me that file (and a screenshot) - and I can integrate it properly into the patcher, even without installing MQ9!

I couldn't get this one to work ,the fonts are completely different than aeon silvo ,it looks worse when I rename fonts in OzWeatherTweaks.

[bossanova808]

I just tried here at work on a vanilla Omega install and it gets stuck at the same place.  I'm done, I'm not going to spend any more time on something so rubbish (that should, frankly, be removed from the main Kodi repo as all it does is break people's installs - the only way to fix is to re-install or, if you know how, go into guisettings.xml and manually reset the skin in there - so God only knows how many installs this is breaking for people!!)

Just trash.

[bossanova808]

Just a note that of course OzWeather continues to work nicely with the new Kodi Omega (V21).

I have also updated the Skin Patcher for the new Confluence 1080p version available for Omega, as well as adding support for A Confluence Zeitgeist, bring the list of supported skins to:
Estuary, Estouchy, Amber, Aeon Nox Silvo, Aeon Tajo, OSMC, Confluence, Confluence Zeitgeist, & Xonfluence

[bossanova808]

(If you happen to be using the companion 2nd screen project (https://forum.kodi.tv/showthread.php?tid=375174), note there's a new server address for this - see: https://github.com/bossanova808/kodi.ozw...2nd.screen for details)

[Harbour]

Hello everyone,

I run Kodi on a Vero4K device using the OSMC operating system and the Aeon Nox Silvo skin. I've recently upgraded Kodi to the latest version: Build v21.1 (21.1.0).

After the upgrade, I noticed that the OzWeather extended features (specifically, the BOM radar images) that were previously working without issues have disappeared. To fix this, I reinstalled both the OzWeather add-on (now at v2.1.1) and the Bossanova808 repository (now at v0.2.7), along with the OzWeather Skin Patcher (now at v0.4.0). All these programs seem to be functioning correctly, and all dependencies are installed.

However, when I try to run the OzWeather Skin Patcher, I encounter the following error message:

"Exiting - is skin folder writeable? Error when backing up current myweather.xml."

I’ve checked the Kodi log files, and it has the following relevant messages:

info <general>: ### OzWeather Skin Patcher 0. 4.0: Patching
info <general>: ### OzWeather Skin Patcher 0. 4.0: Backing up current MyWeather.xml to MyWeather.xml.original
error <general>: ### OzWeather Skin Patcher 0. 4.0: ...failed!  Is the skin folder writeable?

To troubleshoot, I used PuTTY to check the permissions of the skin folder. I found that it is indeed writable, as I was able to create a backup manually without any issues.

Can anyone provide advice on how to resolve this problem? Is there something specific I might be missing or any additional steps I should try?

Thank you for your help!

[bossanova808]

@Harbour

OzWeather is at 2.1.3 currently - there were changes in dependencies with 2.1.2 and 2.13, so you should start by updating to the latest, however I guess that is probably not actually your issue.  But can't hurt.

Can you do that update, try again, the post a complete debug log for me to look at, please.

[Harbour]

Hi @bossanova808,

Thank you for your prompt response. I really appreciate your ongoing support for this amazing add-on!

Before I proceed with any changes, I want to make sure I understand correctly. Currently, version 2.1.1 is the latest version available in my Kodi repository, and no updates are showing. However, I've checked GitHub and noticed that versions 2.1.2 and 2.1.3 are available there. Can you clarify why I’m not seeing these updates in the Kodi repository on my end?

Additionally, if I choose to install from GitHub, will I lose the auto-update feature for future versions?

Please advise, and I’ll follow your recommendations.
Thanks again!

[bossanova808]

@Harbour
That's odd, it's definitely 2.1.3 for me and I can see it at the Kodi mirrors:
https://mirrors.kodi.tv/addons/matrix/we...ozweather/

So that should really be available to you.  I just turned on a spare system that I hadn't updated in a little while (CoreELEC) - and it immediately went off and found 2.1.3...so there's definitely something not right at your end there - perhaps ask at the OSMC and get that fixed first?  I've no idea why it is not showing for you, sorry.

If you install the zip from Github, I believe that will break auto updates (until you manually install from the repo again, anyway).  So ideally don't do that, and it shouldn't be necessary...

[Karellen]

Can you clarify why I’m not seeing these updates in the Kodi repository on my end?

Did you select Check for Updates from the left sideblade menu?

believe that will break auto updates

No, I don't think so. It is a Kodi repo addon, so should still update ok.

[Harbour]

Thank you both, @bossanova808 and @Karellen, for your quick responses and support!

While trying to fix the add-on, I uninstalled and reinstalled it from the Kodi repository, so I believe I should have the latest version available to me. However, I don’t see the "Check for Updates" option on the left-side menu. Could this be specific to the Aeon Nox Silvo skin? The options I see are: Configure, What’s New, Preview (disabled), Use (disabled), Uninstall, Versions, Disable, Auto-update (disabled), and Dependencies.

Is there anything else you suggest I should do, or should I seek assistance on the OSMC forum?

[Karellen]

don’t see the "Check for Updates" option on the left-side menu.

Via Settings>Addons

[Harbour]

I found and ran the 'Check for Updates' menu, but no updates are available. Any other suggestions? Should I try installing from GitHub, or would it be best to ask on the OSMC forum about why I’m not seeing the latest add-on update that’s available to others?

[Karellen]

Any other suggestions?

We will need a Debug Log that captures running the Check for Updates.

[Harbour]

I restarted Kodi, ran 'Check for Updates,' and then attempted to run 'OzWeather Skin Patcher,' which resulted in the previously mentioned error. Here is the log file:

https://paste.kodi.tv/vudogopuwu.kodi

[bossanova808]

So re: the addon updates I see:

2024-10-27 23:17:55.232 T:2887 debug <general>: CRepositoryUpdateJob[repository.xbmc.org] checking for updates.
2024-10-27 23:17:55.236 T:2887 debug <general>: CurlFile::Open - <https://download.osmc.tv/kodi/addons/omega/addons.xml.gz?sha256>
2024-10-27 23:17:56.186 T:2887 debug <general>: CRepositoryUpdateJob[repository.xbmc.org] checksum not changed.
2024-10-27 23:17:56.186 T:2887 debug <general>: CRepositoryUpdater: done.

which seems to imply OSMC is using it's own mirror, and looking there, it is out of date (leads to: https://ftp.fau.de/osmc/osmc/download/ko...ozweather/ - which only has 2.1.1)

Conslusion - you'll need help from the OSMC folks as their addon mirror appears to be not updating.

Skin Patcher:

No extra clues in there unfortunately (next time you might want to turn off the uPnP server to make a cleaner log, there's just endless uPnP logging in there, makes it hard to wade through...)

What is failing is this:

python:


if not xbmcvfs.exists(config.backup_myweather_xml):

  Logger.info("Backing up current MyWeather.xml to MyWeather.xml.original")

  success = xbmcvfs.copy(config.current_myweather_xml, config.backup_myweather_xml)

  if success:

    Logger.info("...done")

  else:

    Logger.error("...failed! Is the skin folder writeable?")

    Notify.error('Exiting - is skin folder writeable? Error when backing up current MyWeather.xml')

    sys.exit(1)

...which means the only thing it is trying to do at that point is copy that file.  My guess is that the user Kodi is running under can not write to that folder even if the one you log in via ssh can, or that somehow permissions are stuffed up following your upgrade.  You could ssh in and 'chmod -R a+rwx' that whole folder (the skin xml folder - /home/osmc/.kodi/addons/skin.aeon.nox.silvo/xml), I suppose, which should allow it to proceed for now, if it is in fact permissions...but if there's a permissions error more generally with your install, it might well get reset on the next skin update.