Cast groups changing "elected leader"

[freol35241]

Hi,
I'm having some trouble with the chromecast audio group functionality in pychromecast, it seems like the cast group every now and then changes the "elected leader" of the group (and thereby the ip-adress of the group) but remains on the same port-number. Below is a log from HomeAssistant discovery showing the behaviour.

The first three lines shows the discovery of 3 "real" chromecast audio devices. Line 4 shows the discovery of a cast group on ip=192.168.0.205 and port 42675. Line 5 and 6 shows that after some (random?) time, the ip of the group changes (new device is discovered) but the port number stays the same. A Chromecast object associated with the first ip of the group will now return an error (see bottom) and a new Chromecast object (with the new ip) has to be created in order to connect.

Chromcast objects with "dynamic ip", is that possible? Maybe in line with the approach brought up in #111 ?

17-03-12 12:55:46 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.100', 8009)

17-03-12 12:55:46 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.104', 8009)

17-03-12 12:55:46 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.205', 8009)

17-03-12 12:55:46 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.205', 42675)

17-03-12 13:28:29 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.100', 42675)

17-03-12 15:17:08 INFO (MainThread) [homeassistant.components.discovery] Found new service: google_cast ('192.168.0.104', 42675)

Error in homeassistant after ip of group has changed:
File "/home/hass/.homeassistant/deps/pychromecast/socket_client.py", line 589, in send_message raise NotConnected("Chromecast is connecting...")