@sdetweil said > which class caused the smaller size?

Dear Sam,
don’t know!
have experimented a while to change several parameters in the developer’s console who could be associated with the size but none of my trials caused any visible change.

At least I could figure out (by the association with the filename) which CSS element is representing the icon.
This is (in my case)

.weather_forecast .weathericon

(I’ve (as many users) two instances of the weather module and gave them a classes definition to handle CSS for both instances different. In the Forecast instance (class weather_forecast) are the described symptoms located)

I’ve played around and have done some research and came to the conclusion that height could be the appropriate attribute.
For this reason I’ve added

.weather_forecast .weathericon  {
height: 30px;
}

to my custom.css and this exactly does the trick.

Where the “overnight” changes comes from - I have absolutely no idea and - see above - couldn’t even figure out any “change” …
Sorry for this.

• May I’m to dumb to figure it out …

Thanks a lot, anyway.
Warmest regards,
Ralf

@sdetweil OK, good news.
Then I’m really asking what happened to cause the described changes on my mirror.
It’s obviously “magic” again :-)

Regards,
Ralf

@sdetweil said

have you tried restarting MagicMirror?

Dear Sam, yes I’ve restarted the mirror several times, no effect.
Thanks to second link in your signature I was able to identify the CSS topic which addresses the size of the icon - but this was not neccessary earlier - worked without this.

IS there an auto-update mechanism?
(this would be bad…)

Regards,
Ralf

Dear team,
my MagicMirror ran stable for a pretty good time.
Now - for some unknown reasons - the icons (custom SVG files) for the standard weather module forecast becomes really tiny so nearly invisible.
I do not made any changes in the last past days. (really. :-) !)

Because it’s related to a “standard” module here my question: Is the mirror updating by himself?
And if this is the case - how can I avoid this?

Thanks a LOT for any idea.
Regards,
Ralf

@chrisfr1976 said in MMM-Temp2IOT:

The Temp2IOT project is not mine. But it is really great work.

OK, thought i was you :-) .

I’ve found the root-cause for wrong date:
Yesterday I’ve played primarily with the mirror-module to test if this works for me (yes, it works…).
Today I’ve done the soldering part and connected the sensors.
Now sensor data is transmitted and this seems to trigger attachment of time-marks.
Now the json record contains correct timestamp.

Regards,
Ralf

@cpcode OK, use it really seldom, so your findings are new to mee…
Good luck.
Ralf

@chrisfr1976
have solved it by myself…
Used @sdetweil 's tip with developer console and identified CSS classes for the icons.
Have set

.MMM-Temp2IOT .iconify {
    font-size: 0px; /* Symbole verschwinden lassen */
}

in custom.css -
works :-)

Warm regards,
Ralf

@sdetweil OK; will do.
Thanks.
Ralf

@chrisfr1976 cool stuff - I like it and it works without any problem.

Do you have a hint for me how I can disable the icons?
The text is sufficient for me.
I’ve tried a condition which never will be met: “condition > 100” but this doesn’t work.

Good work - especially the code for the ESP board, thanks a LOT!

Additional question: the api is posting a json record with Unix Startdate (“Thu Jan 1 00:00:00 1970”)?
Is this correct?

{
  "systemname": "tbd",
  "secure_counter": 0,
  "firmware": "2.3.06-b",
  "sensors": [
    {
      "name": "Sonne",
      "value": 0,
      "mean-1": {
        "value": "NaN",
        "count": 0,
        "period": 3600
      },
      "mean-24": {
        "value": "NaN",
        "count": 0,
        "period": 86400
      },
      "unit": "Celsius",
      "time": "Thu Jan  1 00:00:00 1970"
    },
    {
      "name": "Schatten",
      "value": 0,
      "unit": "Celsius",
      "time": "Thu Jan  1 00:00:00 1970"
    }
  ]
}

Warmest regards,
Ralf

@sdetweil , Cool!
Thanks a lot.

pi@smarthome:~/MagicMirror/modules/birthdaylist $ git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 3 (delta 2), reused 3 (delta 2), pack-reused 0 (from 0)
Unpacking objects: 100% (3/3), 584 bytes | 97.00 KiB/s, done.
From https://github.com/sdetweil/birthdaylist
   0c16aeb..e4013e9  master     -> origin/master
Updating 0c16aeb..e4013e9
Fast-forward
 birthdaylist.js | 31 +++++++++++++++++++------------
 1 file changed, 19 insertions(+), 12 deletions(-)

Can I now remove the debug-attributes?
Warmest regards,
Ralf