GTench

@xlurkrI am using 4 speaker hubs with one yolink hub and one node server. They are scattered throughout the house on different floors. They announce for things like packages at front door, back shed door open, gate open etc. I believe  that I leave a few seconds delay between sending the same message to each speaker hub but not sure if this is necessary (just a precaution to prevent confusion - like 2 people speaking at the same time). I only wish the node server could allow for more than 9 possible messages. @Panda88any chance for this; does the local hub allow for more than 9?
Gary

I tried that twice from the AC with no luck. I just resorted to power cycling the eisy and that worked.
thanks... back to testing

Yes, it looks to me like the phone app is the main source (and that makes sense to me too) but the name change is just not being picked up by the nodes unless  adding a new (or missing) node. Now that I realize how this is working, I don't mind deleting the node and restarting the node server to have the new name picked up; so, don't worry about changing anything for me. Changing names is something that is quite easy to do this way and is something that would only happen very infrequently for me.
If I want to use a node name different than in the app, I could just change it in the AC (overriding the PG3) and I have done this with other node servers. In this case though, I want the app name and the AC name to be the same for consistency and since the AC gets its names from the nodes, I wanted the app and node names to match
Yolink is working great for me. I really appreciate all the work that you have put into it
Gary

I thought maybe PG3x 3.1.24 corrected the node server reinstall problem but I guess not. A delete and reinstall did work

Forget it. Looks like it just took some time. Works now