Frustrated new HE owner

🎬 Get Started
1

I can say one thing HE is NOT for the average user! Here's my present setup:

by room

Den
light1---innr---zigbee
light2---innr---zigbee
light3---innr---zigbee
contact sensor---gocontrol---zwave
repeater-plug---3rd reality---zigbee

Deck
backlight---osram---zigbee
hottub---innr---zigbee

kitchen
repeater-plug---sylvania---zigbee
backdoor sensor---gocontrol---zwave

living room
frontdoor sensor---gocontrol---zwave
repeater-plug---3rd realityz---zigbee
lr1 light---innr---zigbee

bedroom1
light4---sengled---zigbee--not on mesh

bedroom2
repeater-plug---sylvania---zigbee

master
repeater-plug---3rd reality---zigbee
br1light---innr---zigbee
br2light--innr---zigbee

Probably one of the smallest systems. I use it mainly to interface to Alexa to turn stuff on and off by voice and some small automations. I moved from ST to HE for the speed and convenience of everything except alexa being local. BUT being an old guy and not the brightest bulb in the house am finding that even the small things I did with ST do not work.
example:
using basic rules, created the following:
if backdoor sensor opens, turn on the backlight and the hot tub.
BUT noooooooo for some reason HE is not seeing the sensor open even though it changes from inactive to active on device screen when the door opens

thanks to another user I did manage to get my tapt switch working as a NUE zigbee switch (Just on/off) Porch lite on at sunset and off at sunrise. Will find out tonite if that works.

I pretty much rebuilt my system from the ground up.
installed and registered HE
Added 5 zigbee repeaters and let them settle overnite
added 8 zigbee bulbs and let them settle
checked every device to be sure that it would turn on/off using the device screen
interfaced to alexa on HE and Alexa
started doing automation with basic rules.

Have i missed something this is supposed to fun....

2

As nearly as I can tell, you have three z-wave LSS/FLiRS devices with no z-wave repeaters. So this automation relies on these sensors robustly communicating with the hub directly. That may not be as reliable as one would hope.

Since the vast majority of your devices are zigbee, and most of them should repeat, why not replace the three z-wave contact sensors with inexpensive zigbee equivalents from Sengled, Linkind, or Third Reality?

4 Likes
3

Having three battery operated Z-Wave devices and no mains-powered Z-Wave repeaters may not be the best approach on HE. My experience w/the HE C7 is that it is more "needy" in terms of Z-Wave than my ST hub was.

Given your Zigbee-centric situation, I agree that switching out those GoControls for a few inexpensive Zigbee contact sensors could be a good approach. Third reality sensors use two AA (or AAA?) batteries, should have long life and are inexpensive.

Can you post a screen shot of your Basic Rule that isn't working?

And when you say:

You mean the contact sensor changes from closed to open, right?

2 Likes
4

When Backdoor Sensor opens ...
Turn on Backlite, Hot Tub

It probably can not get any simpler.

1 Like
5

If the contact sensor device page is consistently showing Open/Close when you open and close the door (and you seemed to say so above) then the next likely issue is the automation has some issue with it. That's why I asked for a screen shot of the automation. "Typos" in automations can occur (ask me how I know.) :wink:

You can also turn on debug logging for the device (on the device page) and enable logging for the Basic Rule on the rule page, open a tab in your browser to the Logs page, clear the logs and then open the door, and post a screen shot of what appears in your logs.

image
image

1 Like
6

would a tuya zigbee sensor work with HE

7

Can you post your z-wave details page? I just want to see it beyond knowing you only have 3 devices.

8

I believe so...if the generic zigbee contact sensor didn't work, we have a community developer who has created a bunch of drivers for Tuya devices. Sounds like @jim273 got it working after talking with them.

Can also ask @kkossev and @tomas1 from that thread to be sure.

2 Likes
9

Most of the Tuya Zigbee contact sensors should work with the Hubitat inbuilt 'Generic Zigbee Contact Sensor (no temp)' driver. There are exceptions from this as there are countless number of Tuya platform manufacturers, but we need to know the exact Model and Manufacturer values of the particular device. These can be found on the device web page 'Data' section,\

2 Likes
10

While you're at it a screenshot of your ZigBee routing would help.

http://your.hub.ip.here/hub/zigbee/getChildAndRouteInfo

With W10:
To select image: Windows Key + Shift + S
To paste into message: Control + V

1 Like
11

No idea what this means but?

Here's what came back:

Parent child parameters
EzspGetParentChildParametersResponse [childCount=0, parentEui64=0000000000000000, parentNodeId=65535]

Child Data

Neighbor Table Entry
[Chesters light, 091A], LQI:255, age:4, inCost:1, outCost:1
[Couch, 44BD], LQI:255, age:5, inCost:1, outCost:1
[nancys light, 52A2], LQI:254, age:3, inCost:1, outCost:1
[Backlite, 5E84], LQI:252, age:4, inCost:3, outCost:7
[LR1, 7A1C], LQI:255, age:4, inCost:1, outCost:1
[Den repeater, 8FF9], LQI:255, age:4, inCost:1, outCost:3
[LRrepeaterplug, BF49], LQI:236, age:3, inCost:5, outCost:0
[Bedroom2 Repeater, C517], LQI:253, age:4, inCost:3, outCost:1
[Kitchen repeater, CA08], LQI:234, age:4, inCost:5, outCost:3
[BR1, FCCB], LQI:251, age:4, inCost:3, outCost:7

Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [LR1, 7A1C] via [LR1, 7A1C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [null, CFB4] via [null, FA50]
status:Active, age:64, routeRecordState:0, concentratorType:None, [BR2, A13B] via [Bedroom2 Repeater, C517]
status:Active, age:64, routeRecordState:0, concentratorType:None, [BR1, FCCB] via [Bedroom2 Repeater, C517]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Hot Tub, 8602] via [Chesters light, 091A]
status:Active, age:64, routeRecordState:0, concentratorType:None, [LRrepeaterplug, BF49] via [null, FA50]
status:Active, age:64, routeRecordState:0, concentratorType:None, [null, 5B1B] via [null, 5B1B]
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Backlite, 5E84] via [Chesters light, 091A]
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused

12

I can make no sense of this log. I opened and closed the door 4 times (i think)

2022-10-09 14:23:29.522debugparse:zw device: 0A, command: 7105, payload: 07 00 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:23:29.513debugskip:BasicSet(value:0)

dev:112022-10-09 14:23:29.509debugparse:zw device: 0A, command: 2001, payload: 00 , isMulticast: false

dev:112022-10-09 14:23:21.524debugparse:zw device: 0A, command: 7105, payload: 07 FF 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:23:21.514debugskip:BasicSet(value:255)

dev:112022-10-09 14:23:21.511debugparse:zw device: 0A, command: 2001, payload: FF , isMulticast: false

dev:252022-10-09 14:23:05.306infomailbox: motion is active

dev:112022-10-09 14:22:51.893debugparse:zw device: 0A, command: 7105, payload: 07 00 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:51.880debugskip:BasicSet(value:0)

dev:112022-10-09 14:22:51.877debugparse:zw device: 0A, command: 2001, payload: 00 , isMulticast: false

dev:112022-10-09 14:22:47.595debugparse:zw device: 0A, command: 7105, payload: 07 FF 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:47.586debugskip:BasicSet(value:255)

dev:112022-10-09 14:22:47.583debugparse:zw device: 0A, command: 2001, payload: FF , isMulticast: false

dev:112022-10-09 14:22:41.878debugparse:zw device: 0A, command: 7105, payload: 07 00 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:41.865debugskip:BasicSet(value:0)

dev:112022-10-09 14:22:41.863debugparse:zw device: 0A, command: 2001, payload: 00 , isMulticast: false

dev:112022-10-09 14:22:36.155debugparse:zw device: 0A, command: 7105, payload: 07 FF 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:36.144debugskip:BasicSet(value:255)

dev:112022-10-09 14:22:36.141debugparse:zw device: 0A, command: 2001, payload: FF , isMulticast: false

dev:112022-10-09 14:22:29.581debugparse:zw device: 0A, command: 7105, payload: 07 00 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:29.571debugskip:BasicSet(value:0)

dev:112022-10-09 14:22:29.567debugparse:zw device: 0A, command: 2001, payload: 00 , isMulticast: false

dev:112022-10-09 14:22:23.031debugskip:BasicSet(value:255)

dev:112022-10-09 14:22:23.006debugparse:zw device: 0A, command: 7105, payload: 07 FF 00 FF 07 02 00 00 , isMulticast: false

dev:112022-10-09 14:22:23.002debugparse:zw device: 0A, command: 2001, payload: FF , isMulticast: false

dev:112022-10-09 14:17:31.275warndescription logging is: true

dev:112022-10-09 14:17:31.274warndebug logging is: true

13

the mailbox entry is for a motion detector that appears to be working

14

Agreed. :wink:

Text

Please post as screen captures.

i.e. Logs

image
image1262×526 91.8 KB

http://docs2.hubitat.com/en/user-interface/advanced-features/logs

3 Likes
15

Well I agree, but to be fair it's not purporting to be so (at this stage in its evolution). That's why I started with SmartThings until I familiarised myself with what smart home was all about. :smiley:

16

If the sensor changes the state, then the hub is seeing the sensor, for a simple use case such as that, it should be rock solid, 100% reliable, at least that is the experience of most users. Are the bulbs not turning on/off from the Device Details page, as expected? Do you have any restrictions in the app that might prevent the app from executing? Might want to turn the logging on, for the app to see where it breaks.

2 Likes
17

Go to the Device page for the door w/the contact sensor that controls kicks off you automation. Go to the Device tab, then choose the device.

Device tab will look like this:

2022-10-09 12_39_08-Chrome Main
2022-10-09 12_39_08-Chrome Main969×738 71.1 KB

Click on the contact sensor in your device list that is supposed to turn on the automation when the door it's attached to opens: Below is an example from my hub of a contact sensor device page:

2022-10-09 12_39_55-Chrome Main
2022-10-09 12_39_55-Chrome Main1369×488 25.8 KB

Scroll down on that page until you get to the Device Information section:

image
image1175×598 36.9 KB

Tell us what it says in the "Type*" dropdown. It should say something like mine, and include the words "contact sensor." What does yours say?

2 Likes
18

Again, please post your z-wave details page in it's entirety so we can help you. Include all columns and rows. Then post your zigbee routing table by going to http://your.hub.ip.here/hub/zigbee/getChildAndRouteInfo

1 Like
19

I will agree with this, but i will say that learning curve seems to level out pretty quickly, and this community is a big help in that regard. I also came from ST. In a fairly short amount of time I found i was doing far more with hubutat than I ever dreamed of doing on ST.

3 Likes
20

Your zigbee routing table looks good. Two repeaters are not as good as the others (Backlite, and BR1). But that's okay; the zigbee mesh should be fine.

The logs indicate that you did open (payload: FF) and close (payload: 00) the door 4 times in rapid succession.

dev:112022-10-09 14:23:29.509debugparse:zw device: 0A, command: 2001, payload: 00, isMulticast: false
dev:112022-10-09 14:23:21.511debugparse:zw device: 0A, command: 2001, payload: FF, isMulticast: false
dev:112022-10-09 14:22:51.877debugparse:zw device: 0A, command: 2001, payload: 00, isMulticast: false
dev:112022-10-09 14:22:47.583debugparse:zw device: 0A, command: 2001, payload: FF, isMulticast: false
dev:112022-10-09 14:22:41.863debugparse:zw device: 0A, command: 2001, payload: 00, isMulticast: false
dev:112022-10-09 14:22:36.141debugparse:zw device: 0A, command: 2001, payload: FF, isMulticast: false
dev:112022-10-09 14:22:29.567debugparse:zw device: 0A, command: 2001, payload: 00, isMulticast: false
dev:112022-10-09 14:22:23.002debugparse:zw device: 0A, command: 2001, payload: FF, isMulticast: false

To me, your test clearly indicates that the hub is receiving messages from your z-wave sensor just fine.

So if your zigbee mesh is ok, and z-wave messages are being received just fine, it indicates there is an issue with the setup of your automation.

Can you post a screen shot of your automation?