@cowboysdude I reached out to the developer on the GitHub repo by creating an issue there, with no response for quite some time.
Unfortunately, I do not know how to identify the css selector(s) you mentioned, nor how to verify if the modules are using the same ones or not. I am teaching myself programming bit by bit and it is a very slow and painful process.
I figured out the issue…idiot error (me). I typed the config option as “apiKey” instead of “apikey” and it wouldn’t read it as registered. So sorry for taking your time. Works now.
I went through the entire process of obtaining new Google Credentials and now it works. Must have been blip when I did the authentication yesterday. Sorry for troubling you.
I went through the entire process of obtaining new Google Credentials and now it works. Must have been blip when I did the authentication yesterday. Sorry for troubling you.
Thanks for the rapid reply. Oddly enough, I just went through enabling said API on Google’s Cloud Console and authentication as well as paying a $5 fee for access to Google Device Acccess API yesterday and nothing was mentioned about the API going away. It even had me give permissions to view my Nest Thermostat on the permissions screen.
Moron here, installed mmm-nest-status according to instructions. Got all the secret stuff off google and meticulously entered it in my config.js file. I used all default settings, meaning the config was copied from the github page and nothing changed other than google credentials. Rechecked all commas and formatting stuff. When I start up my MagicMirror, mmm-nest-status module displays:
“Nest API Timeout Error: Request failed with status code 404.
This module will try to load data again in 5 minutes.”
I can’t figure out how to take screenshots. I don’t know how to get debug files to copy and paste here. I am, as I mentioned, a moron.
Thanks for any help.
Config.js like this:
module: "mmm-nest-status",
position: "lower_third", // pick whichever position you want
config: {
clientId: "<YOUR_DEVICE_ACCESS_CLIENT_ID>",
clientSecret: "<YOUR_DEVICE_ACCESS_CLIENT_SECRET>",
refreshToken: "<YOUR_DEVICE_ACCESS_REFRESH_TOKEN>",
projectId: "<YOUR_DEVICE_ACCESS_PROJECT_ID>",
displayType: "grid",
displayMode: "all",
thermostatsToShow: "all",
// ... and whatever else configuration options you want to use
}
},
There is never enough time in a day!!!
I wish I had the skill to do it myself. I am struggling to figure out enough coding just to set up my config.js file.
If anyone would be willing to take a gander at the issue I posted on the developer’s GitHub page:
I haven’t had a response from Jopyth in over 9 days, perhaps a guru here is willing to provide feedback and/or a suggestion if this is even possible.
I figured out the issue…idiot error (me). I typed the config option as “apiKey” instead of “apikey” and it wouldn’t read it as registered. So sorry for taking your time. Works now.
@cowboysdude I reached out to the developer on the GitHub repo by creating an issue there, with no response for quite some time.
Unfortunately, I do not know how to identify the css selector(s) you mentioned, nor how to verify if the modules are using the same ones or not. I am teaching myself programming bit by bit and it is a very slow and painful process.
Link to issue posted on MMM-GoogleTasks GitHub Repo, with further explanation below.
Bug Description:
System Info:
Screenshot
Module Configuration:
{
module: 'MMM-pages',
config: {
modules:
[['MMM-GoogleTasks', 'MMM-Gas', 'MMM-AlarmClock', 'MMM-NOAA3'],
['MMM-SimpleLogo', 'MMM-CalendarExt']],
excludes: ['alert', 'updatenotification', 'clock', 'MMM-Remote-Control'],
animationTime: 0,
rotationTime: 5000,
delayTime: 0,
},
},
{
module: 'MMM-ModuleScheduler',
config: {
notification_schedule: [
//TURN SCREEN ON AT 05:00 AM EVERY DAY
{notification: 'REMOTE_ACTION', schedule: '30 5 * * *', payload: {action: 'MONITORON'}},
//TURN SCREEN OFF AT 01:00 AM EVERY DAY
{notification: 'REMOTE_ACTION', schedule: '00 1 * * *', payload: {action: 'MONITOROFF'}},
//RESTART THE RASPBERRY PI DAILY AT 02:00 AM
{notification: 'REMOTE_ACTION', schedule: '00 2 * * *', payload: {action: 'REBOOT'}},
],
schedulerClass: 'scheduler',
animationSpeed: 0,
global_schedule: {
from: '00 0 * * *',
to: '01 0 * * *',
groupClass: 'hide_module',
},
},
},
{
module: 'MMM-AlarmClock',
position: 'top_center',
classes: 'hide_module',
config: {
alarms: [
{
time: '09:27', //must be 24 hr format
days: [1,2,3,4,5], //Sunday=0, Saturday=7
title: 'KBRX - Party Line',
message: 'Party Line',
sound: 'http://162.244.81.209:8032/stream?autoplay=1',
volume: 1.0,
touch: false,
format: 'ddd, h:mm A',
timer: 1.15 * 60 * 60000, //change first operand to specify hours
fade: false,
fadeTimer: 60 * 1000, //change 1st operand to specify seconds, how long fade into alarm before volume is set
fadeStep: 0.005, //0.5%, inc volume this percent amount each second until fadeTimer is reached
popup: false,
},
],
},
},
Console Errors:
The following are the ONLY errors that showed in the console, and I discovered by process of elimination that the moment-timezone errors are caused by the MagicMirror default “clock” module.
moment-timezone-with-data.js:472 Moment Timezone has no data for none. See http://momentjs.com/timezone/docs/#/data-loading/.logError @ moment-timezone-with-data.js:472
TypeError: Cannot convert undefined or null to object
at Function.keys ()
at Class.getDom (MMM-GoogleTasks.js:87)
at main.js:110
at new Promise ()
at updateDom (main.js:109)
at main.js:53
at Array.forEach ()
at createDomObjects (main.js:24)
at Object.modulesStarted (main.js:471)
at startModules (loader.js:59)
Helpful Hints:
Then, by another module elimination process, I discovered that disabling/deleting MMM-GoogleTasks from the config.js file makes MMM-pages, MMM-Carousel, and MMM-ModuleScheduler run as expected.
This is bugging me, since really look forward to using MMM-GoogleTasks on my Mirror, and I must be able to switch out pages of modules since I am using it for an advanced personal assistant and family organization center.
Please help.