ST App: A network or server error occurred. Try again later

How can we solve this issue?
Is it due to the hub or the device itself?
In my situation, it kept repeating while configuring the relay from toggle to momentary.

What version of the hub do you have? What is the model number of the device, and is it Z-Wave or Zigbee? Is this device newly added, or has it been working before? What driver is the device using? It may not have paired with SmartThings correctly.

It is a problem with the app, when you make a change to a value in a capability and choose the same value, the app expects another different value and does not accept the event sent by the driver.

They already fixed it some time ago and now it’s back, it’s like groundhog day.

The driver works well and configures device correctly.

3 Likes

Today I’m seeing the same error when I try to do anything to my devices, without any recent value changes. Basically can’t do anything manually at this point. Any known W/As?

Hub V2 w/latest FW

Well, you are right, something else has changed in the App or God knows where, the capabilities do not show the events that the driver sends, even after changing the assigned profile, a refresh is carried out in the app and the app continues saying that there is no assigned value and connection failure.

I have been looking in the logs and increasing the delay from 1 sec to 3 seconds to emit the events after changing the profile, it seems to work well again.

I will modify it in the affected drivers and wait for them to break it again, but they will have ruined more profile changes in the numerous drivers that use this function, it is exasperating :grimacing: :man_facepalming:

───────────────────────────────────────────────────
 Name         Z-Wave Switch and Child Mc
 Version      2024-02-22T13:50:20.801563314        
───────────────────────────────────────────────────
─────────────────────────────────────────────────── 
 Name         Z-Wave Device Config Mc
 Version      2024-02-22T13:55:28.891851756        
───────────────────────────────────────────────────
──────────────────────────────────────────────────── 
 Name         Z-Wave Sensor and Child Thermostat Mc 
 Version      2024-02-22T13:55:53.637077999
────────────────────────────────────────────────────

If the capabilities are not updated after the profile change, perform a refresh and they will be updated

1 Like

By the way, they have also changed something in the creation of child devices, now new child devices appear in the same room where the parent device is, instead of the room where the Hub is.

But not always, I’ll try to guess why some do and others don’t, how fun! :joy:

4 Likes

Mine looks to be working again. I assume the updates propagated automagically through the subscribed channel. Thanks!

Hi @nayelyz

Something has changed in the App or there is a problem in the platform, that when the driver sends the capabilities events the app does not update them and issues a network error.

It happens in a subdriver that configures parameters and association groups in Zwave devices.

When you change the profile to make changes to parameters or groups, etc., the values are emitted to initialize the capabilities, but now it no longer works. This has worked perfectly for over a year.

Even if you refresh the App, the events are seen in the CLI logs and the App’s capabilities are not updated.

I added a delay between the profile change function and the broadcast of the events and it worked for a while, but again it doesn’t work

In these logs you can see that a refresh is performed and the values of the three capabilities are emitted.

2024-02-22T15:45:35.932709674Z TRACE Z-Wave Switch and Child Mc  Received event with handler capability
2024-02-22T15:45:36.400478382Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2024-02-22T15:45:36.422330966Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> Lazy loaded driver into dispatcher: fibaro double switch
2024-02-22T15:45:36.458142466Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> Lazy loaded driver into dispatcher: Device Config subdriver
2024-02-22T15:45:36.472446757Z TRACE Z-Wave Switch and Child Mc  Found CapabilityCommandDispatcher handler in zwave_switch -> Device Config subdriver
2024-02-22T15:45:36.477516924Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"parameterStart","capability_id":"legendabsolute60149.parameterStart","component_id":"main","state":{"value":1},"visibility":{"displayed":false}}      
2024-02-22T15:45:36.492311466Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"parameterEnd","capability_id":"legendabsolute60149.parameterend","component_id":"main","state":{"value":255},"visibility":{"displayed":false}}        
2024-02-22T15:45:36.499173716Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"deviceInfo","capability_id":"legendabsolute60149.deviceInfo","component_id":"main","state":{"value":"<table style='font-size:65%'> <tbody><tr> <th align=left></th> <td><em style='color:blue;font-weight: bold;'> Z-Wave Device Parameters Scan: </em> <BR><em style='color:black;font-weight: bold;'> 1- Enter Parameter Number to Start.</em> <BR><em style='color:black;font-weight: bold;'> 2- Enter Parameter Number to End.</em> <BR><em style='color:black;font-weight: bold;'> * 3- If device is Asleep: Awake device manually.</em> 
<BR><em style='color:black;font-weight: bold;'> 4- Press Action Button.</em> <BR><em style='color:green;font-weight: bold;'> 5- Parameter Number, Value & Size will be shown</em></td></tr></tbody></table>"},"visibility":{"displayed":false}}

In this screenshot you can see what the app shows

The deviceInfo capability is updated, but the other two are not.

If in the driver I change the initial values of the capabilities from 1 to 2 and from 255 to 254 it works again, but if I reinstall the driver it fails again, I don’t understand anything

024-02-22T16:17:00.096988659Z TRACE Z-Wave Switch and Child Mc  Found DeviceLifecycleDispatcher handler in zwave_switch -> Device Config subdriver
2024-02-22T16:17:00.101564034Z PRINT Z-Wave Switch and Child Mc  <<<< info_Changed in device-config subdriver >>>>
2024-02-22T16:17:00.106230284Z PRINT Z-Wave Switch and Child Mc  device.preferences[infoChanged]=       Param   preferences:    changeConfigProfile
2024-02-22T16:17:00.110825992Z PRINT Z-Wave Switch and Child Mc  device.preferences[infoChanged]=               preferences:    version
2024-02-22T16:17:00.153782992Z DEBUG Z-Wave Switch and Child Mc  Device Info-Luz Escalera device thread event handled
2024-02-22T16:17:01.619121992Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"parameterStart","capability_id":"legendabsolute60149.parameterStart","component_id":"main","state":{"value":2},"visibility":{"displayed":false}}      
2024-02-22T16:17:01.640249867Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"parameterEnd","capability_id":"legendabsolute60149.parameterend","component_id":"main","state":{"value":254},"visibility":{"displayed":false}}        
2024-02-22T16:17:01.659541575Z INFO Z-Wave Switch and Child Mc  <ZwaveChildDevice: 1ffeacac-53ac-4543-9e65-d20d17b6ebaa [ac895f6b-9e11-4a96-83a6-c4b8f175422b][main] (Device Info-Luz Escalera)> emitting event: {"attribute_id":"deviceInfo","capability_id":"legendabsolute60149.deviceInfo","component_id":"main","state":{"value":"<table style='font-size:65%'> <tbody><tr> <th align=left></th> <td><em style='color:blue;font-weight: bold;'> Z-Wave Device Parameters Scan: </em> <BR><em style='color:black;font-weight: bold;'> 1- Enter Parameter Number to Start.</em> <BR><em style='color:black;font-weight: bold;'> 2- Enter Parameter Number to End.</em> <BR><em style='color:black;font-weight: bold;'> * 3- If device is Asleep: Awake device manually.</em> 
<BR><em style='color:black;font-weight: bold;'> 4- Press Action Button.</em> <BR><em style='color:green;font-weight: bold;'> 5- Parameter Number, Value & Size will be shown</em></td></tr></tbody></table>"},"visibility":{"displayed":false}}

@nayelyz I hope you can find some explanation!, Thanks

EDIT, In case it helps:
If in any capability that supports a value change command, if you set the same value that the capability already has, it also gives a network error, but since the capability is initialized it does not stop working.

In the Capability Temperatura, Valor de CondiciΓ³n de ComparaciΓ³n, I enter the same value 0, the driver sends the value 0, but the app gives a network error

I think is similar issue

2024-02-22T17:06:08.853033837Z TRACE Zigbee Temp Sensor and Child Thermostat Mc  Received event with handler capability
2024-02-22T17:06:08.872417504Z INFO Zigbee Temp Sensor and Child Thermostat Mc  <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0x0874] (Environment Sensor)> received command: {"args":{"value":0},"capability":"legendabsolute60149.tempCondition2","command":"setTempCondition","component":"main","positional_args":[0]}
2024-02-22T17:06:08.896383962Z TRACE Zigbee Temp Sensor and Child Thermostat Mc  Found CapabilityCommandDispatcher handler in st-zigbee-temp
2024-02-22T17:06:08.901961587Z PRINT Zigbee Temp Sensor and Child Thermostat Mc  set_TempCondition.value=       0
2024-02-22T17:06:08.907180004Z INFO Zigbee Temp Sensor and Child Thermostat Mc  <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0x0874] (Environment Sensor)> emitting event: {"attribute_id":"tempTarget","capability_id":"legendabsolute60149.tempTarget","component_id":"main","state":{"value":"Equal-Up"}}
2024-02-22T17:06:08.913093504Z INFO Zigbee Temp Sensor and Child Thermostat Mc  <ZigbeeDevice: eb7c780e-e667-46ab-ba47-ea81341df249 [0x0874] (Environment Sensor)> emitting event: {"attribute_id":"tempCondition","capability_id":"legendabsolute60149.tempCondition2","component_id":"main","state":{"unit":"C","value":0}}

1 Like

When I deleted child device and created another child configure device it didn’t work again, I hope yours still works.

What app do you use Android or iO’s?

IOS.

Frankly I’m not sure my issue was related to your drivers, since the network hang was also happening when I tried to control devices using stock ST drivers.

This only happens when you change the profile of a device, right?
In my tests, I saw the following:

  1. The device is installed and initialized correctly
  2. If we change the device’s profile and immediately send events to its capabilities, they are not initialized if they were not included in the previous one.
    For example, if the previous profile had Switch and thermostatMode, but then changed to another that has Switch, thermostatMode and smokeDetector, the first two will take the new value we send but β€œsmokeDetector” won’t be initialized.

Hi @nayelyz thanks for your response

That seems correct, in fact in the logs I can see warnings because driver try to emit some events in some capabilities that do not exist in the profile.

This is solved by increasing the delay to 3 sec to emit values, although it has been working for almost 2 years without problems with a delay of 1 sec.

The problem is that once the profile is updated, if you refresh in app, the values of the capabilities are emitted by driver and the app does not show them and it stays that way until you modify the emitted values, as I mentioned in the post.

2 Likes

I’m using ST Hub V3, and the device name is Flush 2 Relay Pro(Z-wave,) newly add into the hub and the driver’s name is β€œZ-Wave Device Config Mc”. So, what is the proper way?

Mariano said this is a problem with the ST Ap and not a problem with the device or the driver.

What do you want to configure on this device? parameters or association groups?

This driver is only used for this, viewing or configuring parameters or association groups.

Once you have chosen what you want to do in preferences and if it does not allow you to change data in app, then perform several refreshes by sliding your finger in the details view, exit the app, device, to see if you are lucky and the capabilities are initialized.

Let’s hope they fix the issue soon.

1 Like

While solving the network error problem that leaves the device inoperative because it does not allow values to be entered and you need to use the parameter configurator or association groups with Z-Wave Device Config Mc or with the child device configurator incorporated in the Z-Wave Switch drivers and Child Mc or Z-Wave Sensor and Child Thermostat Mc then you could follow this procedure.

When you open the profile you need and get the network error and data capabilities are greyed out:

  • Does not remove the Child configurator device
  • Perform a refresh and leave that profile selected for approximately 30 minutes even if you close the details view.
  • Reopen the device and perform a refresh, the initial values should appear and start working.
  • If not, wait a little longer and do the previous step again.
  • You will need to perform this process on each profile that does not work.
  • Once it works, it will always work until you delete the child device configuration or change the device driver if you are using Z-Wave Device Config Mc.

This problem seems to be caused by a problem in the initialization of some capabilities when the driver emits the initial values.
For some reason, those values that the driver emits, the Hub does not send them to the platform or the platform does not admit them as new events.
Even if from the smartthings page, advanced users, you send the commands with the values, these values are received in the driver and the driver emits the values, but they are not displayed in smartthings, advanced users or in the app until after about 30 minutes

@Nayelyz has already opened a report and we hope smartthings find the solution soon.

1 Like