October 4Oct 4 @Javi When I turn on or off an Elk output in UDM, I get the following error message. The command does go thru however. This error does NOT show up in the UI.
October 5Oct 5 This is usually caused when the plugin software (PG3) does not respond to a command before the controller timeout. It could be the plugin software, the plugin itself, or if too many commands a re sent consecutively.Did this recently start after some change (e..g migrating to eisy-ui plugins from PG3)? Is is sporadic?
October 5Oct 5 Author I am not sure when it started, but it happens every time. The command does get executed however.
October 5Oct 5 Author yes, its been doing it for a while now and I have rebooted the EISY after each of the new upgrades. The error only appears in UDM.. it does not appear in the UI.
October 5Oct 5 It is likely eisy-ui fails to propagate the error to the user. Will likely show the same error response in the browser's developer tools.Unfortunately I don't have a good test case on when or why this happens, so will need help identifying the cause. If anyone checks the PG3 or Plugins log it may show an error which we can isolate.
October 6Oct 6 Author 19 hours ago, Javi said:It is likely eisy-ui fails to propagate the error to the user. Will likely show the same error response in the browser's developer tools.Unfortunately I don't have a good test case on when or why this happens, so will need help identifying the cause. If anyone checks the PG3 or Plugins log it may show an error which we can isolate.I am able to easily repeat this error because it happens every time. So I cycled an elk output called Sprkl Drip Line (n014_output_28) and downloaded all the possible logs for pgx and the debug log from the Elk plugin.Begin at time 026-10-06 08:26:58.085 Command udi_interface DEBUG Output:cmd_set_on: output_28:Sprkl Drip Line in Elk Debug Log.Admin Edit <removed attached files>Thanks.
October 6Oct 6 I randomly get those errors on ud Mobile as well. The command succeeds, yet I get an error. Unlike the op, I am not consistently seeing it.
October 6Oct 6 2 hours ago, dbwarner5 said:I am able to easily repeat this error because it happens every time. So I cycled an elk output called Sprkl Drip Line (n014_output_28) and downloaded all the possible logs for pgx and the debug log from the Elk plugin.Begin at time 026-10-06 08:26:58.085 Command udi_interface DEBUG Output:cmd_set_on: output_28:Sprkl Drip Line in Elk Debug Log.Admin Edit <removed attached files>Thanks.Does this only happen when multiple commands are issued in a short period, less than 1 second apart? This seems too fast for a human, is there are program that triggers another command to the same nodeserver at the same time.2026-10-06 08:26:58.082 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_28/cmd/DON....2026-10-06 08:26:58.153 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON...2026-10-06 08:26:58.234 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON
October 7Oct 7 Author No..it happens every time I "press" the button in UDM to change the state of the node. Time in between changes is irrelevant.
Wednesday at 01:21 PM5 days Author It’s my sprinkler system. So when I turn a valve on, there is a program that turns on the pump. Ill add a delay and see if that helps but when I turn it off I really need the pump to shut down immediately so may still have the problem but will play with a 1 second delay
Wednesday at 03:26 PM5 days Solution Being as it works, the issue is just feedback. Due to the future migration PG3 to eisy-ui Plugins, I'm not sure if we would investigate the issue on PG3 (as it could be one of the limitations we hope to solve with eisy-ui plugins). If the Elk plugin works on Plugins (Beta) we can investigate the response issue.
Wednesday at 07:24 PM5 days Author agree.. will just watch it. I did put in delays and still go the messages.. no worries.
Wednesday at 09:18 PM5 days This is the same issue I see, this is arming my Elk panel. It succeeded in arming, but I got the message. It is a command type of favorite that sets the alarm system to armed night in this instance. Arming the system also triggers some programs in IoX to run.
Wednesday at 09:26 PM5 days Probably the same issue, if multiple commands is issued to the same node server in a very short period (usually less than a second) the error is shown. I think this is due to a timeout, but not exactly sure. This has always existed so is not a new issue. If this happens in eisy-ui plugins (not PG3) we can investigate further, no point in fixing something that is already being replaced.
Thursday at 03:14 PM4 days 17 hours ago, Javi said:Probably the same issue, if multiple commands is issued to the same node server in a very short period (usually less than a second) the error is shown. I think this is due to a timeout, but not exactly sure. This has always existed so is not a new issue. If this happens in eisy-ui plugins (not PG3) we can investigate further, no point in fixing something that is already being replaced. It i just one command, "set armed status night".
Thursday at 03:58 PM4 days 41 minutes ago, apostolakisl said:It i just one command, "set armed status night".Filter the PG3 log for /cmd/, if there are multiple in the same second it is the same issue.On 10/6/2026 at 9:09 AM, Javi said:2026-10-06 08:26:58.082 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_28/cmd/DON....2026-10-06 08:26:58.153 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON...2026-10-06 08:26:58.234 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON
Create an account or sign in to comment