@sean thanks! So it is a feature! I can see what we could do with it, and now that I know where to look, I’ll put it to good use. I’ll dive into the currentweather code and try to find out why it behaves different.
Read the statement by Michael Teeuw here.
Posts made by jck
-
RE: All modules auto hide, except currentweather
-
All modules auto hide, except currentweather
This may be a feature but I can’t find any info on it.
I’m still preparing my MM, so my Pi 3B+ is hooked onto a spare monitor and sitting on my desk. All works well, but after some time, all modules disappear from view, except the (default) currentweather. I configured a hotword for Google Assistent, and activating this all modules come back to view.
Also when my webcam recognizes my face, the default Calendar module comes up (exactly as I intended it). But the other modules stay hidden.
The thing is: WHY do all modules hide, except one? As far as I can tell there is little reason for the default clock not to behave in exactly the same way, but it doesn’t. The other thing is: the hotword should only triggers Google assistant, so I don’t understand why it wakes all the other modules while the face recognition only triggers the calendar. What is happening and how do I control it?
My settup:
MMM-AssistantMk2
MMM-Facial-Recognition-OCV3
MMM-Hotword
MMM-Hue-Lights -
RE: MMM-Assistant: Register your Mirror as Google Assistant related device invalid JSON
@Sean
I found the problem! As always, it was very simple as soon as you see it. The error did precisely report the problem but I was to blind to spot it! It said it expected a value, and it could’t read the one I provided.
I used the wrong kind of " to make the input seen as STRING. If I had used the sample you provided in the module, all would have been good, but I copied the example on the github… and that one uses the slanted version of ".
My mirror now shows up on the Google Home app! Thanks for all the hard work!
-
RE: MMM-Assistant: Register your Mirror as Google Assistant related device invalid JSON
@sean yes, I did.
Just to be sure I just did the whole thing over again, trying to make sure I didn’t miss a step. But got the same results. As far as I can tell, it sends out the JSON alright, together with the right ACCESSTOKEN. But it seems to misread the value given at the id line.
-
RE: MMM-Assistant: Register your Mirror as Google Assistant related device invalid JSON
Hi, thanks for replying!
Here’s the file:
{ "id": “my_mirror_001”, "model_id": “mirror-5a142-magicmirror-nz3frj”, "nickname": “Magic Mirror”, "client_type": "SDK_SERVICE" }
-
MMM-Assistant: Register your Mirror as Google Assistant related device invalid JSON
Hi,
I tried to get my Mirror to show in the Google Home app and followed the instructions here: https://github.com/eouia/MMM-AssistantMk2/blob/master/USAGE.md
After i ran the command:
curl -s -X POST -H "Content-Type: application/json" \ -H "Authorization: Bearer $ACCESSTOKEN" -d @deviceInstance.json \ https://embeddedassistant.googleapis.com/v1alpha2/projects/YOUR_PROJECT_ID/devices/
(replacing the YOUR_PROJECT_ID with my project ID) I got an error:
{ "error": { "code": 400, "message": "Invalid JSON payload received. Expected a value.\n“magicmirror”, \n^", "status": "INVALID_ARGUMENT" } }
My best guess is that I didn’t use the correct value for my model_id or project_id but I tried different values and still run into dead ends.
Any pointers?