@Mar for anyone else who is getting this an npm rebuild fixes it. from here https://github.com/atom/apm/issues/635

@PointPubMedia

                {
                        module: 'MMM-ProfileSwitcher',
                        config: {
                                includeEveryoneToDefault: true,
                                ignoreModules: ["alert", "updatenotification"],
                                enterMessages: false,
                                leaveMessages: false,
                                defaultTime: 15000,
                                timers: {
                                        "PAGE2":{profile:"default"}, //Switch to defaultClass after defaultTime
                                }
                        }
                },
                {
                        module: 'MMM-Buttons',
                        minShortPressTime: 0,
                        maxShortPressTime: 1000,
                        minLongPressTime: 3000,
                        config: {
                        buttons: [
                                {
                                        pin:23,
                                        name: "change_profile_1",
                                        longPress: undefined,
                                        shortPress: {
                                                notification: "CURRENT_PROFILE",
                                                payload: "PAGE2"
                                        }
                                },
                                {
                                        pin: 22,
                                        name: "change_profile_2",
                                        longPress: undefined,
                                        shortPress: {
                                                notification: "CURRENT_PROFILE",
                                                payload: "default"
                                        }
                                }
                        ]
                        }
                },

@istepgueu @Jopyth Whoo hoo got it.

MMM-Buttons.js: Semi colons on line 71/72 and line 86 needs to be changed to:

sendAction: function(description) {

where as it currently just reads:

sendAction(description) {

@cowboysdude Perfect, so I should expect it to shut off by the time the system loads to the prompt.

Yes it has two sensors, one for sensitivity and the other for how long to send the active signal. Suppose I’ll just play around a bit. Maybe i’ll try find the logs for wherever it tells you when cron jobs have run. Not having any luck so far. i might be doing the cron part wrong, i’ve never played around with cron jobs before.

Im thinking its the pir.py script as I’ve done the cron job right I think.

edit: locations of the startup and shutdown script in pir.py need to be updated! Doh!

@Jopyth Thanks for the response, and that seems to make complete sense. I missed that part in the documentation.

Though upon trying PINS 22/23 i am still getting the same result. The button.py program detects each individual click properly, but in the MM I have to double (sometimes triple) click the button so that it registers. I can see it registers as it shows up in the pm2 logs and my profile changes.

Im not sure if its an issue with the buttons as they are a standard 4 pin button and the test script works fine with them?

@tosti007 Thanks for updating your module so quickly! and obviously thanks for taking the time to respond and maintain.

@Jopyth It finally worked!!! :lifter_tone2: thanks so much. Ive spent days on this :(

Tried this last link you provided previously before posting but nothing was working, your support around getting node updated (and npm) was all that needed to happen first.

Thanks again!

@Jopyth Fixed!! I switched the 1 and the 0 in the watchHandler function of node_helper.js and solved the issue. Must have been backwards with how the button was being interpreted vs set up?

Put the 0 first, then 1.

Now the double click makes sense, the time between the clicks seems to have been what was counted as a valid min press time.

@istepgueu Well thank you for trying to help, its much appreciated.

@Hein-Jan Thanks for the workaround, i suppose rebooting nightly isnt ideal but if it fixes things I’ll give it a shot. I just don’t understand as it was working perfectly for so long, as I’m sure it is for others also. There must be something in either the wunderlist config or in the MM config that it doesnt like.