Closed pzim-devdata closed 2 years ago
That smells like a bug in zp
. I haven’t tried zo join
for a long time, and messed with the initialisation order several times to address issues in Homebridge ZP. I need to do some testing this weekend to analyse what went wrong.
That smells like a bug in
zp
. I haven’t triedzo join
for a long time, and messed with the initialisation order several times to address issues in Homebridge ZP. I need to do some testing this weekend to analyse what went wrong.
Thanks ;-)
That was simple, just call initTopology()
. Also fixed some debug messages while at it.
In v1.4.9.
Thank you for your answer.
It's working perfectly with the update to v1.4.9.
The command line to join is : zp -H 192.168.1.128 join "Salle à manger"
with the zoneGroupName
or the zoneDisplayName
at the end and not the zone
.
For instance zp -H 192.168.1.107 join RINCON_542A1B452AEC01400
dosesn't work.
Thank you ;-)
I don’t know the RINCON numbers of my zone players by heart, so It makes more sense to me to use the zone name, instead of the zone player ID. I did consider using the hostname or IP address (to be consistent with the -H
flag), but that would be more complex technically and I never implemented that.
Yes you're right. It's perfect like this. I meant in zp help when we execute zp -h
, the join
line should be join [-h] zoneGroupName
or join [-h] zoneDisplayName
and not join [-h] zone
Thank you for your help ;-)
Issue
Hello,
Thank you so much for your homebridge plugin.
I have a problem when I want to group my Sonos Roam and my Sonos One to play together. When I use this command line to join :
zp -H 192.168.1.107 join RINCON_542A1B452AEC01400
I have the following error message :Could you help me please ?
Log Messages
Here is the result of
zp -H 192.168.1.107 topology
:Debug Files