View Categories

Actions – ‘Device not found’

0:00 1:29

Symptoms:

  • The action is triggered but is not executed.
  • The app displays the message ‘Device not found’.
  • Some of the devices are working properly, whilst others do not respond to commands.
  • The controller is visible in the app, but the associated automations cannot be run.

Possible causes:

  • The target device has been removed from the system or reset to its factory settings.
  • The device’s network configuration (e.g. IP address) has been changed, and the action is referring to out-of-date data.
  • The target device is offline or has lost its connection to the Wi-Fi network.
  • The action was created before the device was added back to the system.
  • There has been a problem with communication between devices on the local network.

Suggested solutions:

  1. Check whether the device specified in the promotion is available and visible in the app.
  2. Check that the device has an active connection to the Wi-Fi network.
  3. Open the action configuration and check that all assigned devices are correct.
  4. If the device has been removed or reset, create the action again.
  5. Check whether the devices can communicate with each other on the local network (no client isolation, VLANs configured correctly).
  6. Once you have made the changes, save the configuration and test the action again.

Note for the installer:
The message ‘Device not found’ usually means that the action refers to a device that is no longer available under the identifier saved when the automation was created. This problem often occurs after the device has been reset, re-added to the system, or following changes to the network configuration.

Scroll to Top