Hi,
There are a few things you need to do to add a SteelSeries gauge to a new page. They are:
1. add the necessary div tag(s) to the page HTML to placehold the gauge(s)
2. add the necessary script tags to the page HTML to call the SteelSeries javascript
3. configure the SteelSeries javascript file gauges.js
Since you have a correctly rendered (apart form current data) gauge on your page you have 1 correct (the placeholder clearly exists) and 2 correct (a gauge is rendered) and the issue is with 3.
In such cases using the browser/web console in your web browser (usually found under developer tools but name and location varies from browser to browser) while viewing the problem page will give you some clues. In this case when I view your page I see the following in the browser console:
Which tells me that indeed gauges.js cannot find gauge-data.txt. The solution is to alter the following setting in gauges.js (circa line 74):
realTimeUrlWeewx : 'gauge-data.txt', // *** WeeWX Users: Change to your location of the gauge data file ***
and add some path info. The trick in your case, since you are using one copy of gauges.js to support the Seasons skin and ss skin, will be to add path info that works for both your Seasons and ss skins. You will need to find a suitable absolute path that works for both, perhaps something like /Wetter/ss/gauge-data.txt or /wp-content/Wetter/ss/gauge-data.txt, the correct setting depends on you web server root and its directory structure. I suggest you make the changes to gauges.js on your web server monitoring the browser/web console for both pages until you have both pages working properly. This way you make changes/test immediately rather than having to restart WeeWX and wait for a report cycle to complete. Once you have the correct setting go back to your WeeWX machine and make the appropriate changes to skins/ss/scripts/gauges.js so that your changes will not be lost on the next WeeWX restart.
Note that if you wish to have the mouseover trend graphs display on both pages as well you will have a similar issue with the following setting in gauges.js (circa line 38):
imgPathURL : '', // *** Change this to the relative path for your 'Trend' graph images
Gary