@open_book Just looking at your pi’s IP. It looks like it’s using 192.168.0.X and you’re whitelisting the 192.168.1.X IPs. Can you try adding

"::ffff:192.168.0.1/120", "192.168.0.1/24"

to your whitelist and see if that fixes it up?

@open_book The ipWhitelist should have no affect on your SSH ability. This sounds like there is some problem with either your network or the pi itself. The ipWhitelist just affects what can connect to the MagicMirror software.

Can you give me your network setup and how you’re trying to access it through SSH? I’m guessing that you are trying to SSH in from inside your network and not from somewhere else.

I haven’t used the remote control module so I’m not to sure how it works with the whitelist. From how you’re describing it, it sounds like whatever the IP of the device you use the remote control with is what the MagicMirror needs whitelisted. If that’s the case, are you just trying to access your mirror from devices on your internal network or are you using a data plan with your mobile? If so, that IP probably changes frequently.

Those IPs you listed ("...1.1/120"), are those IPv6 or IPv4 IPs?

@caseyrcoughlin It might be possible, but how would someone select the up/down arrows, etc? Are you setting up a touch screen mirror?

@alberttwong That’s great! I don’t have a drop cam so I’m not really sure what information people would want to get from them.

I made a separate branch if you want to check it out. I’ll merge it after I run some more tests.
https://github.com/mochman/MMM-Nest/tree/protect

You are going to have to edit your Nest developer settings to allow read access to the “protect” in order for this to work. When you do that, you’ll need to run getToken.sh again to get a new token.

I gave you the option to use a visual representation, or a list representation. If you use visual, you have the choice to display your nest, protect, or both together.

Here are some of the ways it displays to you.

I can’t find the “Smoke is clearing” data or stuff like that, so it just shows if there is an alarm for smoke or carbon monoxide, or if your battery is low.

Please take a look and tell me what you think.

@pugsly Sure. What kind of info would you be looking for on it? From what I see on the API, we can read CO Alarm State, Smoke Alarm State, Battery Health, and some other things people probably don’t want to see.

What I’m thinking right now is putting a colored ring (like the one on the smoke detector) around the thermostat circle to indicate good, warning, or emergency status. Any ideas?

I updated the css using edits from @j-e-f-f. The nest display looks closer to what the actual nest thermostat looks like.

@j-e-f-f Your CSS changes look great! I added them back into my module with a few tweaks to get the heat&cool mode working again. If you just want to send me pull requests instead of making a new module with cosmetic changes, I’d me more than happy to merge them.

Please follow the steps outlined at the top of this page. Let me know what you’re seeing when you do those steps.

You might have to add some custom css to MagicMirror itself to get this to work the way you want it to. I’m not entirely sure how to do that, but I bet there are a bunch of posts in this forum with the answer.

Is the smartphone on your wifi? If it is, just follow the steps to add your whole subnet.

If you’re trying to access it while using the phone’s network, that’s going to be harder. You’re going to have to configure your router to allow port forwarding to your pi, then figure out what your phones IP is. Then you could be safe and only allow that IP. The problem with that is when your IP changes, you’ll have to edit your whitelist again. You could try to add the class C or D subnet if you don’t want to worry too much about this, but you’ll be opening up your network to the internet in the process so good luck!

@Mitch1138 You may be able to change the .center part of the css to change the font size. I’m not to sure though, I don’t know much about CSS. Sorry.

@lucallmon If you don’t care about the changes you made to those files then you can run
git stash from your MagicMirror directory. You should be able to run the git pull command after that.

If you want to keep them, I’d just copy those files to somewhere not in your MagicMirror directory, run the stash command, pull the new MM, and put them back if you think they aren’t going to break anything in 2.1.1

Okay I thought you were using alexaPi, looks like alexa-client. In that case, have you run

cd /home/pi/MagicMirror/alexa-client/
pip install -r requirements.txt
python setup.py install
sudo pip install -r auth_web_requirements.txt

already? If so, try

cd /home/pi/MagicMirror/alexa-client/
python auth_web.py

In this application you will need to add the token you get from the website to your settings.py file. After you get the token, run nano settings.py and paste the token where it says

REFRESH_TOKEN= ``

so it will say something like

REFRESH_TOKEN= `yourTokenGoesHere`

Are you physically connected or VNC’ed to the raspberryPi? If so, open up a terminal window and then type
sudo python /path/to/your/alexapi/folder/auth_web.py
then open up your browser (the one in the pi) and go to http://localhost:3000
log in with your Amazon login/pass. The script should update your settings.py file for you.

If you are using an ssh program to access the pi. Run the first command as normal, then open up a browser and go to http://your.pi.ip.addr:3000

The rest should be the same.

It looks like your raspberry pi started using IPv4 instead of IPv6. the ::ffff: before your ip shows that it’s trying to use a IPv6. That’s where "::ffff:10.0.0.1/120" was working. Seems like something changed though that it’s now using the IPv4 address.
So to cover all your bases, keep both "::ffff:10.0.0.1/120" and "10.0.0.1/24" in and you shouldn’t run into this problem again.

Have you tried adding "10.0.0.1/24" to the list since it looks like your client is using an IPv4 connection?

How did you set up your AlexaPi program? Did you use the default raspberrypi platform? If so, you may need to change it in your config file.

sudo nano /etc/opt/AlexaPi/config.yaml

Find the area called Platform: and change

platform:
  # Name of your platform, e.g. raspberrypi, orangepi, desktop
device: "raspberrypi"

to:

platform:
  # Name of your platform, e.g. raspberrypi, orangepi, desktop
device: "magicmirror"

You may also want to scroll down further on the config file and see if your magicmirror settings are correct.

Then don’t forget to restart the AlexaPi program.

Thanks.

I added a “last updated at: XXXX” to the modules and now they both have updated correctly the past few days. Guess it was gremlins.

@Jopyth 1 is MMM-forecast-io and the other is one I made. Other modules I’ve made still update correctly as well as other default modules.

If it becomes a pain to keep reloading the mirror, I’ll probably just wipe the drive and start over fresh.