@paviro I am interested. Will figure out if the date works for me in the next week.

@broberg Thanks for flagging them. @paviro mentioned he has a small mathematical captcha on the login page, however it seems as if the bots figured out how to solve it.

@Mar I don’t know the concrete differences between these commands. I guess you will have to look at the man pages, or search for some documentation. I would just use the commands, which work (best) for your Pi. Also why is it a 2 and not a 7 in your last command?

Which of these commands works best for a Pi is probably depending on model, firmware, and maybe other things.

@cowboysdude So you would go with sub-categories, rather than defining new base categories? It not completely clear to me though, which categories you would split, and which subcategories you suggest? Or do you just want example below the categories, so it is easier to see where a module should go?

Also, maybe the future should go more into the direction of @MichMich’s module beta for showcasing modules.

@B4rth Please note that a notification never has a dedicated receiver. It is always a broadcast to all other modules. But sending notifications should definitely work with the module. Is your button working? If you are struggling with the correct URL for sending notifications, you can use this fiddle to build the correct URL.

The below config should be a simple example for showing an alert (it sends a notification to all modules and the alert module reacts to it):

{
    module: 'MMM-Buttons',
    config: {
        buttons: [
            {
                pin: 25,
                name: "test_button",
                longPress: {
                    notification: "SHOW_ALERT",
                    payload: {"title": "Hello World", "message": "Long Press!"}
                },
                shortPress: {
                    notification: "SHOW_ALERT",
                    payload: {"title": "Hello World", "message": "Short Press!"}
                }
            }
        ]
    }
},

Make sure to check that you are using the correct pin number and change the notification config, if you want another module to react.

@yawns Actually I was talking about modules for configuration purposes (Mobile App, Admin Interface, …), but maybe they should just belong to the general System category.

@lucallmon said in Physical button:

you guys were no help. lol.

This is what fixed it: https://www.raspberrypi.org/forums/viewtopic.php?t=68183&p=497867

@lucallmon That is just rude and unnecessary in my opinion. Keep in mind that everyone here is doing this voluntarily and (usually) in their free time. Maybe you should not crosspost next time, only discuss problems related to the MagicMirror project and keep a friendly and respectful attitude towards everyone around here.

For reference: I started a similar discussion a few months ago here. Except for the weather/environment category, all have been created.

@cowboysdude What changes do you suggest?

I think Utilities is the category that needs “refurbishing” the most. It is basically the category all modules go in, which have no other fitting category and we probably need one like it, but maybe we can try to split it up. My suggestion from back then still stands, we could introduce a Weather/Environment category. Are there enough module to justify a Smart Home, a Sensors (GPIO integrations), a Voice Recognition or a Configuration category?

Also I agree with @yawns, new and changed categories would maybe be better than splitting some categories another time.

@strawberry-3.141 Thanks for tagging. I updated the commands to not include additional single quotes.

@zichao92 It usually should not start multiple helpers. You could insert a console.log("Script started!"); before the PythonShell.run(...) and see if it appears multiple times in the log?