Purchased new SmartThings Sensors, they're not working correctly with a NZ Kickstarter ST hub

Devices & Integrations
1

I have the original Kickstarter Hub and some SmartThings that came with it, they’ve been working without issue. Recently I purchased three new Things - the Button, the Water Leak Sensor and a new Multipurpose Sensor.

All three connected OK, all are reporting temperatures and the Multipurpose Sensor is reporting when it’s active (being moved) but apart from that, the core functionality of each sensor isn’t working - the Button is always reporting that it’s pressed (and after setting it up, pressing it doesn’t trigger what I’d expect it to), the Water Leak Sensor is always reporting that it is dry and the Multipurpose Sensor is always showing as open.

I can see in the IDE that they’re detected as the correct devices. I’m using the Classic app but downloaded the new one without any luck. I’ve also removed, reset and paired the sensors a couple of times but always have the same results. I did try to add them via the new app following the instructions but I don’t see these devices as being available - it only gives me options for Samsung appliances and a couple of other devices.

Does anyone have any suggestions?

1 Like
2

If you are in the USA, you can get a used or refurbished Hub V2 from eBay for ~$50, or a brand new Hub V3 for varying prices depending on promos (?).

While that may not be necessary (let’s see what further answers appear), it may be worth the small expense in order to determine for you, and the benefit of the Community, if that solves your problem.

As an FYI, I experienced something of the reverse situation. I have original “Kickstarter edition” Smart Sense multi-sensors (open, close, temperature, and acceleration-activity). It took several tries to get them added to my SmartThings WiFi (Hub V3.25), but they now work - partially. Open/Close works, but not activity, nor battery. :confused:

I could experiment and try reconnecting these sensors to my V1 Hub, though I’d rather move forward with my slow migration of devices from V1 to V3.25.

I also have an original ZigBee Dev Shield; that’s running my Projector and Screen. I have no idea what’s going to happen when I try to migrate it. I feel I might just end up keeping it connected to V1 indefinitely.

BTW: Using New App, you can add multiple Hubs to the same SmartThings Location. That means you can keep using your V1 Hub, while you add various devices to V3, and they can be used in the same SmartApps (SHM, Smart Lighting, Scenes, Routines, etc.); even from the Classic App. You just need to use the New App to join the new Hub to the old Location - then either App is usable with your new double-Hub Location…

3

Thank you for all of that information! Unfortunately I’m not in the USA, I’m in New Zealand which makes it difficult as we have a different frequency authorised for Z-Wave and I’m not sure if I’d be able to disable that in a V2 Hub. I’ll look into whether this is viable - while it wouldn’t be ideal to be running two Hubs, it’s good to know that it’s possible to do so.

I suspect all of the functionality around interpreting and reporting device data was handled by the DeviceTypeHandlers, so will also see if it’s possible to find and fork the official DTH and do some logging to see what’s going on. I definitely don’t know enough about this, but it seems like the version of the Hub used shouldn’t make a difference. When I dig deeper into the IDE, I see that the Water Leak Sensor doesn’t contain any parameters for dry/wet and the Multipurpose Sensor doesn’t have open/close - it actually has a few other things missing when compared to my original Kickstarter Multi Sensors - would be interesting to see if you see something similar for your Kickstarter vs new sensors. The Button does have the pressed parameter and it is in fact reporting that it’s always pressed.

Edited to add that I can see that z-wave can be disabled on a Hub via the IDE, so I’ll look into ordering a V2 or V3 Hub if I’m unable to get the new devices working on my original Hub.

4

Yes you can disable the zwave radio from the IDE.

1 Like
5

I’m not 100% sure, but I don’t think it’s legal to import a US hUB into New Zealand As they are one of the strictest in the world on enforcing Z wave frequency because they run some police bands That would be subject to interference.

Smartthings has just recently started to release hubs on The New Zealand frequency for sale in Australia though right now they are only being sold through RACV. But you may be able to find some eventually.

6

Tagging @tpmanley

7

@katiebot, can you try factory resetting and joining one the button while you have live logs (https://graph.api.smartthings.com/ide/logs) open in the IDE and see what gets logged?

2 Likes
8

@tpmanley thanks for the tip! I’ve just done this, I only selected the logs for the button:

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:52: debug enroll response: [st wattr 0x4BB4 0x01 0x0500 0x0010 0x00F0 {D052A80707250001}, delay 2000, raw 1280 {01 23 00 00 00}, delay 200, send 0x4BB4 0x1 0x1, delay 2000]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:52: debug Parse returned [:]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:52: debug description: enroll request endpoint 0x01 : data 0x0002

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:50: debug Parse returned [name:temperature, value:32, unit:C, descriptionText:Button was 32°C, translatable:true]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:50: debug description: catchall: 0104 0402 01 01 0140 00 4BB4 00 00 0000 01 01 000000295D0C

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:48: debug Parse returned [name:battery, translatable:true, descriptionText:{{ device.displayName }} battery was {{ value }}%, value:99]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:48: debug Battery Percentage rawValue = 197 -> 98.5%

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:48: debug description: read attr - raw: 4BB40100010A21000020C5, dni: 4BB4, endpoint: 01, cluster: 0001, size: 0A, attrId: 0021, result: success, encoding: 20, value: c5

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:46: debug Parse returned [:]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:46: debug TEMP REPORTING CONFIG RESPONSE: [raw:0104 0402 01 01 0140 00 4BB4 00 00 0000 07 01 00, profileId:0104, clusterId:0402, sourceEndpoint:01, destinationEndpoint:01, options:0140, messageType:00, dni:4BB4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:1026, commandInt:7]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:46: debug description: catchall: 0104 0402 01 01 0140 00 4BB4 00 00 0000 07 01 00

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:42: debug Parse returned [:]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:42: debug description: catchall: 0104 0001 01 01 0140 00 4BB4 00 00 0000 07 01 00

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:34: debug enroll response: [st wattr 0x4BB4 0x01 0x0500 0x0010 0x00F0 {D052A80707250001}, delay 2000, raw 1280 {01 23 00 00 00}, delay 200, send 0x4BB4 0x1 0x1, delay 2000]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:34: debug Parse returned [:]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:34: debug description: enroll request endpoint 0x01 : data 0x0002

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:32: debug Parse returned [name:temperature, value:32, unit:C, descriptionText:Button was 32°C, translatable:true]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:32: debug description: catchall: 0104 0402 01 01 0140 00 4BB4 00 00 0000 01 01 000000295D0C

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug Parse returned [name:battery, translatable:true, descriptionText:{{ device.displayName }} battery was {{ value }}%, value:99]

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug Battery Percentage rawValue = 197 -> 98.5%

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug description: read attr - raw: 4BB40100010A21000020C5, dni: 4BB4, endpoint: 01, cluster: 0001, size: 0A, attrId: 0021, result: success, encoding: 20, value: c5

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug Refreshing Values

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug Refreshing Values

9d63778c-2ab1-43b3-9498-c9369d0ea729 19:26:29: debug Configuring Reporting

9

@katiebot, thanks, I think the problem will be fixed if you contact support and ask them to update the firmware on the Zigbee radio on your hub. There was a bug in an older version of the firmware that I think would cause the problems you’re experiencing.

1 Like
10

I’ll do that now - thank you so much!

11

If anyone else encounters the same issue, this was resolved by the SmartThings team pushing a zigbee update to my hub. Thanks again everyone who helped!

1 Like