Misunderstood command

[jukerjim]

Just added a smart plug and named it "Manley". When I ask Google to turn it on (or off) it responds with --- "sure, turning on/off three lights".

Regardless of how many times I repeat the command I get the same incorrect response. (got it to turn on the device just once)

Manley doesn't sound anything like lights, so what's going on?

[Musicmonkey5555]

What is the exactly words you are saying? You often have to say the type of device. I will try changing the name of one of mine to the same thing and try to see if I can reproduce. For insurance we have one marked as a fan and have to say "turn on Rosalee fan". Also does it have issues with other commands? Other thing you can try us retrain it with your voice

[jukerjim]

After wake phrase "turn on/off manley"

[Cathal_S]

Hi jukerjim,

Adding to the suggestions from @Musicmonkey5555 please also check that you have the correct device type set.

• From the Google Home app long press on the device icon.
• Select the settings cog ⚙️ icon top right.
• Select 'device type' and check that you have it set as an outlet instead of a light.

[jukerjim]

Sadly it is properly identified as an outlet.

[Cathal_S]

Hi again,

I'm also getting some strange actions when using the command "Hey Google turn off Manley"? Strange?

Is it possible for you to try using a different name for the outlet and see if you still have this issue? I will ask other product experts to see if this is something they can replicate.

[jukerjim]

Hello again to you Cathal.

The device is a vintage Manley popcorn machine so that is the only logical name for the outlet.

I will try renaming it to "themanley" and see what happens.

[Cathal_S]

Yes I understand that you would like to keep the naming of the device. My suggestion is so we can narrow down if the issue is being directly linked to the name 'Manley'.

Could you possibly try the name 'Popcorn' and see if it functions correctly?

[jukerjim]

Update. After renaming to "themanley" the results are:

me: "turn on themanley"  Google "Sure, turning on Manley"

me: "turn off themanley"  Google: Sure, turning off three lights

repeated several times and the results are consistent.

there are two popcorn machines on outlets; the name of one machine is "u pop it" Its' device name currently WAS "popcorn machine". When I added the Manley I changed the name of the original to "upopit" and it works great. I then added manley and.....you noticed the results.

Now it got even more interesting! I renamed the Manley machine to "Manley popcorn" with the following result:

me: "turn on manley popcorn"   Google "sure, turning on Manley popcorn"

me: "turn off manley popcorn"  Google "to turn off your speaker, unplug it from the power source. To tell me to turn off other devices, include the name of the device in your request"

[Cathal_S]

So it's definitely the word Manley that is causing this issue.

Please repeat the command and immediately afterwards submit feedback from the Google Home app as described in the link below and check ✔️ the box to include log files, I will do the same.
Feedback:
https://support.google.com/googlenest/answer/7071494

I will also flag this thread for the attention of a community specialist.

[jukerjim]

Latest update:

My latest workaround was to rename the device to "manleypopper" and that works fine so far. Should I revert back to the original name in order to submit the issue, or will your feedback be sufficient?

By the way, I tried "manly" instead of "manlEy and amazingly I was able to make it go on and off properly for three cycles, but from the fourth on, it would accept the turn on command, but insisted on turning OFF three lights. Just WEIRD.

Jim

[Cathal_S]

Yes this is a strange quirk?

When I use the command "Hey Google, turn Manley off" the assistant will either turn off all 4 lights in the same room or turn off all devices I have in that room?

Yes please leave feedback from the Google Home app, you don't need to change the name back just use the same command that causes the issues before submitting the feedback.

[jukerjim]

First off, thanks for your patience with this issue. Leave it to me to uncover strange issues. I have a reputation for that!

Just for grins, another other odd problem I ran into earlier:

I have a Wurlitzer 1015 jukebox on a switch named "1015".

When I asked google to turn on the ten fifteen, it complained about a timer not available or something.

When I asked Google to turn on the "one zero one five" Google responded with "sure, turning on the ten fifteen".

That seems to have resolved it self and now it accepts a "ten fiftee" command.

This technology is just astonishing and I suppose these goofy issues are part of growing up.

Jim

[Cathal_S]

Haha, you definitely found a strange problem here. Maybe you could use a routine with a custom 'Try your own action' command for your situation as a workaround?

See screenshot below...

I just tested this with one of my lights instead of the Manleypopper command and it seemed to work ok.

[jukerjim]

This is getting ridiculous. My latest rename "Manleypopper" worked for an hour or so, but  now it no loner works.

The "turn on manleypopper works BUT

turn off manleypopper gets "sorry, I don't understand.

[Cathal_S]

Is it possible for you to change the device name to something without the name 'Manley' included and then make two different routines for on/off either like the one in my screenshot above or using the 'Adjust home devices' action.

Hopefully this will allow to say "Hey Google, Manley On or Off" but have the routine turn on/off the device without the name'Manley'.

 

[jukerjim]

Patient and smart you are!

A pair of routines asking Google to operate the device - now named - "Popcorn" works at least for now. A couple of days testing should verify success.

Since the device is now controlled with routines, there is no verbal feedback. Is there any way to get a verbal acknowledgment when a routine is/was started?

And again my sincere for your help. Perhaps the folks at Google will figure out a way to keep the word "Manley" from driving it nutzoid.

[Cathal_S]

Hopefully Google takes action on our feedback and addresses this soon, but In the meantime you can also add any announcement to your routines by using the 'Say something' option within the communicate and announce section....

Edit: Add another action to your routines and use this option 👍

[Musicmonkey5555]

I would try the routine to do something else even just say something back and see if it works. I've seen many cheaper wifi plugs have issues depending on how they integrate. Especially where they will work for a while and then stop, sometimes even clicking the button on them it unplugging then for a bit and then back in reset then. Or try a different plug that has been working for a while, but change the name to again narrow down the plug vs words. I've definitely seen issues with numbers, but you gotta figure all the different built in words to work quickly could interfere easily with a custom one you add. You just have to come up with something that works and you can remember. You could even do room name and popcorn if they are different rooms to see if it works.

[jukerjim]

Thanks for the response.

I've had my share of disappearing and sometimes reappearing sockets and even one that simply went belly-up. Unfortunately, substituting sockets accomplished nothing.

The word "Manley" simply gives Google the vapors!

I'm going with Cathal_S' workaround until (hopefully) Google solves the problem.

Jim

[Jake]

Hey all,

Sorry for the late reply. I wanted to check in and see if you had any other questions from here? Please let me know, as I would be happy to take a closer look.

Thanks so much Cathal_S for the helpful replies.

Best regards,

Jake

[Muddi]

Hey folks,

It's us again - how is it going with your devices? Do you still need help?

Cheers,

Muddi

[Jake]

Hey all,

I want to ensure you are good to go, and everything is working properly. Please let me know if you are still having trouble, as I will be locking the thread in 24 hours due to inactivity. 

Best regards,
Jake

[Jake]

Hey all,

It has been a few days since the last reply, and I am going to lock the thread at this time. If you have any questions, please feel free to create a new post. 

Best regards,
Jake