@MilkShake I tried editing my config.js with the following:

            {
            module: "MMM-Hotword",
            position: "top_left",
            config: {
                    recipes: ["with-AMk2v3_smart-mirror.js"],

                    }
            },


            {
            module: "MMM-AssistantMk2",
            position: "top_left",
            config: {
                    assistantConfig: {
                            latitude: 55.749842,
                            longitude: 12.497128,
                    },
                    recipes: [ "with-MMM-Hotword.js" ],
                    addons: true,
                    },
            },

But it crashes my MagicMirror. If I remove “addons: true,” the mirror starts and the two top_left positions are empty.

Hi,
I think I got MMM-AssistantMk2 and Bugsounet’s https://github.com/bugsounet/addons installed successfully! Used the same credentials.json file as I used in the other Assistant setup and tested with node auth_and_test.js.

It’s can become quite confusing with all these modules and addons. Can anyone elaborate on what is needed configuration wise, to allow for voice activation of AssistantMk2.

I guess addons need to be activated for Assistant and HotWord needs a configuration of sorts. I will have a look at this later.

Best
MilkShake

@Bugsounet That seems like a good way to go! I’m mostly just after the voice activation for the Assistant, but I’ll go with anything that works. So would the process be:

1. Install MMM-AssistantMk2 from https://github.com/eouia/MMM-AssistantMk2/wiki/Installation
2. Install MMM-AssistantMk2 Plugins embedded with addons.js from https://github.com/bugsounet/addons

?

Thanks for all the help guys!

@Sean said in Working Google-Assistant on Raspbian Buster and 4b:

@MilkShake
Hotword is just one method to activate amk2. If you prefer, any other methods can be used. - touchscreen button, hw button, sensors like pir, 3d gesture detector, touchscreen gesture, finger snapping, or Any module can emit some notifications of MagicMirror.

Yes ok :) I would like to be able to enable the Assistant using voice, so HotWord seems like the way to go. The mirror has a pir sensor also for turning on the screen, built into the side of the frame, so it can be activated by hand movement.

Since I managed to get the regular assistant working on the PI, I will have a go at Assistant-Mk2 and HotWord tonight. Hopefully it will just install :)

@Chris Hey, thanks man! A little bit disheartening after getting it to work on the pi, but I will definitely restore the pi once again and give it a try. Am I right in understanding that you need some software to listen for an activation command, e.i. HotWord? I think I succeeded in installing MMM-AssistantMk2 earlier, but I did not get HotWord to work, after which I gave up.

Hi All,
I have a Magic Mirror installation running on the new Rasp4b and Rasbian Buster. I tried getting MMM-AssistantMk2 and MMM-Hotword working using various documents on here, but could not get it to work, so I tried another route -> getting Google Assistant to work on the Raspberry. It works now.

Is there any way from going from a working google assistant to implement it into the Magic Mirror and can anyone point me in the right direction?

Best Regards and thanks!
Milkshake

@Sean Ok, Thank you dude. I will put more effort into it :)

Hi Huys, I am trying to follow this guide however I have trouble finding some of the folders after the install.

In Step 5: The path ~/MagicMirror/modules/MMM-Hotword/node_modules/snowboy does not exist. I found Snowboy in ~/MagicMirror/modules/MMM-Hotword/snowboy instead.

In Step 5 after installing the assistant, I cannot find the folder scripts in ~/MagicMirror/modules/MMM-AssistantMk2 to make them executable.

Does anyone have an idea why that could be? I am running the latest Rasbian Buster distribution.

Best Regards
MilkShake

I found a solution for my monitor SAMSUNG S24F354 using:

DISPLAY=:0 xset dpms force on

DISPLAY=:0 xset dpms force off

This seems to work right now from the shell. Turns the monitor instantly off/on. Last night when trying with the PIR script, it didn’t work however, returning an error when calling shell scripts: the server was lacking dpms. This must be because DPMS was turned off as a part of the MagicMirror configuration.

I have a fresh install right now and just verified that these commands actually works. Now to get the PIR sensor working with the shell scripts.

Hi,
I know I am going to be flamed for asking this, but here goes…

I am trying to implement a PIR sensor on a Raspi 4b to turn on the HDMI output when activated. I have read page up and down of this issue and have seen different possible solutions, but nothing that works for me.

I can use tvservice -o to turn off HDMI just fine. When I use tvservice -p again, the monitor turns on, but remains only with backlight.

I have read something about adding a resistor on the powercable for the monitor, but have anyone found a solution to this? Is it because I am using a specific monitor or is this a general problem?

Best regards
Lars