Read the statement by Michael Teeuw here.
[MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io)
-
@richland007 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):
How do i read more log lines not only tailing the last 15 from pm2 logs mm ??
They should be in ~/.pm2/logs by default. You can also stop the pm2 version and run the mirror manually using the instructions above.
I’ll let you know if I can replecate the CPU issue, but that’s very strange. I haven’t seen that.
Make sure you update to the latest version of the module to see the correct line, but other than that I don’t know why its not working for more than one device. At this point it sounds like a fauxmojs issue… You can always open an issue on their GitHub repo.
-
@djsunrise19 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):
Thanks. I’m using an echo dot 3rd generation. Sadly, I have to wait. There seems to be no problems with your module / the mirror / network.
I’d suggest posting a comment on the fauxmojs issue–maybe it will prompt them that more people are waiting for a fix. It looks like the python version has been fixed, so I’m sure it’s just a matter of them getting around to it.
-
@richland007 – So I just noticed something interesting: I tried adding multiple devices, and running “Discover my devices” from my echo. Alexa said she didn’t find any new devices, but when I looked in the device list on alexa.amazon.com, she had already found the other devices. Maybe try deleting all of the Wemo devices on your Alexa app and then retrying discovery?
-
@shbatm i will try it again but i think i did it once or twice deleting all my devices and had her discover them back up to no avail
D -
@shbatm I was wondering, however i am sure that i am wrong and just wishful thinking, but maybe changing the minimum version of MM for MMM-AlexaOnOff to 2.4.1 (which is the version i am at) only works for one instance, meaning initiating one device and not for all of them???
D -
@richland007 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):
wishful thinking
-
@richland007 Solution: Why not just update your mirror to 2.6.0? On my 2.6.0 mirror this add-on is working great, Alexa is finding all it’s 15 devices in one run.
-
Does anyone have instructions on how to connect this to Google Home? I’ve been searching for days with no luck.
-
@MoreLinux hi, have a MAC and the module is not working and I don’t know why?
-
I have latest Magic Mirror version with Alexa Dot 3rd gen. I am unable to discover device after installation. Anyone experience this issue and solve it? Running
netstat -tulpn | grep electronI get LISTENing on port 21900. When I ask Alexa to discover devices, I get nothing. Both Alexa & Rasp Pi are connected to the same wifi. Only thing in my logs when running Magic Mirror is/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines: 0|MagicMir | ATTENTION: default value of option force_s3tc_enable overridden by environment.Any help is appreciated
-
@Stoffbeuteluwe I also don’t know why it’s not working for you. I haven’t written the module, just installed and it worked.
I have an Amazon Echo Dot 2. generation.
-
@MoreLinux on Mac??
-
@sbrundage85 you can try echo dot 2 …I think the 3.generation is not working.
-
@Stoffbeuteluwe Any word on the possibility of getting things working with the Echo Dot 3rd gen? Any references of things to try? Any help is appreciated, really want to get my mirror up and running and this is a huge module I want to implement
-
@MoreLinux can you post your config. of MMM-AlexaOnOff Module so i can try?
-
for me not working on MAC…
Patricks-Mini:MMM-AlexaOnOff patrickhahn$ npm install npm WARN deprecated hapi@16.7.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated boom@4.3.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated ammo@2.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated boom@5.2.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated accept@2.1.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated call@4.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated catbox@7.1.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated catbox-memory@2.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated cryptiles@3.1.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated heavy@4.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated items@2.1.2: This module has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version of hapi to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated iron@4.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated mimos@3.0.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated joi@11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated podium@1.3.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated somever@1.0.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated statehood@5.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated shot@3.4.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated joi@12.0.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated subtext@5.0.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated joi@10.6.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated bourne@1.1.2: This module has moved and is now available at @hapi/bourne. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues. npm WARN deprecated content@3.0.7: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated pez@2.1.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated wreck@12.5.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated nigel@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated b64@3.0.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated vise@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm notice created a lockfile as package-lock.json. You should commit this file. added 59 packages from 21 contributors and audited 137 packages in 5.801s found 0 vulnerabilities Patricks-Mini:MMM-AlexaOnOff patrickhahn$ -
@sbrundage85 Hello, with my Mirror (2.8.0) an EchoDot 3rd Gen. I’m unable to discover devices, too. I try everything i know, but no solution. You found some solution?
Greets Niggich
-
@Niggich no 😢
-
@shbatm Can you help us?
-
I am running MM version 2.7.1 with the latest MMM-AlexaOnOff module. Below is my config.js details for this module. I get no errors when restarting MM and had no problem with Alexa discovering the devices listed in the module. I get confirmation feedback from Alexa when saying “Turn Magic Mirror Off”, but nothing happens. This used to work on an older build of MM but I wanted to start from scratch with the latest version and this has been the only Mod not working correctly. Any help is appreciated. Thank you.
{ module: 'MMM-AlexaOnOff', // classes: 'default everyone', config: { devices: [{ name: "Magic Mirror", on: { notification: "REMOTE_ACTION", payload: { action:'MONITORON' } }, off: { notification: "REMOTE_ACTION", payload: { action:'MONITOROFF' } }, }, { name: "Magic Mirror Modules", on: { notification: "REMOTE_ACTION", payload: { action:'SHOWALL' } }, off: { notification: "REMOTE_ACTION", payload: { action:'HIDEALL' } }, }, { name: "Magic Mirror Maps", on: { notification: "REMOTE_ACTION", payload: {action: "SHOW", module: "module_8_MMM-GoogleMapsTraffic"} }, off: { notification: "REMOTE_ACTION", payload: {action: "HIDE", module: "module_8_MMM-GoogleMapsTraffic"} }, }, { name: "Magic Mirror Reboot", on: { notification: "REMOTE_ACTION", payload: { action:'REBOOT' } }, off: { notification: "REMOTE_ACTION", payload: { action:'SHUTDOWN' } }, }, { name: "Magic Mirror Update", on: { notification: "REMOTE_ACTION", payload: { action:'UPDATE' } }, off: { notification: "REMOTE_ACTION", payload: { action:'RESTART' } }, }] } },
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login