Posts made by smackenzie5

smackenzie5

@shbatm
Need some help getting AlexaOnOff to work with Google Mini

I’m including the following folks in this post since, at some point in the forum, they have all asked how to get AlexaOnOff working with Google Home @eddgeywing @retroflex @selarp @felipemfa
If any of you have already gotten Google to work with AlexOnOff, please share.

@shbatm in previous posts you asked for the following info so here it is:

My mirror version is 2.7.1. My understanding is I don’t need to change line 21 in MMM-AlexaOnOff to match this number.
“FauxMo service started. Listening on 192.168.1.32:21900” is listed – see below.
Tested with example but got similar results as original – see below.
Even tried discovery from alexa.amazon.com but unable to register for account since I don’t have an echo – yes, I’m desperate…

Here is the code for my config.js – should be same as yours:

{
    			module: 'MMM-OnScreenMenu',
    			position: 'bottom_right',
		},
		{
    			module: 'MMM-AlexaOnOff',
    			config: {
        			devices: [{ 
              			name: "Magic Mirror",
              			on: { 
                			notification: "ONSCREENMENU_PROCESS_ACTION",
                			payload: { actionName:'monitorOn' }
              			},
              			off: { 
                			notification: "ONSCREENMENU_PROCESS_ACTION",
                			payload: { actionName:'monitorOff' }
              			},
        		}]
    			}
		},

Here is what I get when I start MagicMirror:

pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ sudo npm start

> magicmirror@2.7.1 start /home/pi/MagicMirror
> sh run-start.sh

Starting MagicMirror: v2.7.1
Loading config ...
Loading module helpers ...
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: currentweather.
No helper found for module: weatherforecast.
No helper found for module: MMM-google-route.
Initializing new module helper ...
Module helper loaded: MMM-OnScreenMenu
Initializing new module helper ...
Module helper loaded: MMM-AlexaOnOff
All module helpers loaded.
Starting server on port 8080 ... 
Server started ...
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: MMM-OnScreenMenu
Connecting socket for: MMM-AlexaOnOff
Module helper started for MMM-AlexaOnOff
Sockets connected & modules started ...
Launching application.
Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/xxx/basic.ics - Interval: 300000
21900
FauxMo service started. Listening on 192.168.1.32:21900

Here is the sudo netstat -tulpn:

pi@raspberrypi:~ $ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      3081/electron       
tcp        0      0 0.0.0.0:21900           0.0.0.0:*               LISTEN      3081/electron       
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           3081/electron       
udp        0      0 0.0.0.0:68              0.0.0.0:*                           307/dhcpcd          
udp        0      0 0.0.0.0:56022           0.0.0.0:*                           335/avahi-daemon: r 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1334/libpepflashpla 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1334/libpepflashpla 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           335/avahi-daemon: r 
udp6       0      0 :::55455                :::*                                335/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                335/avahi-daemon: r 
pi@raspberrypi:~ $

And starting the example:

pi@raspberrypi:~ $ cd ~/MagicMirror/modules/MMM-AlexaOnOff/node_modules/fauxmojs/example
pi@raspberrypi:~/MagicMirror/modules/MMM-AlexaOnOff/node_modules/fauxmojs/example $     node example.js
started..

And the sudo netstat -tulpn for the example:

pi@raspberrypi:~ $ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      3081/electron       
tcp        0      0 0.0.0.0:11000           0.0.0.0:*               LISTEN      3634/node           
tcp        0      0 0.0.0.0:11001           0.0.0.0:*               LISTEN      3634/node           
tcp        0      0 0.0.0.0:21900           0.0.0.0:*               LISTEN      3081/electron       
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           3634/node           
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           3081/electron       
udp        0      0 0.0.0.0:68              0.0.0.0:*                           307/dhcpcd          
udp        0      0 0.0.0.0:56022           0.0.0.0:*                           335/avahi-daemon: r 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1334/libpepflashpla 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1334/libpepflashpla 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           335/avahi-daemon: r 
udp6       0      0 :::55455                :::*                                335/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                335/avahi-daemon: r 
pi@raspberrypi:~ $

Switching gears –
I started looking at the Belkin website for how to connect Wemo to Google:
https://www.belkin.com/us/support-article?articlenum=224185

The article basically says that you have to setup your Wemo device before Google can find it. In order to setup your Wemo device, you have to select it from your wifi menu:
https://www.belkin.com/us/support-article?articlenum=110936

After running Mirror (and same with example), I tried setting up Wemo but I’m not able to see the faux Wemo switch or devices on my wifi.

Is the faux Wemo discoverable under wifi as the article directs?

Another option Belkin describes is entering the MAC address.
Is there a MAC address for the faux Wemo switch?

I know that’s a lot of stuff to go through but I’ve been working on this for a while.
I really want to get this working. Without it, my mirror is pretty much useless.
I’m going to use AlexaOnOff with OnScreenMenu to turn the monitor on and off only (BTW – OnScreenMenu works great, thanks).

Any help with AlexaOnOff would be appreciated.

Thanks,
Scott

smackenzie5

Anybody know how to move map labels (cities) so they aren’t covered up by the driving direction route line?
labelOrigin seems to be good for a single marker but doesn’t work with multiple city labels on the route.

Thanks

smackenzie5

I’m trying to get the google-route module to zoom in on the map it generates for the routes. Currently, the map returned for my directions is too big and the routes too small.

Based on my reading to date, it looks like you can control the zoom through mapOptions however, I haven’t had any luck and I’m out of ideas. Below is my config.js file that shows how I’ve written the zoom function. Ideas?

Thanks

		{
            		module: 'MMM-google-route',
            		position: 'bottom_bar',
                        header: 'Which Commute Sucks Less',
			config: {
                	key: 'key',
                	directionsRequest:{
                    		origin: '30.388259,-86.507500',
                    		destination: '30.482197,-86.503158'
                		},
			mapOptions:{
				zoom: 10
				}
            		}
        	},

smackenzie5

Thanks @broberg

Does the config.js file takes precedence over the css files?

I’ve tried deleting the calendar’s position line in the config.js file and the calendar module can’t be seen. I tried changing the calendar’s position to absolute in the config.js files and that prevented the mirror from loading at all. Basically, is there anything that needs to be done to the config.js file or should the custom.css file take precedence over everything?

smackenzie5

@broberg Is there an order of precedence between custom.css, calendar.css, and config.js?

I’ve added the position, left and top lines above to my custom.css and calendar.css.
(I put the lines in both just trying to get it to work)

When I start up MagicMirror, the calendar module is in the correct position when it says “Loading…” but once the calendar loads, the module changes position. To me, it looks like the module is at the “top_left” position below the clock which is what the config.js specifies.

Any thoughts on why the module is moving position after loading?

BTW – I added the lines to drop the margin completely to my custom.css and it worked great, no problems.

Thanks,
Scott

smackenzie5

Re: MMM-SORT - (Static Or Rotating Tides)

@Mykle1 First thanks for the module. Installed it yesterday and everything’s working great.
I did have a question regarding WorldTides API Keys and pricing - just want to make sure I’m understanding it correctly.

Their website says:
“When you register, you get one month of 100 free credits to make API calls.
After that, credits cost $1.99 per 1000 credits and subscriptions start at only $0.99/mo. Bulk pricing also available for as low as $0.10 per 1000 credits.”

To me that reads the first month is free then you have to pay to get the module data after that.
Is that your experience using the WorldTides API?

Thanks,
Scott

smackenzie5

Thanks @lavolp3 - worked well.