Currently on your system I see three sensor tamper conditions and two sensor offline malfunctions. These are not conditions you can fix remotely.
Sensor tampers on wireless sensors are due to the cover not being affixed properly/the sensor tamper switch not being closed. Remove and reattach the cover securely.
Please read the following thread for what can cause Offline conditions.
Additionally some specific sensors like 2GIG Smoke Detectors may throw offline conditions for specific circumstances unrelated to signaling, such as being beyond expiration date or having a dirty sensing element. This is usually accompanied by LED flashing and beeping from the device.
If the above link does not help resolve the offline issue, what model number are the offline smoke detectors? What is their replace-by date?
I believe all the issues have been resolved. The last one was the tamper switch. I reset it several times but it kept coming back. Finally, I switched 2 sensors and I have not had an issue since then. I think the smokes are back online unless I am mistaken
I added a Z-Wave outlet. I tried several times to turn it on by voice but I get the message "I found multiple matching lights. I renamed it a couple of times but get the same results. Currently, I named it Heavy. What am I doing wrong?
What are you voice feature are you using, Alexa or Google?
Does the device work outside of voice control (via Alarm.com or the panel) and was a Z-Wave Network Rediscovery run for all devices after installation?
I ask Google to talk to Alarm.com. That works for all the other devices. Yes, I can turn it on using the app/computer/panel and I ran rediscover and test network.
When you ask google to activate that switch, is it hearing you correctly?
You can check what it heard via the Google Home app. Youll want to check what google hears matches what is in ADC. I just updated the integration guide to include how to check that:
It’s not a Google issue as all I do is ask Google to talk to Alarm.com. Alarm.com then asks what I want to do. I tell it to turn on any one of my nodes and it does it, all except this one entry. It is simply called “Heavy” which does not sound anything like any other node. It has no special characters or plurals, it’s dead simple but doesn’t work.
It’s not a Google issue as all I do is ask Google to talk to Alarm.com. Alarm.com then asks what I want to do.
So to clarify, when you say “Ok Google, Ask Alarm.com to…” you are not speaking to the Alarm.com app. You are interacting with Google Home. Google Home has access to an ADC device list that you’ve shared with the integration and command API.
Voice control is 100% Google side. Did you check what the Home app heard to make sure there are no mistakes and that it matches?
Yes, I could do that, and I have, however, for the test I say “Hey Google talk to alarm .com” and stop. Alarm.com, in a different voice, then comes on and asks what I want. If I tell it to turn on the living room light it does, if I ask it to turn on “heavy” I get that error message. Even if you were right why would it work for one and not for the other?
Even if you were right why would it work for one and not for the other?
It might not work for one, but for the other, because those are two different names, and Google might be mishearing or spelling one differently than you anticipate. If Google’s and ADC’s spelling does not match, you’ll just need to adjust the ADC device name to match what Google is hearing.
Google is not putting Alarm.com on the phone, your Google Home is processing your speech and determining what is said. That is then being matched up to your ADC device list via the integration.
The above steps are recommendations straight from the ADC integration instructions.
They are the most likely cause of what you are seeing. Can you please provide a screenshot or confirmation of what Google hears when you give the command for the one that doesn’t work currently?
I have used extremely simple labels, Living, Fan, Bedroom, etc. Also, there are 2 ways to command Google. One is “Hey Google, ask alarm.com to turn on bedroom” after which the alarm.com voice comes on and says “Sure, turning on the bedroom, is there anything else I can do for you?”
Or you can say “Hey Google talk to alarm.com” after which the alarm.com voice comes on and says “How can I help you.”
The words do not show up on a screen so there is no screenshot to send.
Is there a way to disconnect Alarm.com from Google and then reconnect?
To confirm, when you ask Google to turn on Heavy, and it gives you the error message “found multiple matching lights.” you are unable to confirm what google hears through the google home app as described here?
One is “Hey Google, ask alarm.com to turn on bedroom” after which the alarm.com voice comes on and says “Sure, turning on the bedroom, is there anything else I can do for you?”
Or you can say “Hey Google talk to alarm.com” after which the alarm.com voice comes on and says “How can I help you.”
Do both of these command types fail with the same error message when asking to turn on heavy?
Yes, but how do I get it to work the way it’s supposed to?
You can try removing the Z-Wave device from panel programming, then re-adding and running a Z-Wave network rediscovery. Afterwards test the Google Home interaction again for resolution.
Over the weekend I removed all devices, reset the panel, and added them in one at a time doing a “rediscover” after each addition. After the last one, I got a positive response to the final rediscover, no faulty nodes.
This time I named that node “Fan” not heavy. The results are the same. If I interface with Google either way and say “turn on the bedroom” the light comes on. If I say “turn on the fan” it says “I found multiple matching lights.”
If I say “turn on the fan” it says “I found multiple matching lights.”
What is the make/model of the Z-Wave device in use?
Do you have other devices of this exact same make/model working with Google?
Over the weekend I removed all devices, reset the panel, and added them in one at a time doing a “rediscover” after each addition
In the future to save time, you can just run one rediscovery, after all devices have been cleared/added and placed in their installation locations. In general, rediscovery should be done at the end whenever you add/remove a new device(s).
Yeah, I was getting a node failure and could not isolate it so that’s why I added them one by one like that.
The device is a Zooz-z-wave-plus-power-switch-zen15 and it is the only one like it. It is a heavy-duty switch for my window AC.
Removing the Alam.com link from Google Home and re-adding it may resolve the issue but the Zooz-z-wave-plus-power-switch-zen15 is not listed as a compatible device from either Alarm.com or Qolsys which may be the root of the issue.
Current compatible device lists can be found below: