@sdetweil said in 2.32.0 to 2.33.0 fails due to "some node app still running":
ps -ef | grep node
Thanks for jumping in here. This command was really helpful. I wonder if I might make sense to change the error message from
“some node app still running, please shutdown MagicMirror and restart”
to
“some node app still running, run ps -ef | grep node to see running node apps and shut them down before continuing”
For others who might read this later, in my case NoMachine was the culprit.
Does anyone know if it’s possible to tell the updatenotification module that you want to skip an update?
Sometimes I don’t need an update, but I also don’t need a message continuously displaying telling me one is available. But on the other hand, I don’t want to disable the module because I want to be notified about future updates.
Or if there isn’t some built-in way to tell the module you’re skipping the update, is there some way to trick it to think you’ve already done it?
@sdetweil said
the design is a ‘mirror’ on a wall
I know this was the original design, but I’m assuming that there are other people like me who realize the value of this software, but are using it somewhat outside it’s original design.
In my case, I have two MM’s running in my house:
One is on my HTPC, where I bring up the HTPC interface when I want to watch something and I have a MM with MMM-BackgroundSlideshow running as a sort of MM-PhotoFrame hybrid when I don’t.
The other is my kitchen touchscreen computer that has MM 90% of the time, but the other 10% gets minimized to Ubuntu touch so I can bring up recipes.
Just an update on this. I don’t know if the methodology has changed or this is just an additional way. In my MM, it seems like the cursor is being hidden by
html {
cursor: none;
}
so it can be shown with
html {
cursor: auto;
}
(default would probably work as well)
TL;DR Anyone know of a way for MM to display data from an ESPHome device?
For a while now I’ve been using esp32and esp8266 microcontrollers to send household sensor data to my MM (for example https://github.com/balassy/MMM-RemoteTemperature), programing them with Arduino.
I also have a Home Assistant server, and so little by little I’ve been programing more of my household sensors with ESPHome, as it’s a lot quicker and easier, and the sensor data can also be used to trigger automations.
But still find my MM useful for at-a-glance info and would like to display some of the same sensor data there as well.
Does anyone know of a module for MM that could display data sent from ESPHome? For most things, the data point would include an icon, label, value, and symbol.
Thanks, @sdetweil That was the ticket.
From both the name of the option and the fact that the description and example don’t say anything about including a time format, I assumed this was not the place to set that.
I think I had even tried doing it at one point and it didn’t work – but I probably hadn’t tried it with urgency:0 and getRelative:0 set.
I’m going to put in a pull request to try to make this a little less confusing for others in the future. Can you tell me if this sounds okay?
CURRENT ENTRY
Format to use for the date of events when using absolute dates. (version <= 2.16.0) From version 2.16.0, this option will be used to format absolute and relative dates. (e.g. DD/MM/YY to change from the default MM/DD/YYYY)
Possible values: See Moment.js formats
Default value: MMM Do (e.g. Jan 18th)
PROPOSED CHANGE
Format to use for the date of events when using absolute dates. (version <= 2.16.0) From version 2.16.0, this option will be used to format absolute and relative dates. (e.g. DD/MM/YY to change from the default MM/DD/YYYY)
To show the event time along with the date, use a format like MMM Do HH:mm. Depending on configuration, may also require the options timeFormat:“absolute”, urgency:0, getRelative:0,
Possible values: See Moment.js formats
Default value: MMM Do (e.g. Jan 18th)
I agree. The number of settings and their interrelatedness is a little overwhelming.
My config already has the other three settings
{
module: "calendar",
position: "right",
config: {
maximumNumberOfDays: 2,
displaySymbol: true,
fetchInterval: 15 * 60 * 1000,
fade: false,
urgency: 0,
timeFormat: "absolute",
dateFormat: "ddd",
fullDayEventDateFormat: "ddd",
showEnd: true,
getRelative: 0,
showTimeToday: true,
colored: false,
calendars: [
{
url: "https://calendar.google.com/calendar/ical/ ... /basic.ics",
symbol: "c",
},
{
url: "https://calendar.google.com/calendar/ical/ ... /basic.ics",
symbol: "j",
},
{
url: "https://calendar.google.com/calendar/ical/ ... /basic.ics",
symbol: "t",
},
],
}
},
** I deleted and reposted my entry from yesterday becuse I realized in my various testing I had left off one of the options. This is my actual config. **
Both of the things you mention make logical sense, but neither seem to work that way in real life.
when showEnd is set to false (or left blank, as false is defualt), the event only shows the day and not any time
when showEnd is set to true, the event shows the day and the start time
neither option seems to show the end time (or end day) of an event
and showEnd works when I set it in the global section, but does nothing when I add it to an individual calendar entry
Is your MM behaving differently then mine?
I’m wondering if there is some mistake in the Calendar config documentation. The documentation seems to refer to two options named showEnd, which I don’t believe is possible.
Also, it’s not really clear what this option does. In my thinking, “end time of events” would mean I would have “Jan 18th 16:30 - 17:30” instead of just “Jan 18th 16:30” and “end of a date” would mean “Jan 18th - 21st”
But this doesn’t seem to do either of those. It seems like it adds the time (with formatting determined by dateEndFormat) so that “Jan 18th” becomes “Jan 18th 16:30”.
Am I understanding this correctly? If so, I can put in a pull request to change the documentation.
Thanks, but my objective in suggesting this is not simply to get different configs at different ports. That’s necessary, of course, but as you mention it can already be accomplished with multiple instances. (And for reference, this is what I’m currently doing.)
I’ve found the multiple instance method to have a few downsides that compound as the number of instances grows. I’m currently running two instances – where the difficulties are a pain but manageable. But I was thinking of adding some extra displays that would take me four instances – where the difficulties would become somewhat untenable.
multiple instances means multiple API calls and/or HTTP POST requests from my sensors. In the case of the HTTP POST requests, I have to use CNAMEs on my router to make my MM machine look like multiple machines and then program the sensor to run the same HTTP POST routine multiple times for each “machine”. Thankfully my router and sensor firmwares (OpenWRT and Arduino) allow for this, but others would not.
multiple instances means that I have to maintain multiple config and CSS files. In my case 90% of the config and CSS files are the same (formatting settings, API credentials, sensor data display parameters, etc.) so if I make changes in that 90%, I have to make notes (or use a file compare utility) to make sure the same changes are copied over to all the instances.
I guess my thought here is that many people have a pile of old phones and tablets sitting around collecting dust and adding functionality like this would make it very easy to repurpose those as useful extensions of their MagicMirror.