I migrated Roku over to the eisy-ui and am having problems getting both of my Rokus to properly install. What happens is that if both are online they get discovered and added but one or the other will show internal server errors. Both wont install properly. I reinstalled Roku in the eisy-ui but with the same results. If I disconnect one and restart the NS the connected one will get discovered and installed properly but then if I connect the other Roku and restart that on will have the internal server error.

A similar thing is happing with Tivo. May be a discovery issue.

Thanks

Gary

Roku-log-2026-10-20T23-55-49.308Z.zip

I am seeing these system errors coming from NS2 Roku. I stopped Roku and errors stopped.

26-10-21 05:11:10 [info] Polls: Message sent to plugin (slot 2) successfully

2026-10-21 05:11:10 [info] pluginEvent: Received commands on topic udi/pg3/ns/status/plugin_2: set

2026-10-21 05:11:10 [warn] pluginEvent: Error processing API command 'set': Validation failed: 0.value: Invalid input: expected number, received NaN

Received: {

"set": [

{

"address": "2m67n",

"driver": "GV2",

"value": "native-ui",

"uom": 56,

"text": null

}

]

}

2026-10-21 05:11:10 [info] pluginEvent: Sending response to plugin plugin_2: set

2026-10-21 05:11:10 [info] pluginEvent: Message sent to plugin (slot 2) successfully

2026-10-21 05:11:10 [info] pluginEvent: Received commands on topic udi/pg3/ns/status/plugin_2: set

2026-10-21 05:11:10 [debug] pluginEvent: Processing set property request from plugin 2

2026-10-21 05:11:10 [debug] pluginEvent: Set property GV2=562859 (uom:56) for node n002_33908

2026-10-21 05:11:10 [info] pluginEvent: Sending response to plugin plugin_2: set

2026-10-21 05:11:10 [info] pluginEvent: Message sent to plugin (slot 2) successfully

2026-10-21 05:11:10 [info] pluginEvent: Received commands on topic udi/pg3/ns/status/plugin_2: set

2026-10-21 05:11:10 [debug] pluginEvent: Processing set property request from plugin 2

2026-10-21 05:11:10 [debug] pluginEvent: Set property GV1=0 (uom:25) for node n002_33908

2026-10-21 05:11:10 [info] pluginEvent: Sending response to plugin plugin_2: set

2026-10-21 05:11:10 [info] pluginEvent: Message sent to plugin (slot 2) successfully

2026-10-21 05:11:13 [debug] proxy: Proxy connection check: Successful.

2026-10-21 05:11:13 [debug] Polls: Sending short poll to plugin 10

2026-10-21 05:11:13 [info] Polls: Message sent to plugin (slot 10) successfully

2026-10-21 05:11:13 [debug] Polls: Sending short poll to plugin 7

2026-10-21 05:11:13 [info] Polls: Message sent to plugin (slot 7) successfully

2026-10-21 05:11:13 [debug] Polls: Sending short poll to plugin 8

2026-10-21 05:11:13 [info] Polls: Message sent to plugin (slot 8) successfully

2026-10-21 05:11:13 [debug] Polls: Sending short poll to plugin 5

2026-10-21 05:11:13 [info] Polls: Message sent to plugin (slot 5) successfully

2026-10-21 05:11:13 [debug] Polls: Sending long poll to plugin 1

2026-10-21 05:11:13 [info] Polls: Message sent to plugin (slot 1) successfully

2026-10-21 05:11:15 [debug] Polls: Sending short poll to plugin 2

2026-10-21 05:11:15 [info] Polls: Message sent to plugin (slot 2) successfully

2026-10-21 05:11:15 [info] pluginEvent: Received commands on topic udi/pg3/ns/status/plugin_2: set

2026-10-21 05:11:15 [warn] pluginEvent: Error processing API command 'set': Validation failed: 0.value: Invalid input: expected number, received NaN

Received: {

"set": [

{

"address": "2m67n",

"driver": "GV2",

"value": "native-ui",

"uom": 56,

"text": null

}

]

I just tried the Roku NS today and it can now discover and load both Rokus correctly. All seems to work now.

Thanks

Gary

The issue of an internal server error turned up on one of the Rokus but can still function from a program. The control buttons are no longer present on the one with the error.

I just updated to the latest software and still can't get my two Rokus to load properly One or the other will show an internal server error on the node.

From the log, there seems to be a couple of different things going on. But it doesn't seem like those would be unique to running in the new internal plugins on eisy-ui.

Have you migrated back to PG3 and is everything working fine there? That's usually the first test, if it works fine in PG3 but not after migration, it's something UDI will need to look into.

The two things I see in the log are:

1. it looks like the discovery process is returning a list with the first item being an invalid/null device which may just mean something else on your network is responding to the discovery broadcast. It throws an error for that, but that's what it should do when a non-Roku device responds.

2. the errors around 'native-ui' appear to be related to some recent firmware change on the Roku. Maybe they renamed something or added something. I'll need to look into this more.

Neither of these look like they are breaking anything. From your log, both Rokus are being discovered and the nodes created for them. The "internal server error" sounds like it may be coming from eisy-ui and possibly could be related to the native-ui errors or may just be a bug in eisy-ui.

I installed the plug both on both internal and PG3 with eisy-ui.

On PG3, it is working correctly

On internal, one of the nodes is giving the internal server error and it coming from eisy-ui:

2026-10-23 09:47:05 [debug] web: HTTP Request from ::ffff:192.168.92.100 - GET /api/groups/nodeRoles/n023_29806
2026-10-23 09:47:05 [error] web: Error processing /groups/nodeRoles/n023_29806: NodeDef roku_44 not found in family 10 instance 23
2026-10-23 09:47:05 [debug] web: HTTP Request from ::ffff:192.168.92.100 - GET /api/profile/node/n023_29806/cmds/accepts
2026-10-23 09:47:05 [http] web: GET /api/groups/nodeRoles/n023_29806 : 200 : 4ms 
2026-10-23 09:47:05 [error] web: Error processing /profile/node/n023_29806/cmds/accepts: NodeDef roku_44 not found in family 10 instance 23
2026-10-23 09:47:05 [http] web: GET /api/profile/node/n023_29806/cmds/accepts : 200 : 2ms 

However, looking at the nodedef files, roku_44 and roku_45 are both there. So some type of bug in eisy-ui.