Additional question as CSS rookie:
I’ve tried to identify the object of the header.

how can I address this correctly?
Sorry, I’m not able to figure this out.

My best guess is

.weather_forecast .header {
  border-bottom-width: 0px;
  color: black;
  font-size: 0px;
}

but this doesn’t work.
How do I make this right?

Thanks!
Ralf

Answer yourself is a nice sport :-)

• sometimes structured telling hepls thinking - or in other words:
  How I can I know what I mean before I’ve heard what I’ve said …

As I read my own words - I’ve seen that it might be a good idea to test, if the header must be set indentical in both instances…

• Leaving them both commented - so “blank” doesn’t work.
  Setting both to something “not null” at least survives some PIR-switch-offs …

Keep you posted.

• nevertheless with two headers it do not look nice so I’m still looking for a hint, how to get this done properly …
  Thanks so far.

Ralf

@wuermchen
The log info from MMM-FRITZ-Box-Callmonitor seems to be O.K. …
Regards,
Ralf

After having an exact look on this - this happens immediatly if MMM-PIR switches off the monitor and first “wake-up” resets the headers.

• So debug/debugging option doesn’t help here

Addition: I ran into “sync” problems in another module and the “debug” + “debugging” option has helped to resolve this - that’s the reason for being present in this config as well - to give it a try…

Good evening team,
as I wrote in another post I’m playing around with the weather (standard) module and today I finally was a bit successful and able to change the default icons in a way I like.
Works as aspected and different icons in different sizes are shown appropriately.

But:
after a while the header of both of the module-instances (I am using two instances of the module- one for current, one for forecast) switching back to default:

Only a restart of the mirror corrects this and the header appears as wanted (the header of second instance - forecast - is empty):

.

config.js for thes modules is as follows:

// Wetter aktuell für xxx

		{
			module: "weather",
			disabled: false,
			position: "top_right", 
            header: "CityName",
            classes: "weather_current", 
			config: {
				weatherProvider: "openmeteo",
				type: "current",
				lat: x0.24127,
				lon: 0x.61174403,
				showSun: false,
				debug: true,
				debugging: true,

			}
		},

// Wettervorherssage - 

		{
			module: "weather",
			position: "top_right",
			disabled: false,
			//header: "Vorhersage",
			classes: "weather_forecast",
			config: {
				weatherProvider: "openmeteo",
				type: "forecast",
				lat: x0.24127,
				lon: xx.6174403,
				debug: true,
				debugging: true,				

			}
		},

Any idea how to solve this?
Thanks a LOT

Regards,
Ralf

@sdetweil OK; good to know.
Thanks!

Warm regards,
Ralf

Hi team,

I’m playing around with the standard “weather” module - try to understand, how it works and how I can change something or even develop an own module.
During my journey I had a look into weather.css and there seems to be an error.
It’s possible that my assumption is wrong and that I miss something, than please ignore this…

I’ve found an additional space in line 39

.weather .weathericon,
.weather .fa-home {
  font-size: 75%;
  line-height: 65px;
  display: inline-block;
  transform: translate(0, -3px);
}

.weather .humidity-icon {
  padding-right: 4px;
}

.weather .humidity-padding {
  padding-bottom: 6px;
}

.weather .day {
  padding-left: 0;
  padding-right: 25px;
}

.weather .weather-icon {
  padding-right: 30px;
  text-align: center;
}

.weather .min-temp {
  padding-left: 20px;
  padding-right: 0;
}

.weather .precipitation-amount,
.weather .precipitation-prob,
.weather .uv-index {
  padding-left: 20px;
  padding-right: 0;
}

.weather tr .weathericon {
  line-height: 25px;
}

.weather tr.colored .min-temp {
  color: #bcddff;
}

.weather tr.colored .max-temp {
  color: #ff8e99;
}

this is the block

.weather tr .weathericon {
  line-height: 25px;
}

and the space is between “tr” and the following dot “.” .

this is not the case in the two following blocks.

Regards,
Ralf

@sdetweil OK, thanks.
Have done.

@wuermchen
Hi.
I guess it SHOULD work - at least it works for me at current github status (approx. 2-3 old - not sure what you have archived).
At my own initial setup I got the same error message and after some researches it was caused by refused authentication on the fritzbox side.

So I would start at this point initially - not at module side.
My first attempt was login without password (as possible for console) - this doesn’t work.
I’ve created a separate user on AVM side with full access to phonebook and so on and this worked from scratch.
I see that you have an explicite user/pw as well - so I would double check if this user exists on AVM side and do have the right access privileges.

For being sure I would recommend to delete all parameters from configuration you do not really need and experiment with the base parameters.
E.g. you have set the Port number - at default - I would delete this one.

I’m not sure if you are aware but you can find the documentation of the module in your module folder as well - you do not need the - closed - github entry.
“README.md” is the file.

Good luck!
Ralf