@KristjanESPERANTO Sorry, typo, it is lower x. It start when I manually run npm start. When I manually run node --run start:x11 it works fine. When I manually run the script ./mm.sh it works fine. When calling it from the cron nothing. In my log I see the command node --run start:x11 but MM does not launch.

Hi,

Is there anything that can be done about the add at the bottom left of the Forum? It is blocking the posts. This was gone for a while but is now back and is a nuisance.

Hi.

I have been using crontab to start my MM for ages and it has always worked well. After updating it no longer seems to work. cron calls a script that has the following.

cd ~/MagicMirror
DISPLAY=0 npm start

Now, I have seen that it is suggest to use node --run start:X11 going forward and I have updated my start script with same but that does not seem to work either.

So my mm.sh now looks like,

cd ~/MagicMirror
DISPLAY=0 node --run start:X11

But as mentioned, this does not work.

Any ideas?

@nowayto Hi. That sounds more like something else. Have you checked the logs to see if you see any errors during the time when there is no update? Let me know if you see anything.

The retry will try 3 times, first after 1000 milliseconds and and then at 2000 milliseconds and the last time at 3000 milliseconds and will return a warning. The next time it will try is at the refresh interval which is whatever value you have set.

You can update if you want to check this out. You can let me know if you experience any issues.

I am thinking about making the retry interval configurable but not sure if it is warranted at the moment.

v2.2.0 Upgrade

I have decided to refactor the code to make it a little easier to manage

• Update growatt library to latest
• Added helper functions
• Add a connection retry in cases where connection to the Growatt server is down or interrupted
• Add better error handling

Current users do NOT have to update to the latest version unless you want to be on the latest version.

If you do decide to upgrade and experience any issues, please open an issue on the MMM-Growatt Github page.

The same updates were applied to the MMM-Growatt-Stats module. If you update and experience any issues please open a ticket at the MMM-Growatt-Stats Github page.

@Niggich Glad it is working for you now.

@Niggich Have you also check for any errors in the Dev console (shift + ctrl + i)

@Niggich said in MMM-WOTD:

not working with more pages and server mode

Not sure I understand the above.

The module works fine, works with MMM-pages and in Container (server only mode) I have tested this.

Can you check in the logs if you see any errors in the logs and advise?

@plainbroke You can target the selectors specifically in your custom.css like this:

#wotd-we {
  color: orange;
  font-size: 50px;
}

@sdetweil Agreed, all work is the same.

@sdetweil You provide your own list of modules and config alongside your compose and it all gets imported into the container. No need to go fiddle in the container itself.

@plainbroke There are instructions on the Docker website. Follow the link in my post above.

@KristjanESPERANTO Well, I wanted to see how it works? 😉 Wanted to build one that was preloaded with my own modules for my own use but then rethought the design a bit and see if I could build a generic one based on trixie. So yeah, just pure curiosity and to see if I could…🤣

Hi,

Firstly, I know there are a few out there and by far the one from @karsten13 seems to be the best and most well maintained out there.

I have created my container based on Debian Trixie and MMv2.31.0.

I am looking for testers to see if I have missed anything or if there is room for improvements. I have only been able to test this on my Windows laptop, don’t have a spare RPi at the moment to test this with.

All instructions can be found here mumblebaj/magicmirror:latest

Contributions are most welcome.

Thanks

@Nage1951 ChatGPT has been around for a while now. There is even a module built on it already. Checkout the 3rd party modules list, hamburger menu on top. Not sure if it still works but it is there.

@sdetweil Yeah, was reading that earlier when you posted it from another issue. Will see if I can pull the MM repo and have a look at the code in there.

@sdetweil and @redfishbluefish When I had the same issue with my MMM-NewsAPI module where if a user opted not to show a QR Code, it would create an empty div which took up space. I had to implement the following in code to dynamically remove the div for it if the option is not selected. You would need to have similar logic for if no alert results are returned you remove all traces of the parent div.

else {
                const qrCodeElement = document.getElementById("NEWSAPI_QRCODE")
                if (qrCodeElement) {
                    qrCodeElement.parentNode.removeChild(qrCodeElement)
                }
            }

This is how I have implemented it in my module, may not be the most elegant but works for me and the QR div no longer takes up the space if the user did not opt to show it.

@htilburgs Thanks for confirming. I double checked the icons available from weatherbit and compared to the list and they are all covered. Hopefully it was just a once off thing. 🙏

@htilburgs Good morning. I have just tested weatherbit using you lat and lon and not seeing any errors.

@htilburgs I will have a look at weatherbit. They may have changed icons.

Just a little busy today but when I get a moment I will definitely have a look.

I also require your lat and lon so I can get the data/icons for your region/area