[Aeotec Hub] Z-Wave switch not working correctly (July 2023)

Hi @nayelyz and team

I have a V3 hub updated to the latest firmware. But I having some issues with some Z-Wave Switch devices (Wall Switch) that are not working as expected since the previous firmware. My device status is working and updating as expected in the Smartthings App or Web when turning On/Off the physical switch, but when I try to turn it On/Off inside the Smartthings App or Web, Its not working, I get a network issue. Could you please help me to see what could be the root cause? Thank you!

Welcome to the SmartThings Community, @FiruLAD!

I understand, could you provide the things listed below, please?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
  1. Name of the device with the issue
  2. Replicate the issue and while doing that, get the driver’s logs. For this, you need to set up the ST CLI and run the command below:
    smartthings edge:drivers:logcat
    You’ll find the Hub’s IP address in the Advanced Users app > “Hubs” section > Open your Hub details

Thanks a lot for the Support and follow Up @nayelyz :slight_smile:

I just complete all the steps you just mention. I have 3 devices: Switch and its two children’s Light 1 and Light 2 (This because my device has two switches that can be turn on/off).

First I try to turn On/Off the lights inside the Smarthings App, but no success (Network issue). Then I try to turn On/Off the lights in the Physical device, and this works properly and status is reported that lights are turn on/off inside the app for Light1 and Light 2.

Here the Drivers log

2023-07-07T23:05:01.377349740+00:00 TRACE Z-Wave Switch Received event with handler capability
2023-07-07T23:05:01.399433074+00:00 TRACE Z-Wave Switch Z-Wave command(42273673) queued for radio transmission: CC:Switch Multi-level, CID:0x01
2023-07-07T23:05:01.406124740+00:00 INFO Z-Wave Switch <ZwaveChildDevice: 282bdfae-02f3-4033-ac75-b0c5691271fd [9d761dd4-48c4-458e-8446-b1deccc18996][01] (Z-Wave Device Multichannel 1)> received command: {“args”:{},“positional_args”:{},“capability”:“switch”,“component”:“main”,“command”:“on”}
2023-07-07T23:05:01.407630407+00:00 TRACE Z-Wave Switch Found CapabilityCommandDispatcher handler in zwave_switch
2023-07-07T23:05:01.409014074+00:00 TRACE Z-Wave Switch SWITCH_MULTILEVEL supported.
2023-07-07T23:05:01.410447407+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> sending Z-Wave command: {args={duration=“default”, value=“ON_ENABLE”}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“SET”, dst_channels={1}, encap=“AUTO”, payload=“\xFF\xFF”, src_channel=0, version=2}
2023-07-07T23:05:01.440717740+00:00 TRACE Z-Wave Switch Z-Wave command(42273673) transmit status: TRANSMIT_COMPLETE_OK
2023-07-07T23:05:01.456604074+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 1 device thread event handled
2023-07-07T23:05:01.457432074+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 1 device thread event handled
2023-07-07T23:05:06.475876074+00:00 TRACE Z-Wave Switch Z-Wave command(0dd2d3fa) queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-07-07T23:05:06.477381407+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={1}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-07-07T23:05:06.484774407+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 1 device thread event handled
2023-07-07T23:05:06.569841741+00:00 TRACE Z-Wave Switch Z-Wave command(0dd2d3fa) transmit status: TRANSMIT_COMPLETE_OK
2023-07-07T23:05:14.896618408+00:00 TRACE Z-Wave Switch Received event with handler capability
2023-07-07T23:05:14.935899075+00:00 TRACE Z-Wave Switch Z-Wave command(5d46192d) queued for radio transmission: CC:Switch Multi-level, CID:0x01
2023-07-07T23:05:14.955847075+00:00 INFO Z-Wave Switch <ZwaveChildDevice: c0176bff-f7cb-48ed-8bf5-98da0a81cfd1 [9d761dd4-48c4-458e-8446-b1deccc18996][02] (Z-Wave Device Multichannel 2)> received command: {“args”:{},“positional_args”:{},“capability”:“switch”,“component”:“main”,“command”:“on”}
2023-07-07T23:05:14.957643742+00:00 TRACE Z-Wave Switch Found CapabilityCommandDispatcher handler in zwave_switch
2023-07-07T23:05:14.958837408+00:00 TRACE Z-Wave Switch SWITCH_MULTILEVEL supported.
2023-07-07T23:05:14.959999408+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> sending Z-Wave command: {args={duration=“default”, value=“ON_ENABLE”}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“SET”, dst_channels={2}, encap=“AUTO”, payload=“\xFF\xFF”, src_channel=0, version=2}
2023-07-07T23:05:14.970233408+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 2 device thread event handled
2023-07-07T23:05:14.980251075+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 2 device thread event handled
2023-07-07T23:05:15.069822408+00:00 TRACE Z-Wave Switch Z-Wave command(5d46192d) transmit status: TRANSMIT_COMPLETE_OK
2023-07-07T23:05:19.971853076+00:00 TRACE Z-Wave Switch Z-Wave command(36cb6ff7) queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-07-07T23:05:19.980211409+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={2}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-07-07T23:05:19.981952076+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel 2 device thread event handled
2023-07-07T23:05:20.069733076+00:00 TRACE Z-Wave Switch Z-Wave command(36cb6ff7) transmit status: TRANSMIT_COMPLETE_OK
2023-07-07T23:05:42.040974745+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:42.042415412+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={key_attributes=“KEY_RELEASED”, scene_number=2, sequence_number=18, slow_refresh=false}, cmd_class=“CENTRAL_SCENE”, cmd_id=“NOTIFICATION”, dst_channels={}, encap=“NONE”, payload=“\x12\x01\x02”, src_channel=0, version=3}
2023-07-07T23:05:42.055867078+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.058988078+00:00 WARN Z-Wave Switch Attempted to generate event for 9d761dd4-48c4-458e-8446-b1deccc18996.main but it does not support capability Button
2023-07-07T23:05:42.067858078+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:05:42.073554078+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:42.077291412+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={2}, encap=“NONE”, payload=“\xFF”, src_channel=2, version=1}
2023-07-07T23:05:42.094648745+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.105259412+00:00 INFO Z-Wave Switch <ZwaveChildDevice: c0176bff-f7cb-48ed-8bf5-98da0a81cfd1 [9d761dd4-48c4-458e-8446-b1deccc18996][02] (Z-Wave Device Multichannel 2)> emitting event: {“component_id”:“main”,“state”:{“value”:“on”},“attribute_id”:“switch”,“capability_id”:“switch”}
2023-07-07T23:05:42.119279745+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.139301745+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Switch Level
2023-07-07T23:05:42.140617078+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.141814745+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.153473078+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Contact Sensor
2023-07-07T23:05:42.168041412+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.169278412+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Motion Sensor
2023-07-07T23:05:42.171420078+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:42.179210078+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Water Sensor
2023-07-07T23:05:42.182788412+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:05:51.146992413+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:51.148413413+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={key_attributes=“KEY_RELEASED”, scene_number=2, sequence_number=19, slow_refresh=false}, cmd_class=“CENTRAL_SCENE”, cmd_id=“NOTIFICATION”, dst_channels={}, encap=“NONE”, payload=“\x13\x01\x02”, src_channel=0, version=3}
2023-07-07T23:05:51.169593079+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:51.173183413+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={value=0}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={2}, encap=“NONE”, payload=“\x00”, src_channel=2, version=1}
2023-07-07T23:05:51.184614413+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.185412413+00:00 WARN Z-Wave Switch Attempted to generate event for 9d761dd4-48c4-458e-8446-b1deccc18996.main but it does not support capability Button
2023-07-07T23:05:51.199218079+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:05:51.206003746+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.216789079+00:00 INFO Z-Wave Switch <ZwaveChildDevice: c0176bff-f7cb-48ed-8bf5-98da0a81cfd1 [9d761dd4-48c4-458e-8446-b1deccc18996][02] (Z-Wave Device Multichannel 2)> emitting event: {“component_id”:“main”,“state”:{“value”:“off”},“attribute_id”:“switch”,“capability_id”:“switch”}
2023-07-07T23:05:51.230474413+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.244726079+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.246618413+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.252761413+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Contact Sensor
2023-07-07T23:05:51.254246079+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.265611413+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Motion Sensor
2023-07-07T23:05:51.270075079+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:51.278142746+00:00 WARN Z-Wave Switch Attempted to generate event for c0176bff-f7cb-48ed-8bf5-98da0a81cfd1.main but it does not support capability Water Sensor
2023-07-07T23:05:51.281804413+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:05:56.221698747+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:56.225374413+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={key_attributes=“KEY_RELEASED”, scene_number=1, sequence_number=20, slow_refresh=false}, cmd_class=“CENTRAL_SCENE”, cmd_id=“NOTIFICATION”, dst_channels={}, encap=“NONE”, payload=“\x14\x01\x01”, src_channel=0, version=3}
2023-07-07T23:05:56.246934413+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:05:56.250247747+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={1}, encap=“NONE”, payload=“\xFF”, src_channel=1, version=1}
2023-07-07T23:05:56.257284747+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.258098080+00:00 WARN Z-Wave Switch Attempted to generate event for 9d761dd4-48c4-458e-8446-b1deccc18996.main but it does not support capability Button
2023-07-07T23:05:56.262680413+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:05:56.278000080+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.289243413+00:00 INFO Z-Wave Switch <ZwaveChildDevice: 282bdfae-02f3-4033-ac75-b0c5691271fd [9d761dd4-48c4-458e-8446-b1deccc18996][01] (Z-Wave Device Multichannel 1)> emitting event: {“component_id”:“main”,“state”:{“value”:“on”},“attribute_id”:“switch”,“capability_id”:“switch”}
2023-07-07T23:05:56.300773080+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.313726080+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Switch Level
2023-07-07T23:05:56.326997080+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.328611080+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.333980413+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Contact Sensor
2023-07-07T23:05:56.335293747+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.346830747+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Motion Sensor
2023-07-07T23:05:56.358014413+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:05:56.358844413+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Water Sensor
2023-07-07T23:05:56.361233080+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:06:03.443185414+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:06:03.445051081+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={key_attributes=“KEY_RELEASED”, scene_number=1, sequence_number=21, slow_refresh=false}, cmd_class=“CENTRAL_SCENE”, cmd_id=“NOTIFICATION”, dst_channels={}, encap=“NONE”, payload=“\x15\x01\x01”, src_channel=0, version=3}
2023-07-07T23:06:03.469667081+00:00 TRACE Z-Wave Switch Received event with handler unnamed
2023-07-07T23:06:03.473368081+00:00 INFO Z-Wave Switch <ZwaveDevice: 9d761dd4-48c4-458e-8446-b1deccc18996 [12] (Switch)> received Z-Wave command: {args={value=0}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={1}, encap=“NONE”, payload=“\x00”, src_channel=1, version=1}
2023-07-07T23:06:03.480532081+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.481371748+00:00 WARN Z-Wave Switch Attempted to generate event for 9d761dd4-48c4-458e-8446-b1deccc18996.main but it does not support capability Button
2023-07-07T23:06:03.487693081+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled
2023-07-07T23:06:03.502550748+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.528812414+00:00 INFO Z-Wave Switch <ZwaveChildDevice: 282bdfae-02f3-4033-ac75-b0c5691271fd [9d761dd4-48c4-458e-8446-b1deccc18996][01] (Z-Wave Device Multichannel 1)> emitting event: {“component_id”:“main”,“state”:{“value”:“off”},“attribute_id”:“switch”,“capability_id”:“switch”}
2023-07-07T23:06:03.531009414+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.536049748+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.538010414+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.547064748+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Contact Sensor
2023-07-07T23:06:03.557027081+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.561156748+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Motion Sensor
2023-07-07T23:06:03.564710414+00:00 TRACE Z-Wave Switch Found ZwaveDispatcher handler in zwave_switch
2023-07-07T23:06:03.571656748+00:00 WARN Z-Wave Switch Attempted to generate event for 282bdfae-02f3-4033-ac75-b0c5691271fd.main but it does not support capability Water Sensor
2023-07-07T23:06:03.577100748+00:00 DEBUG Z-Wave Switch Z-Wave Device Multichannel device thread event handled

Please let me know if more info is needed from my side @nayelyz Thank you :smiley:

Hi, @FiruLAD

I see that the main device (Switch) supports the capabilities “switch” and “switchLevel” (dimmer) is that right?

It seems that for certain commands, the driver is trying to send events for capabilities that don’t exist for the child device “Light 1” but I’m not sure why, we can see those messages here for example:

Can you share the device’s model and brand so I can look for its fingerprints, please? I need to check if they are included and if so, the configuration to handle its events.

Hi @nayelyz

Mi device (Switch) does support only On/Off function and not switchLevel (Dimmer)
I own a Horus HSC-S511 (I have for only one Light, and also double to control two lights in the same device).

This devices stoped to work when my hub updates with the latest Z-Wave Switch driver. (June 13th version) and with the 48.3 firmware. Before this updates, I was able to control my devices in ST App without issues and either have the proper status when the physical device was used. And in the ST App It was no Dimmer functions until this latest Driver version.

Hi @FiruLAD I was checking the information of you device, unfortunately I can not find this model on the Z-Wave alliance, if a device is not z-wave certified it will most likely not work correctly with the generics drivers, in this case I recommended you to find to use a driver made by the community.

Hi @AlejandroPadilla

But why my device was working perfectly? I had been using my hub and this devices for more that 1 year without issues, and now with this latests updates, my devices are not working any more!!!

And my device is part of the Z-Wave Alliance

@AlejandroPadilla @nayelyz More details about my device

Manufacturer ID:
Horus Smart Control 0x0298

Just try to get a similar device in the catalogue and find this ones, not sure if this can help
@AlejandroPadilla @nayelyz

https://products.z-wavealliance.org/products/1115?selectedFrequencyId=-1 (but with 2 switch for mine)
https://products.z-wavealliance.org/products/3674?selectedFrequencyId=-1

Mmm the company is a affiliate member not a Manufacturer member, but I still have a few doubts about your devices,

  • Do you know if your device was using a custom DTH? because in these days have been migrating some DTH devices.
  • or Was your device using an edge driver before the problem?

Hi @AlejandroPadilla Thanks for the clarification

No, I was not using any custom DTH
And when my drivers was working properly before this catastrophic updates, I were able to see in the IDE page, that all my devices and child devices were Locally running and able to see the routes that my devices were working with my Hub. But when I start to have issues with this devices, the routes were properly wrong, and appears the driver used as “Placeholder”. I can see now in the new IDE page, that when adding my devices, the parent devices is setup as Locally, but the Childs are setup as Cloud and “EDGE_CHILD”

My devices were all working perfectly!! This before June, starting June is when I start to see issues controlling my devices in the ST because they start to not response any action I made in there.

I understand your discomfort, I’m trying to figure out what happened with your device, please can you enable the support access

Enable support access to your account:

  1. Please confirm that the email address that you use in the community is the same as that in SmaertThingsm if not, please send us by private message
  2. Go to the SmartThings Web (my.smartthings.com)
  3. Log in to your Samsung Account
  4. Select Menu (⋮) and choose Settings
  5. Toggle on Account Data Access
  6. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

I already reported that problem and the team is working on it, some devices are no display that value correctly

to verify that value on your device you can use the SmartTings CLI

smartthings devices {deviceid} -j

or you can use the SmartThings API

https://api.smartthings.com/v1/devices/{deviceId}

this is the propriety that you can check with both options

"executingLocally": true,

Thank you @AlejandroPadilla

Account Data Access is enable. And for the 3 devices (Parent and its 2 Childs) it appears “executingLocally”: true

I tried to access your account but I can’t, Are you using the same email address here in Community and SmartThings App? or Are you using another different for SmartThings App?

yes, is the same email for both.

Unfortunately, we tried with the email that you have registered in Community but we don’t have access, you can send the email address of your SmartThings to build@smartthings.com to avoid confusion.