[Jeffers24]

That is exactly what I initially saw when I realized the add-on broke. Did you follow the method I described above? If so, does the machine you pulled the data from actually pull the weather data there? If THAT machine doesn't work, then it won't work on a new machine. You have to have a working cookie from another installation to make it work as I described above.

Let us know.

I think the issue happened when I updated to Kodi 21 from Kodi 20 on my W10 Laptop.

I copied the whole weather.multi settings file from an older install over the Kodi 21 settings file and it now works again 

That is good, but you should follow the step about updating the time in the cookie file so that it doesn't expire! As I understand it, the time that you have now is when it last worked and was able to parse the cookie. With the issues going on now, that clock ticks down to expiration since the addon isn't updating it.... Now, I could be wrong on that, but since Ronie said to do that as part of the workaround, I am surmising that is why he mentioned it. Some cookies are persistent, some have time clocks on them... the server itself will determine that. And since my trailer stopped working from November to now, I suspect the cookie has an expiration date and will time out, so do yourself a favor and follow the step to update the time index as Ronie mentioned and I outlined on how to do.

If I'm wrong anywhere, someone will chime in and make the correction, but as far as I can tell, I think my logic is correct.

Do I do as in my screenshot?

Do I only have to do this once?

[kittmaster]

I think the issue happened when I updated to Kodi 21 from Kodi 20 on my W10 Laptop.

I copied the whole weather.multi settings file from an older install over the Kodi 21 settings file and it now works again 

That is good, but you should follow the step about updating the time in the cookie file so that it doesn't expire! As I understand it, the time that you have now is when it last worked and was able to parse the cookie. With the issues going on now, that clock ticks down to expiration since the addon isn't updating it.... Now, I could be wrong on that, but since Ronie said to do that as part of the workaround, I am surmising that is why he mentioned it. Some cookies are persistent, some have time clocks on them... the server itself will determine that. And since my trailer stopped working from November to now, I suspect the cookie has an expiration date and will time out, so do yourself a favor and follow the step to update the time index as Ronie mentioned and I outlined on how to do.

If I'm wrong anywhere, someone will chime in and make the correction, but as far as I can tell, I think my logic is correct.

Do I do as in my screenshot?

Do I only have to do this once?

Absolutely correct (only once unless you walk away from using it for a few months, then do it again), that is the only change to make.

Take a look at how OLD your current cookie is, and I'm sure due to expire at some point, but maybe it hasn't because you use the skin enough for it to "update" the server and it resets somehow on the server side records... (purely a guess on my part). I say that because my cookie was "younger" than yours... i.e. November 2023 and when I started up the trailer, it was broken.

So having a much newer timestamp will trick the server that at some time, you were "there" and it won't expire. (Purely speculative based on what happened to me).

That is the basic idea of the workaround hoping Ronie can fix what Yahoo has changed.

[kittmaster]

To follow up on my last post, I am going to check my TV in the living room and TV in the bedroom and see if those still work, the bedroom TV (Madnox) isn't use as much but usually pinged monthly or so, the living room every day, and if THOSE still work, that might add some support to my logic regarding time away cookie expiration.

Will report back later today as I have to travel home for some stuff.

[Jeffers24]

To follow up on my last post, I am going to check my TV in the living room and TV in the bedroom and see if those still work, the bedroom TV (Madnox) isn't use as much but usually pinged monthly or so, the living room every day, and if THOSE still work, that might add some support to my logic regarding time away cookie expiration.

Will report back later today as I have to travel home for some stuff.

So by putting todays date into the multi-weather settings file, what does that mean/do?

Will multi-weather stop working again in a week, a month, how does this work, how long till I get the problem again?

[kittmaster]

To follow up on my last post, I am going to check my TV in the living room and TV in the bedroom and see if those still work, the bedroom TV (Madnox) isn't use as much but usually pinged monthly or so, the living room every day, and if THOSE still work, that might add some support to my logic regarding time away cookie expiration.

Will report back later today as I have to travel home for some stuff.

So by putting todays date into the multi-weather settings file, what does that mean/do?

Will multi-weather stop working again in a week, a month, how does this work, how long till I get the problem again?

I can't answer that as I don't know what Yahoo's cookie timeout value is, nor do I think anyone does outside their DEV team.

But let's look at the scenarios, your cookie is from last May, 2023. Mine was November 2023, mine expired, yours did not, simple deduction says that as long as you "use" the weather feature time to time, it will update their servers to extend the life of the cookie. In my case, I had ZERO access to the device that expired in my trailer, then it called home 6 months later after winter when I restarted Kodi, blamo, cookie expired, add-ons not working because it can't acquire an updated value set.

That is my interpretation of these two single events and both have clear outcomes, so it stands to reason that as long as you keep using Kodi, maybe click into the weather feature, say weekly, it should last a good long while until hopefully Ronie can find a workaround......and if not, then your run will be only as long as the cookie is valid and then we all break when our cookies expire... addon goes in the trash... but I can't say if Ronie will find a workaround, he seems pretty frustrated by the recent Yahoo changes......which will be a time suck for him to sort out. So we just have to hope that he can find an elegant solution for the issue or he will notify us all that this is the end of the road for this addon or we get an extension based on new code that continues to operate with their API.

This is a Yahoo thing, not a Ronie thing, they basically painted him out of the box, hopefully he can find a way back in that is valid and doesn't create issues for him/Kodi.

So use in good health until otherwise notified.

Greetz.

[kittmaster]

To follow up on my last post, I am going to check my TV in the living room and TV in the bedroom and see if those still work, the bedroom TV (Madnox) isn't use as much but usually pinged monthly or so, the living room every day, and if THOSE still work, that might add some support to my logic regarding time away cookie expiration.

Will report back later today as I have to travel home for some stuff.

So by putting todays date into the multi-weather settings file, what does that mean/do?

Will multi-weather stop working again in a week, a month, how does this work, how long till I get the problem again?

I forgot to answer the first question, I had posted the answer above, but for a quick answer, it "tricks" the server into thinking you have been there...... like as of "today" when you put that value in... closing the cookie expiration time gap. You are basically cheating "their" clock because the server thinks you were there within the last 24 hours. By leaving the old value, you risk them have some hard limit that forces a cookie refresh... and if it doesn't refresh, you lose your weather data... so you are giving the cookie a shorter "age" as far as their servers are concerned and should allow you to use the cookie without worrying about if it will expire..... that is gist of the situation as I understand it.

[Jeffers24]

To follow up on my last post, I am going to check my TV in the living room and TV in the bedroom and see if those still work, the bedroom TV (Madnox) isn't use as much but usually pinged monthly or so, the living room every day, and if THOSE still work, that might add some support to my logic regarding time away cookie expiration.

Will report back later today as I have to travel home for some stuff.

So by putting todays date into the multi-weather settings file, what does that mean/do?

Will multi-weather stop working again in a week, a month, how does this work, how long till I get the problem again?

I forgot to answer the first question, I had posted the answer above, but for a quick answer, it "tricks" the server into thinking you have been there...... like as of "today" when you put that value in... closing the cookie expiration time gap. You are basically cheating "their" clock because the server thinks you were there within the last 24 hours. By leaving the old value, you risk them have some hard limit that forces a cookie refresh... and if it doesn't refresh, you lose your weather data... so you are giving the cookie a shorter "age" as far as their servers are concerned and should allow you to use the cookie without worrying about if it will expire..... that is gist of the situation as I understand it.

How/What is updating the date and time etc. in the multi-weather userdata settings, do you know?

[skypichat]

To those who have an existing working copy and trying to get other systems running, you can follow this method which worked for my laptop.

Ok, so I have it operational on my laptop, will be passing the modified settings.xml file to my fire device to see if it follows, but thus far, complete uninstall of weather.multi, reinstalled version .25 and it updated to .26 via the add-ons browser.

When I load the weather from the main menu, totally nil, just the baseline stuff.

I exit Kodi, go to the path:

(Windows 10) .....\AppData\Roaming\Kodi\userdata\addon_data\weather.multi\settings.xml"

However, the folder weather.multi does NOT exist. Therefore, I manually create it.

I copy my working unmodified settings.xml file from a working machine to the new laptop but DO NOT START Kodi. 

Go to the website: https://www.epochconverter.com/ as mentioned by Ronie to REPLACE the time to whatever it is when you arrive there, COPY AND PASTE that value to the settings.xml file:

(Windows 10) .....\AppData\Roaming\Kodi\userdata\addon_data\weather.multi\settings.xml"

Save the settings.xml file

Start Kodi and it should be working:

Thanks for this fix.
Works perfectly for me. Wait for a real fix.

[ashlar]

With this being broken (I checked my old installs but they were broken too...), am I correct in understanding there's no working weather addon currently available?