v3.1.2 renaming of nodes based on configuration

ISY nodes to be renamed based on config / YAML / JSON changes
- rename will happen upon restart or Discover
- rename will not happen to default named nodes, where no name was given in the config,  so as not to wipe out user renamed nodes in ISY
 

Feedback is welcome, let me know if you have new ideas or devices you would like on the list.

I next plan on adding the Garage device, which was my original reason for asking permission to take on this plugin.

On 5/13/2024 at 2:24 PM, sjenkins said:

v3.1.2 renaming of nodes based on configuration

ISY nodes to be renamed based on config / YAML / JSON changes
- rename will happen upon restart or Discover
- rename will not happen to default named nodes, where no name was given in the config,  so as not to wipe out user renamed nodes in ISY
 

Feedback is welcome, let me know if you have new ideas or devices you would like on the list.

I next plan on adding the Garage device, which was my original reason for asking permission to take on this plugin.

@sjenkins I used the JSON method to create test devices.  It worked but why were some devices created at different levels in device tree?

Key Value

101  {"id": "101", "type": "switch", "name": "Front Porch Switch"}
102  {"id": "102", "type": "switch", "name": "Back Porch Switch"}
201  {"id": "201", "type": "dimmer", "name": "Patio Dimmer"}
202  {"id": "202", "type": "dimmer", "name": "Driveway Dimmer"}
301  {"id": "301", "type": "temperature", "name": "Outside Temp"}
302  {"id": "302", "type": "temperature", "name": "Inside Temp"}

2 hours ago, hart2hart said:

@sjenkins I used the JSON method to create test devices.  It worked but why were some devices created at different levels in device tree?

Key Value

101  {"id": "101", "type": "switch", "name": "Front Porch Switch"}
102  {"id": "102", "type": "switch", "name": "Back Porch Switch"}
201  {"id": "201", "type": "dimmer", "name": "Patio Dimmer"}
202  {"id": "202", "type": "dimmer", "name": "Driveway Dimmer"}
301  {"id": "301", "type": "temperature", "name": "Outside Temp"}
302  {"id": "302", "type": "temperature", "name": "Inside Temp"}

That happens the odd time with many plugins besides this in my experience.  Nothing to do with the config method. 
hit right mouse and “group nodes” to fix. 
Perhaps @bmercier knows why that happens and if I can do something to fix. 

Edited May 19, 20241 yr by sjenkins

5 hours ago, sjenkins said:

That happens the odd time with many plugins besides this in my experience.  Nothing to do with the config method. 
hit right mouse and “group nodes” to fix. 
Perhaps @bmercier knows why that happens and if I can do something to fix. 

If you can reproduce the problem, look at the PG3 log. Look for this right after a node is created:

• "Group command sent..." or
• "Group command not sent..."

An error code might give a clue. Or, PG3 may see a success where it is no. Either way, that would be useful to know to troubleshoot further.

 

23 hours ago, sjenkins said:

That happens the odd time with many plugins besides this in my experience.  Nothing to do with the config method. 
hit right mouse and “group nodes” to fix. 
Perhaps @bmercier knows why that happens and if I can do something to fix. 

I pulled it up again today and they are grouped together.

20 hours ago, bmercier said:

If you can reproduce the problem, look at the PG3 log. Look for this right after a node is created:

• "Group command sent..." or
• "Group command not sent..."

An error code might give a clue. Or, PG3 may see a success where it is no. Either way, that would be useful to know to troubleshoot further.

 

@bmercier thanks for the hints, I see this enough I will see if I can track it down myself. Not a big deal as you can force the grouping. I usually see it when a number of nodes are added quickly.