@strawberry-3.141 changed, thank you!

I removed the Dom update and it seems to work.

@Mykle1 I ended up copying and renaming the entire module! Worked way better than my silly workaround. Thank you! :)

I’m trying to append alarm objects to the alarms array
This is my code so far.

// SET ALARM
        if(notification === "SET_ALARM"){
            var mqttData = JSON.parse(payload);
            this.config.alarms.push({time: mqttData.hour+":"+mqttData.min, days:
 [1,2,3,4,5,6,7], sound: "alarm.mp3", title: "Alarm", message: mqttData.msg});
            this.updateDom(300);            
            console.log("alarm obj: "+this.config.alarms);
        }

However, in the console it shows only one alarm object.

Note: I have one alarm set in the config file

@strawberry-3.141 great, that’s perfect I’ll take a look thank you!

I’m trying to write my own module that will allow me to set the alarm for the MMM-AlarmClock module through buttons attached to your Pi.

I have the code that will read my button inputs, I have the code that will send the notification to set the alarm and I have my buttons on a PCB wired to my Pi.

There are 5 buttons: one ‘confirm’ button in the middle and 4 around it that count as arrows (left, right, up, down).
This way you’ll be able to set it number per number (kind of like the iphone alarm setter but without animation).

However, I just can’t seem to figure out how to show a popup window that will allow users to set the alarm in.
I know this is probably very simple, but I’m fairly new to JS. I’ve looked at the alert and iFrame modules but can’t really figure out how to use those for my module or if that would even make sense.

This would be the flow:
Press confirm button > open small popup window on top > push up or down until number matches time > push right or left to set next or previous number > repeat > confirm > send notification

My apologies if this was way too much information.

@Mykle1 this was indeed the alternative solution I had in mind! I managed to get it to work now, but it looks a bit iffy since both instances of the module will receive the incoming data and so it will be displayed on the screen twice (which doesn’t seem to happen with outgoing data). I’m going to try see if I can manage to display it only on one of them and otherwise I’ll revert to the alternative you suggested! Thank you :)

Hello,

I was wondering if any of you know how to actually subscribe and publish to a topic using this module? I currently tried adding two different instances of the module to the config file and have one set as sending and one as receiving but that just causes the module to crash and go offline.
Has anyone figured out how to do both of these at the same time?

Hello,

I was wondering if any of you know how to actually subscribe and publish to a topic using this module? I currently tried adding two different modules to the config file and have one set as sending and one as receiving but that just causes the module to crash. Has anyone figured out how to do both of these at the same time?

@strawberry-3.141 I understand, that’s actually really useful thank you! Can I pass parameters with a socketnotification?

Thank you so much for this module, it’s amazing and really easy to use!

I was wondering however, if I would want to let’s say set the alarm through some buttons attached to my pi, would it be best to try and inject lines into the config file (which seems sloppy to me) or can I set it through the js file directly? Or do I just make a second setnextalarm function?

@axellejamous actually it’s really well explain in the snowboy docs. Just scroll down to the asoundrc section and follow the steps!
https://snowboy.kitt.ai/docs

I recently had the same issue.
Check what values you have in your audio file (cat ~/.asoundrc)
For me they were all 0 and changing them to 1 fixed my issue.

Like this:

@slametps Yeah had to do the same! But I downgraded to 1.7.9, so I’ll change it to 1.6.10 now thank you! :)

@bhepler I was! But I manages to fix the issue.
When checking npm versions I saw that electron was ver 1.8.1
I ended up rolling back to 1.7.9 and it works perfectly!
Have no idea why 1.8.1 results in a black screen though.

@aayush447
Ok. I seemed to have solved my issue, the MM works with npm start now.
Electron seemed to be causing the issue for me.

Try this:

and then:

Then just try running npm start in the MagicMirror directory.

I’m not sure why, but this solved it for me! Since you seem to have the same issue it might solve yours too.

@aayush447
Severonly works perfectly, all modules come up like they should and no errors

Hello!

I was wondering if any of you could help me.
I’m basically having the exact same issue as this topic, except the “nl to en” fix isn’t working for me. I’m running the MM with it’s basic config file.
Runs fine on serveronly, but get a black screen on npm start.

I’ve updated everything from my pi to my os to my node modules, but nothing seems to be working. There also don’t seem to be any errors.