Samsung multisensor always open on garage door

🛎️ Get Help
1

I've got a pair of Samsung multisensors on my garage doors, which I use to sense when the garage doors are opened. The main goal is to send me a text reminder to close them if they're still open late enough in the evening. These worked just fine when paired my ST hub, but with my new HE, they always think the doors are opened. Both of them are behaving the same way, so it seems unlikely to be some sort of freak hardware failure. I've removed and relinked them with my HE hub, to no avail. Any other tricks to try?

Thanks,

Brian

2

I've had similar problems moving those sensors over from ST but always managed to get them working In the end. Try these steps...
Pair the device then delete It and pair again, go to the device and hit configure as soon as you can.
Replace or remove the battery for a while.

3

Did you make sure the sensor was oriented correctly?

20190414_134409
20190414_134409.png1440×1817 260 KB

Also you need to toggle the switch on the device preferences that it is being used as a garage sensor.

20190414_134550
20190414_134550.png1440×1557 120 KB

1 Like
4

Yep, the sensor is definitely oriented correctly. It's been working fine with a ST hub for a couple of years, now. Also, I forgot to mention that I had already found the box in the device configuration page that allowed me to say that I was using it as a garage sensor.

I'll try pulling the batteries for a few minutes, and going through the loop a couple of times.

Thanks for the ideas!

Brian

5

I've got through the add-remove-configure loop at least half a dozen times. Sometimes doing a reset on the sensor, and sometimes just removing/adding it, all to no avail. Anybody else hit this, and find a way to get it working?

6

What do you see in the logs?

7

A fair bit of stuff, none of which looks particularly enlightening to my untrained eye. This is what I see related to that sensor (I just had a window open watching the logs, and then ran off to pair the sensor and put it in garage mode):

dev:982019-04-14 02:24:30.092 pm debughandleAcceleration: [raw:AB2E01FC021E120029E9FF130029FAFB1400291F00, dni:AB2E, endpoint:01, cluster:FC02, size:1E, attrId:0012, encoding:29, command:0A, value:FFE9, clusterInt:64514, attrInt:18, additionalAttrs:[[value:FBFA, encoding:29, attrId:0013, consumedBytes:5, attrInt:19], [value:001F, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
dev:982019-04-14 02:24:30.084 pm debugparse: read attr - raw: AB2E01FC021E120029E9FF130029FAFB1400291F00, dni: AB2E, endpoint: 01, cluster: FC02, size: 1E, attrId: 0012, encoding: 29, command: 0A, value: E9FF130029FAFB1400291F00
dev:982019-04-14 02:24:29.321 pm infoGarage Door 2 is inactive
dev:982019-04-14 02:24:29.318 pm debughandleAcceleration: [raw:AB2E01FC020810001800, dni:AB2E, endpoint:01, cluster:FC02, size:08, attrId:0010, encoding:18, command:0A, value:00, clusterInt:64514, attrInt:16]
dev:982019-04-14 02:24:29.315 pm debugparse: read attr - raw: AB2E01FC020810001800, dni: AB2E, endpoint: 01, cluster: FC02, size: 08, attrId: 0010, encoding: 18, command: 0A, value: 00
dev:982019-04-14 02:24:29.101 pm debughandleAcceleration: [raw:AB2E01FC021E120029E8FF130029FEFB1400292000, dni:AB2E, endpoint:01, cluster:FC02, size:1E, attrId:0012, encoding:29, command:0A, value:FFE8, clusterInt:64514, attrInt:18, additionalAttrs:[[value:FBFE, encoding:29, attrId:0013, consumedBytes:5, attrInt:19], [value:0020, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
dev:982019-04-14 02:24:29.094 pm debugparse: read attr - raw: AB2E01FC021E120029E8FF130029FEFB1400292000, dni: AB2E, endpoint: 01, cluster: FC02, size: 1E, attrId: 0012, encoding: 29, command: 0A, value: E8FF130029FEFB1400292000
dev:982019-04-14 02:24:28.101 pm debughandleAcceleration: [raw:AB2E01FC021E120029E9FF130029FCFB1400291900, dni:AB2E, endpoint:01, cluster:FC02, size:1E, attrId:0012, encoding:29, command:0A, value:FFE9, clusterInt:64514, attrInt:18, additionalAttrs:[[value:FBFC, encoding:29, attrId:0013, consumedBytes:5, attrInt:19], [value:0019, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
dev:982019-04-14 02:24:28.094 pm debugparse: read attr - raw: AB2E01FC021E120029E9FF130029FCFB1400291900, dni: AB2E, endpoint: 01, cluster: FC02, size: 1E, attrId: 0012, encoding: 29, command: 0A, value: E9FF130029FCFB1400291900
dev:982019-04-14 02:24:27.092 pm debughandleAcceleration: [raw:AB2E01FC021E120029E8FF130029FAFB1400291A00, dni:AB2E, endpoint:01, cluster:FC02, size:1E, attrId:0012, encoding:29, command:0A, value:FFE8, clusterInt:64514, attrInt:18, additionalAttrs:[[value:FBFA, encoding:29, attrId:0013, consumedBytes:5, attrInt:19], [value:001A, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
dev:982019-04-14 02:24:27.084 pm debugparse: read attr - raw: AB2E01FC021E120029E8FF130029FAFB1400291A00, dni: AB2E, endpoint: 01, cluster: FC02, size: 1E, attrId: 0012, encoding: 29, command: 0A, value: E8FF130029FAFB1400291A00
dev:982019-04-14 02:24:26.080 pm infoGarage Door 2 is active
dev:982019-04-14 02:24:26.077 pm debughandleAcceleration: [raw:AB2E01FC022610001801120029E6FF130029FAFB1400291D00, dni:AB2E, endpoint:01, cluster:FC02, size:26, attrId:0010, encoding:18, command:0A, value:01, clusterInt:64514, attrInt:16, additionalAttrs:[[value:FFE6, encoding:29, attrId:0012, consumedBytes:5, attrInt:18], [value:FBFA, encoding:29, attrId:0013, consumedBytes:5, attrInt:19], [value:001D, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
dev:982019-04-14 02:24:26.066 pm debugparse: read attr - raw: AB2E01FC022610001801120029E6FF130029FAFB1400291D00, dni: AB2E, endpoint: 01, cluster: FC02, size: 26, attrId: 0010, encoding: 18, command: 0A, value: 01120029E6FF130029FAFB1400291D00
dev:982019-04-14 02:24:25.326 pm debugdescMap.cluster: null
dev:982019-04-14 02:24:25.323 pm debugparse: catchall: 0104 FC02 01 01 0040 00 AB2E 00 01 104E 07 01 86001000
dev:982019-04-14 02:24:23.485 pm warndescription logging is: true
dev:982019-04-14 02:24:23.482 pm warndebug logging is: true
dev:982019-04-14 02:24:23.479 pm warngarage option: Opt
dev:982019-04-14 02:24:23.476 pm infoupdated...
dev:982019-04-14 02:24:17.465 pm debugdescMap.cluster: 0500
dev:982019-04-14 02:24:17.457 pm debugparse: read attr - raw: AB2E0105000C0200192500, dni: AB2E, endpoint: 01, cluster: 0500, size: 0C, attrId: 0002, encoding: 19, command: 01, value: 2500
dev:982019-04-14 02:24:17.392 pm infoGarage Door 2 battery is 100%
dev:982019-04-14 02:24:17.388 pm debuggetBatteryResult: 30
dev:982019-04-14 02:24:17.385 pm debugparse: read attr - raw: AB2E0100010A2000201E, dni: AB2E, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, encoding: 20, command: 01, value: 1E
dev:982019-04-14 02:24:17.380 pm debugparseReportAttributeMessage: Temp resultMap: [name:temperature, value:73.98, descriptionText:Garage Door 2 temperature is 73.98°F, unit:°F]
dev:982019-04-14 02:24:17.377 pm infoGarage Door 2 temperature is 73.98°F
dev:982019-04-14 02:24:17.349 pm debugparse: read attr - raw: AB2E0104020C0000291C09, dni: AB2E, endpoint: 01, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, command: 01, value: 1C09
dev:982019-04-14 02:24:17.286 pm debugdescMap.cluster: null
dev:982019-04-14 02:24:17.283 pm debugparse: catchall: 0104 FC02 01 01 0040 00 AB2E 00 01 104E 07 01 86001400

<cut bunches of repeats of the "null" followed by a hex dump>

dev:982019-04-14 02:24:10.295 pm debugparse: catchall: 0000 8021 00 00 0040 00 AB2E 00 00 0000 00 00 D300
dev:982019-04-14 02:24:09.335 pm debugdescMap.cluster: null
dev:982019-04-14 02:24:09.332 pm infoSmartSense Multi Sensor V4 was opened
dev:982019-04-14 02:24:09.328 pm debugparse: zone status 0x0025 -- extended status 0x00
dev:982019-04-14 02:24:09.325 pm debugparse: catchall: 0000 8005 00 00 0040 00 AB2E 00 00 0000 00 00 C9002EAB020102
dev:982019-04-14 02:24:09.310 pm debugdescMap.cluster: null
dev:982019-04-14 02:24:09.305 pm debugparse: catchall: 0104 0500 01 01 0040 00 AB2E 00 00 0000 0B 01 0000
dev:982019-04-14 02:24:08.276 pm debugdescMap.cluster: null
dev:982019-04-14 02:24:08.272 pm debugparse: catchall: 0104 0500 01 01 0040 00 AB2E 00 00 0000 04 01 00
dev:982019-04-14 02:24:07.466 pm warnconfigure...
8

May or may not help. I also used smartthings and my garage sensors worked just fine, when I moved over to HE I was having problems pairing and when they would pair they would suddenly stop updating status. I ended up adding an outlet to repeat the zigbee signal and things have been stable.

9

The sensor just immediately thinks it's opened, and won't change it's mind. The "acceleration" detection works fine, and makes it to the HE. The close sensor is probably only about 8 feet away, though a single wall - it's just a long run from my office through the house and into the garage.

The timing idea might be onto something. I grabbed a brand new sensor, pulled the tab, and paired it all sitting at my desk (so no running around delays), and it worked perfectly on the first try. I might have to try prying those things off the garage door and pair them sitting at my desk.

Thanks,

Brian

10

I would think if it is successfully reporting other attributes (other than open/close) it would not be a connectivity/communication problem.

I'm not familiar with setting one of these up for the garage door . . . do you slide the toggle over and hit configure?

11

I've just been throwing the toggle and hitting "Save Preferences." I can't figure out what the "Configure" button does - I've never seen anything change as a result of pushing it.

12

This is really strange. I pulled both sensors off the door, and started playing with them at my desk, where I could see status updates reflected more easily. Both of these sensors were working fine before, but now they don't register as closed unless I rotate them 90 degrees (either way works, they just have to be "horizontal" instead of "vertical"). The open/close transitions seem to work that way, so I may just try mounting them like that and see if that works long term. No idea how/why this happened to two sensors at the same time, but something that may be worth trying for anybody else hitting problems like this.

13

Just bumped into this issue last night. It was working fine as an open/close sensor, on a regular door, but was generating numerous, unwanted xyz axis events using Garage Door set to NO

Set the sensor to Yes (xyz off) stopped the xyz events, but open and close where backwards, if sent at all. However, I did not immediately realize the setting was the culprit, and thought the sensor failed. Changed batteries, no joy. Decided to give up and work on it in the morning, but then I could not arm my system because the sensor was Open and would never Close. Had to remove the sensor from HSM settings to arm the system.

This morning got to the point of resetting the sensor and re-pairing it to HE, no joy. After many attempts at setting NO on the "do you use this sensor on a garage door to take" and having it actually work I found the answer. Looking in the log I found that even when setting NO the the garage option would be null. For functional open/close events it has to be No in the log. It would not properly set NO until I turned on description logging.

image
image.png1036×73 9.38 KB

image
image

tagging @mike.maxwell @chuck.schwer @bravenel

14

which driver is this?

15

image

16

This works for me too. in ST I had the device mounted vertically and it was fine for years. I couldn't get it to register closed in HE until I mounted it horizontally.

17

Apparently this still hasn't been addressed since I just ran across the same problem. I am new to Hubitat, moving over from Wink. I tried Smartthings but it's too messy with the multiple apps they have going on plus I like the idea that most things will work without the cloud. I had these sensors mounted vertically for Smartthings and it worked great with them but was a no-go for Hubitat. Changed them to horizontal and all is well! I'm glad I found this post as I was scratching my head over it.

3 Likes
18

Welcome to the community @kurtchief

1 Like
19

Thanks Bryan I'm excited to be part of it!

1 Like