@sdetweil yes

@barucomx i need a short ics file from you that causes this problem so we can fix it…

@SdR shouldn’t have needed the reboot. if using pm2 to start mm just use the command pm2 restart 0

@Klinge is this on windows? as you did \MagicMirror

@sdetweil nice thanks

@SuseGigabyte no problem, see https://forum.magicmirror.builders/topic/67/forum-posting-tips?_=1601749531385

@Parvez hotword has been removed, and is no longer available. to use GoogleAssistant you have to install MMM-GoogleAssistant .also bugsounet has removed some of his modules

i can’t help you with this module. check config and position. you can add “disabled: true” to MMM-pages and some other modules to check the display

@knubbl need more info. can u show me the page that is asking for git info…

hi @grinly no worries : ) I agree, I think MMM-JsonTable doesn’t like the structure of the json message you’re getting back - it’s expecting to see information laid out in an array and isn’t set up to parse a different message structure. Your investigations into Node-RED sound interesting - it’s not something I’ve tried but just from a quick look you might well be able to get it to act as an intermediary between your inverter and MagicMirror. If you’ve managed to get Node-RED to call the inverter endpoint for the energy data then that’s a good start. You’re right, if you go this route I think you’ll still have to clean up/reformat the message for consumption by MMM-JsonTable. But the Node-RED documentation might help - it does look like there are ways to get data back to the module too - you could perhaps get MMM-JsonTable to call a Node-RED endpoint instead of the inverter directly, and Node-RED could serve “cleaned-up” json back to MM? https://cookbook.nodered.org/http/serve-json-content Another option might be to see if there’s an alternative MagicMirror module that can handle (or be configured to handle) a wider range of json (or XML) messages? Though you might have to get hands-on with a module to adjust it exactly the way you wanted. If your json message always follows the same format it shouldn’t be too hard to extract the values you’re interested in - I think there are some fairly straightforward modules that would give you an outline of how to request and parse json (e.g. MMM-stocks maybe?). If you wanted the output shown in a table you could take a look inside MMM-JsonTable and see how it’s done there too. Just scrolling the 3rd-party modules list there’s also MMM-Tabulator? I’ve not used this one either but it mentions displaying data from XML or json sources, so it might be worth a try.

@bynan yeh, updates… run the screensaver off script from here https://github.com/sdetweil/MagicMirror_scripts

@jeffeb3 said in default-calendar recurring events aren't being adjusted for the timezone.: and it is displaying those in the right timezone now. awesome… thanks so much for the extra effort to test…

I use a samba share from a linux box to all my devices and systems… window, pi, mac. i have access to the share on my mac… BUT not if pm2 starts MM… I get access denied… if I stop the pm2 instance and then start MM with npm start it works fine… this is the MMM-ImagesPhotos module, with a soft link (ln -s) to the share from the module folder.

in 2.13 we changed over to the node-ical calendar parser to fix a bunch of problems, and add support for microsoft timezone names… we didn’t know if this would impact other calendar modules, as we left in the ical (ical.js) calendar parser. we intend to remove the ical parser on the next release…(Jan 1 approx)

@Stoffbeuteluwe the code says variable updateInterval: 120 * 60 * 1000 in the config section for the module time in milliseconds, default 120 minutes

@RJDaPirate when it goes dark, open the developers window ctrl-shift-i on the keyboard, select the console tab and scroll up to see any errors. you can also filter messages by module, by putting part of the module name in the filter field, rain, for example let us know

I had this problem the last two days – out of the blue, the MM2 was running for over a year with no problem. I know the thread is old, but it pops up when searching here or on google for this error, so I wanted to add how I was able to solve it: I backed up the config, my modules and my custom css. Then I deleted the MagicMirror-Folder, keeping pm2 and everything unchanged. I cloned MM2, ran “npm install”, brought back the config, modules and custom css and ran “pm2 start mm”. Seems so easy now, but for two days I tried everything – except deleting the folder.

@KirC so that means buttons is not configured like u want

@Crime I already tried to fix it like that but sadly i didn’t worked… now i don’t know what to do and i don’t have the knowledge to fix it myself atm atleast .-.