@sdetweil Thank you :)

@karsten13 said in Permanent size for newsfeed box?:

.module.newsfeed {
height: 200px;
}

That seems to be working perfectly, thank you :)

@sdetweil said in Is cloning to a new OS possible?:

@tippon clone is ok, but. you will have to do npm install in all the places where there is a package.json file

I had a feeling it would be something like that. At that point I may as well do a fresh installation and just copy the config.js over. No chance of missing a module’s dependencies then, or adding in a module that’s been commented out but not removed, for example.

@bkeyport said in Is cloning to a new OS possible?:

@tippon To speed reinstall - I have my config.js and custom.css symlinked to a common location outside the MagicMirror tree, and a bash script setup to clone and npm install every module I use, and reinstall the symlinks.

easy peasy…

My system backs that up nightly to a private github repository, and bam quick and dirty way to get my system back running when my pi crashes.

That’s a good point, I didn’t think about using it for a backup. I’ve got Github set up, but I haven’t got into the habit of using it properly yet.

A symlink would be really helpful for the MMM-Cryptocurrency module too. Someone’s made some mods to the MMM-Cryptocurrency.js to add functionality. It’s not merged yet, and that’s beyond me for now, so keeping the modified file outside of the folder would stop me from accidentally wiping it.

I might try for a best of both worlds approach - fresh installations on the Xubuntu system, then set up some scripts.

Thanks both :)

@lavolp3 @sdetweil Thanks for the replies, it worked perfectly! :)

I tried a space before and after ‘live’, and both at once. I made a separate entry for ‘delivery’ too, and put it after the ‘live’ line. The ‘delivery’ line wasn’t necessary, but I tried it as an override (which didn’t work), and liked the way it looked :D

{keyword: 'live ', symbol: 'music', color: 'Aqua'}, {keyword: 'delivery', symbol: 'truck', color: 'GreenYellow'},

@bravooscar That looks great, thanks :)

@tippon my pleasure…

@tippon said in Weather not working since MM update:

I realised today that I’m having a problem with MMM-fitbit2 too. I fixed the issue in my other thread here yesterday:

https://forum.magicmirror.builders/topic/14879/mmm-fitbit2-pythonshell-is-not-a-constructor?_=1617917654075

but updated Magic Mirror shortly after, so I’m not sure if the problem existed before the update or not.

The module loads and seems to work, but I’m only getting values returned for the calories I’ve burned and my weight. My food eaten isn’t updating, even though it’s showing in my Fitbit dashboard.

I know this probably isn’t related, but as both issues appeared at the same time I thought it was worth a mention just in case.

I’m really sorry, I’ve just found out that the reason that my food eaten wasn’t being updated is that my calorie goal had been deleted from my Fitbit dashboard. I use other apps that fill the same goal in, so I hadn’t noticed.

I’m still getting the weather issue though.

@vizulize yeh, i don’t know whay there is a python_shell lib… as exec and spawn are so easy…

@sdetweil parseInt and parseFloat sound vaguely familiar. I was teaching myself Python last year, but had to stop when the schools closed and my daughter was home all day.

Now that the schools are back, I’m hoping to start again. After trying out MagicMirror, I might learn Javascript first though. I find it a lot easier if I’ve got a real world project to learn about, and MM is more interesting too :)

Thanks again for your help :)

In case anyone sees this in the future, I’ve solved it for me setup at least. I found that using locationID along with lat & long and location caused the problem. Changing to just locationID fixed it for me.

weatherProvider: "openweathermap", roundTemp: false, type: "forecast", // current, forecast, daily (equivalent to forecast), hourly (only with OpenWeatherMap /onecall endpoint) locationID: 2657835, { module: "weather", position: "top_right", config: { type: 'current' } }, { module: "weather", position: "top_right", config: { type: 'forecast' } },

Changing the second weather module to forecast instead of hourly was needed in config.js too.