MMM-Hotword does not trigger MMM-AssistantMk2?

[A Former User]

@ACRONN
your hotword configuration is not matched to current version. and you dont need notificationtrigger for basic usage.

[sdetweil]

@ACRONN said in MMM-Hotword does not trigger MMM-AssistantMk2?:

MMM-Hotword.js:249 Uncaught TypeError: Cannot set property ‘innerHTML’ of null
at Class.status (MMM-Hotword.js:249)
at Class.socketNotificationReceived (MMM-Hotword.js:149)

hotword had an error. and so will not be working.

[ACRONN]

@Sean

Thank you

Could you point me to a sample configuration that will work with Hotword and Assistant Mk2? I will also remove Notification Trigger.

[A Former User]

@ACRONN
https://github.com/eouia/MMM-Hotword/blob/master/documents/config.md#simple-configuration-example

[ACRONN]

I initially tried that but I will try it again as per your advice

[ACRONN]

@Sean

Hi Sean

Post a rebuild and using the original config.js it now works ie hotword now correctly calls assistant. The only issue left is when google presents me with options it doesn’t then listen for a follow up selection and throws back to hotword again. Is there a setting to enable assistant to follow up and finish the assistant sequence? Thx