With the end of DarkSky API, I’ve forked this and updated it to use PirateWeather. https://github.com/gonzonia/MMM-BMW-PW
All coding credit goes to @Mykle1 . I pretty much just changed the name and a URL. Pirateweather does not support languages though and that was removed.
I’m just going to rebuild. I’ll let you know if I hit any snags. Thanks again.
@cowboysdude Thanks! I might switch to that. I’ve had to rework it a little because the URL wasn’t getting set except at the first call. I just moved setup for that into the getMenuData and I think it’s all working now. I’ll give it a day to run and see what happens tomorrow before I try messing with it again and update the file on github.
-updated to fix grammar
@sdetweil Just to close the loop on this. I updated MMM-Pir (there was another update soon after I posted) and switched to the updated MMM-Scenes2 and everything seems stable now.
@sdetweil Just to close the loop on this. I updated MMM-Pir (there was another update soon after I posted) and switched to the updated MMM-Scenes2 and everything seems stable now.
Also, I’m using the xrandr mode for mmm-pir since I’m in Raspbian 11 and when I use dpms it doesn’t wake the screen for some reason.
@sdetweil I know. It used to all work great. I don’t think Scenes has updated in a while.
MMM-CalendarExt3 and MMM-pir have both had updates though.
To clarify, when I say disappear, I mean that they are no longer on the screen.Not just that the data is empty. The headers, dates, etc. All not visible. I’ve just restarted recently, I’ll try to look at the page source next time it happens.
Recently I noticed my Calendars disappear after a few hours. I’m not sure when it started. If I VNC into my mirror and refresh or restart the mirror they come back only to stop appearing a few hours later. I see no errors in the log.
I’m using
MMM-CalendarExt3 and MMM-CalendarExt3Agenda in conjunction with MMM-Scenes, the instances that are only on specific scenes are the ones that disappear. I have another instance of MMM-CalendarExt3Agenda that is on all the scenes and that one seems to stay, so I’m wondering if it’s an MMM-Scenes issue.
Edit: I’m also using MMM-Pir. I’m wondering if that might be doing something.
@sdetweil This is helpful, thank you. I guarantee I made no changes though. I think it’s just that it needs to use npm run update
I just did a reinstall for now, but I would like to know what I should do to fix this in the future
Okay, sorry to revive this. I saw there was an update available so I went to update.
I did a git pull and got this
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.
From https://github.com/bugsounet/MMM-Pir
3a5bcdb..1fee537 master -> origin/master
fc5b3f6..658a322 dev -> origin/dev
Updating 3a5bcdb..1fee537
error: Your local changes to the following files would be overwritten by merge:
MMM-Pir.js
components/cronJob.js
components/governorLib.js
components/motion.js
components/motionLib.js
components/pirLib.js
components/screenDisplayer.js
components/screenLib.js
components/screenTouch.js
node_helper.js
Please commit your changes or stash them before you merge.
Aborting
The thing is, I know I have made NO CHANGES to any of those files.
Should I run a pull.rebase? Would that fix it ?
I think I had the GPIO correct originally. Went back to that and it’s working.
@htilburgs yes. I was using mode 9 in the old version. When I looked it up I thought that’s what corresponded. Im on Pi OS 11 and Wayland is for 12 according to the read me