Thanks for sharing Brian. However, assuming subsequent uploads would over-write that file, it would be very tedious to maintain long-term, especially on large systems.
I do agree that the problem seems to have gotten worse in the last few months.
toggle quoted message
Show quoted text
--- On Thursday, March 27, 2025 at 4:36 PM, Brian Matson wrote:
Like everyone else, I've been battling this for a while.
Although, it seems like lately it has gotten much worse.
Let me preface this next statement with ... I haven't heard from this client
regarding this issue since I implemented my "trial" fix. (We all know that
just because a client hasn't reported back doesn't mean there isn't a problem.)
This was my "fix".
1. Use FileZilla to connect to the TSW panel and copy the "Core3config.ini"
file from the \romdisk\user\ directory.
2. Edit the "Core3config.ini" file with Notepad++.
3. There is a section in the config titled [WeatherApp], and I noticed that
many of my panels that were running the exact same VTP file had different data
here under the "defaultLocationData=" section.
4. I copied the "defaultLocationData=" line from one of the good, working TSWs,
making sure that it had everything correct (city, state, country, zip, lat,
long).
5. Upload the new "Core3config.ini" file to the panel and reboot it.
So far, this has "fixed", as far as I know, the few panels I have tested it on.
It should go without saying that I did all of the proper steps with the
"Core3config.ini" file (make a backup copy and only edit the parameters related
to the weather app).
It seems ridiculously "aggressive" to do with every touch panel deployed in the
field.
Maybe it will work for you.
The real answer is that Crestron needs to dedicate at least one software
engineer to fixing these "nagging" issues that plague all of us!
These seemingly small things are a "black eye" on the Crestron name.
Good luck!
