bpwwer Posted February 21, 2023 Posted February 21, 2023 9 hours ago, MJsan said: @bpwwer But the nodes are there (MH sees them??) is there any correlation to this reported problem with the LIFX problem after 5.5.4? No, no correlation to the LiFX problem. I understand the frustration. The fact some of them are working is actually a good sign, it means it can work, we just need to figure out why it's not working for all of them. The node server log with debug enabled is the most important piece of information to understanding what is happening and you still haven't provided that. Without getting into to too many technical details, when PG3(x) installs a node server and the node server creates nodes, there are two main parts to this. The node server running on PG3(x) creates the node in the IoX. Updates to that node come from the node server and commands to that node go to node server. So both the node server and the IoX have an internal representation of the node. Some of the synchronization of this is managed by the node server and some by you the user. The Discover button (and the configuration) on the node server is how it determines what MH devices are out there. If it sees a new device, it creates a new node on the IoX. However, the opposite isn't true, it doesn't remove the node from the IoX if it doesn't see the device during the discovery. That's where you would have to manually remove the node to keep things in sync. That's why the IoX may show 10 device nodes, but if the node server only discovers 4 you get 4 working and 6 not working. The discovery process isn't perfect, it depends on a number of factors both in how the devices themselves are designed, how busy the network is at any given time, etc. It something like asking a group of people to say they're name to see who is there. They start talking over each other and you may only be able to catch a few of the names. That's why you can also enter the devices in a list on the configuration page. So I'll re-iterate, the node server debug log is how we determine what the node server is doing and manually configuring the devices in the node server may help. Those two things are how we move forward. 1
MJsan Posted March 11, 2023 Author Posted March 11, 2023 Hey @bpwwer and all those following ... Got back from a 2-week work trip and did a refresh (discover) and things seem to be populated with status now Did an update to 5.5.9 (and PG3x to 3.1.23) and things _still_ seem to be working. Scenes are firing as expected (which means Insteon KPLs are triggering Magichome LEDs... the whole point of this Let's see how well things keep working for a while, but apparently I'm back to running now.
Recommended Posts