@sonicgoose said in My first Magic Mirror build in an old imac:

@sonicgoose said in My first Magic Mirror build in an old imac:

I’ve been doing the same thing with a 20" white Intel iMac, but have had one helluva time. None of the display controllers work with the native LG 1600x1050 display Apple put in these things, so I’ve basically gutted the iMac and am putting in a new display, etc.

Not to hijack the thread, but this is how mine turned out.

also not wanting to hijack thread… but what weather module are you using?

thanks

Richie

Nailed it down…

            occupiedCMD: {notification: 'PAGE_CHANGED', payload: 2},
            vacantCMD  : {notification: 'PAGE_CHANGED', payload: 0},

happy days, now i can go to bed!

@Meidlmarkus

Awesome… thanks I’ll try it out soon!

… worked like a charm!

howdy folks, just noticed that my cpu is running higher than normal so i taught restarting my mirror would sort it out but it didnt, even with pm2 magicmirror stopped its still showing that its running high. i did top and it shows npm running up to 25% on cpu

tried to upload pic but having problems, should see screen shot when click on like

restarting my pi seems to solve problem for a while, it reoccurs!

@sdetweil as always thanks for your help!

i think i need to bring in the expert: @Bugsounet have you any thoughts?

could there be a way to shut it properly if the mirror is refreshed?

@raf how did you solve it, incase anyone else hase the same issue?

and you can tell from that output that it hung?

I think its when i refresh MM, it doesnt close snowboy properly so when MM refreshes snowboy is open already and hangs?
EDIT* (I tested the theory and if i refresh my MM then snowboy goes into that error loop.)

would that make sense?

yup, thats done it. Any idea what would cause it to hang?

heres the result of that:

pi@MirrorPi:~ $ ps -ef | grep arec
pi         765 21495  0 16:23 pts/1    00:00:00 grep --color=auto arec
pi       25903     1  0 13:36 pts/0    00:00:00 arecord -D plughw:1 -q -r 16000 -c 1 -t wav -f S16_LE -

this is with MM shut down.

hi team,

so ive just noticed that after about 12 hours of being on i get a repeating error message of :

[2020-11-26 15:39:34.519] [LOG]    [SNOWBOY] Retry restarting...
[2020-11-26 15:39:36.595] [LOG]    [LPCM16] WARN: arecord: main:828: 
[2020-11-26 15:39:36.596] [LOG]    [LPCM16] WARN: audio open error: Device or resource busy

and it wont go away until i restart my pi, if i only refresh i still get the error.

i tried searching for an answer but didnt come up with anything, from with much, only found that something else is using it but dont know where to start. would the fact that i updated MMM-Assistant2Display via the MMM-Update-Notification
telegram app have anything to do with it?

or could it be if the MM is refreshed then snowboy thinks that it is busy and wont connect to it?

saw to check this and here is the result of ps -ef | grep aplay :

pi 23592 21495 0 15:35 pts/1 00:00:00 grep --color=auto aplay

Thanks,

Richie

glad to hear you figured it out, i know coming from a very limited knowledge base, trial and error was how i figured it out!

when you say dont add key bindings do you mean the module MMM-Keybindings or the keyBindings in the carousel config?

@raf

if its not working after that, im afraid i dont know, sorry

i dont know anything about ssh either