I have been supporting the SleepNumber integration for a while and am experiencing some odd behavior with the SmartThings API recently.
I initiate a commandRequest via the app for my device and see it begin in the logs. 5 seconds later (consistently) SmartThings issues an interactionResult indicating that there was a node fetch error. The logs show the continued execution of the commandRequest and a valid response.
Did something change with SmartThings such that it now has a 5 second timeout or something along those lines? Sample requests:
TIMESTAMP: 2025-10-16 17:57:01
{"headers":{"schema":"st-schema","version":"1.0","interactionType":"commandRequest","requestId":"1bf10bed-<removed>"},"authentication":{"tokenType":"Bearer","token":"<removed>"},"devices":[{"externalDeviceId":"<removed>","deviceCookie":{"updatedcookie":"12345"},"commands":[{"component":"main","capability":"st.switchLevel","command":"setLevel","arguments":[95]}]}]}
TIMESTAMP: 2025-10-16 17:57:06
{"headers":{"schema":"st-schema","version":"1.0","interactionType":"interactionResult","requestId":"1bf10bed-<removed>"},"authentication":{"tokenType":"Bearer","token":"<removed>"},"deviceState":[{"deviceError":[{"errorEnum":"BAD-RESPONSE","detail":"nodeFetch error for SleepNumber Bed Integration"}]}]}