Jump to content

Command error


Recommended Posts

The first thing to check is that the command exists and has not changed. Changes may occur on Node Server update or firmware update, although the latter is less likely.  Synchronization then edit the command (on the bottom of favorite edit screen) should reset the command if it has changed.

Assuming the command exists, I have seen this at times when commands for the same node are executed in a short time frame.  The error is coming from eisy, although it could be an issue passed from PG3 or the Node Server.

At this time UD Mobile does not show logs, but it would be helpful to see if eisy, PG3, and/or the Node Server have logged errors when this happens.

Link to comment
This topic is now closed to further replies.

  • Create New...