Module Developers

@ankonaskiff17 ah, yes. that’s likely fullscreen below, or inserted at the same place, Prime example of fullscreen below being used is MMM-BackgroundSlideshow.

Fullscreen above, I don’t know of anything using it, other than the built in alert module.

@ankonaskiff17 What kind of discussion were you looking for? They’re pretty obvious how they’re used. fullscreen_below is your background layer, fullscreen_above is your foreground layer.

Other than that, they’re the same as anything else.

I kinda like Sam’s explanation. Only thing I would change is that there’s technically two backgrounds. The background on screen, and the background off screen (No position)

@swvalenti Here’s my weather page from Wunderground

https://www.wunderground.com/dashboard/pws/KNYELMIR44/graph/2021-07-24/2021-07-24/daily

@c1olli NICE!!!

@mdlefevere Thank you!

@majorc They look REALLY awesome!! I’m putting mine on the pole tomorrow…it’s a weekend so I get to play LOL.

Got the 10’ black iron pole all ready to go… mount is ready. Just a matter of installing it and putting the station on top

I did find this you may want to look at ->

https://cbornet.github.io/netatmo-swagger-decl/#section/Authentication

@ankonaskiff17 That’s why it’s better that instead of for instance and image in a module is written like this:

width: 110px;
height: 125px;

that it be written

width: 35%;
height: 37%;

The percent works on space where the px is what it is.

You can always make a module bigger by going into the custom css and doing something like this:

MMM-Whatever

custom.css

.MMM-Whatever {
width: 400px;
}
or
.MMM-Whatever {
width: 90%;
}

BUT this may NOT give you the results you want… but it’s css so you can play with it and if doesn’t work change it back. I would keep all your changes in the custom.css file and back that up that way if you do an update to MM you won’t lose all your work.

I think you can do things like git stash but I’d rather just back the file up myself.
That way you’re only ever changing one file and not individual modules. Too much work. One file, much easier…

@mdlefevere No real answer for this… I’ve tried several times. I can turn it off but not back on…

Are you running a pi4 or pi3?

This was my answer to the pi3 and it works… cannot figure out the pi4

https://github.com/cowboysdude/Pir-Sensor

@majorc I went with Ambient Weather because your data gets uploaded to both Ambient Weather and Weather Underground.

Ambient Weather

For this you get an API key that will return your data in json format which is very usable to build your own module with. This is your weather data which means it’ll be VERY accurate for your area because you are the one capturing it.

OR

You can take the weather info you get back and put it into ANY weather module here and make it work.

They have helper libraries for the api for node js already. Because it’s your data the rate limit is NO more then 1 hit per second… which basically means you can up to the minute accurate weather data.

While I don’t really write too many modules anymore I will be making a new weather module for my mirror with my data

The reason why you don’t see Eve used in the US much is because they are more expensive compared to say Xiaomi products which most are half the price of Eve products.

I am running Home Assistant and I have Xiaomi temp/humd sensors, motions sensors, etc. Much less expensive and work very well.

@veldje I have solved this by including a “birthday” calendar from google and giving at an own symbol.
For that I have created an own calendar within google, transferred all birthdays to that (didn’t take long) and included that calendar into the config.