New plugin pimatic-sounds
0.0.27 testing:
Id when discovering is now the real id, so no issues there anymore.
Everything else seems to be working fine now except the status updates:
It updates when something starts streaming but it doesn’t go back to idle when a stream is stopped.
In the screenshot the above group is playing, the second group was stopped.
Hi thanks for the feedback.
I will check the status and info. The intended design is:
Status field: idle, playing or announcement
Info field:
idle: empty
playing: title of song
announcement: the text or the filename
I will check an update this part.
The first approach on automated update of devices will be also part of next release, but i can do only do basic testing. So without guarantees for you and others to test.
Auto updating is only necessary when you change a group or delete and create as new with the same name in Google home isn’t it?
I would think once you have the groups sorted in a house it will stay that way unless you decide to replace a few devices?
Yes, thats is also my assumption.
I will do a discovery on startup of the Plugin (Pimatic), because thats a good moment to sync. But once live the discover needs to be triggered manually in the Gui of Pimatic.
Wild night last night on pimatic, log was filled with a lot of warnings, this is just a small part of it. I was asleep the whole night while these warnings occurred:
Showing 67 of 67 Messages
2020-02-21 07:55:03info [pimatic,ppm]: 2.15.12
07:19:33info [pimatic-telegram]: [Message] Sending Telegram “Hondenluik is geopend” to dj MvT: success
04:59:35info [pimatic]: Device discovered: pimatic-sounds: Google Home Mini - Slaapkamer
04:59:35info [pimatic]: Device discovered: pimatic-sounds: Google Home Mini - Slaapkamer
04:59:35info [pimatic]: Device discovered: pimatic-sounds: Google Home Mini - Slaapkamer
04:20:11error [pimatic-sounds]: Error in playing announcement: Error: Load cancelled
04:20:10info [pimatic-sounds]: PlayAnnouncement device connected
04:20:10info [pimatic-sounds]: Device connected
04:20:10info [pimatic-sounds]: PlayAnnouncement device connected
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic-sounds]: Device already in config
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Home - Woonkamer Links
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Home - Woonkamer Links
04:19:56info [pimatic]: Device discovered: pimatic-sounds: Google Home - Woonkamer Links
04:19:06info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:06info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:06info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
04:19:06info [pimatic-sounds]: Device already in config
04:19:06info [pimatic-sounds]: Device already in config
04:19:06info [pimatic-sounds]: Device already in config
Keeping Pimatic busy at night 
Are your Google Home’s and Mini shutting down (sleep mode) when nobody is in the room?
Because the discovery retries discovering when an error occurs, I will make it fully manual, to prevent this type of erors.
@bertreb said in New plugin pimatic-sounds:
Are your Google Home’s and Mini shutting down (sleep mode) when nobody is in the room?
They shouldn’t do that I guess?
What I’ve seen (and heard from others) the Google devices reset a lot lately at night. Maybe some software updates from Google? No idea what’s causing it, didn’t notice until this plugin though because the plugin tells it when something is happening 😂.
Yes, thats to choose between two scenarios
And these kind of errors are without a warning so you don’t know what it is.
It will compromise on a 10 minutes reconnect test timer
I published a version 0.0.28 of Sounds.
Some changes in this version;
First many thx for you big effort. Unfortunately with this version (maybe from 0.0.27, I came from 0.0.26) the group device is not more playing. As a workaround I changed to speake group created in the home assistent app. My feeling is that the “GroupDevice” (pimatic) is a little bit faster.
0.0.28 test:
so far no issues, I’m not using the groupsdevice so didn’t test that. Status and info works as far as I can see now 
@ortin said in New plugin pimatic-sounds:
First many thx for you big effort. Unfortunately with this version (maybe from 0.0.27, I came from 0.0.26) the group device is not more playing. As a workaround I changed to speake group created in the home assistent app. My feeling is that the “GroupDevice” (pimatic) is a little bit faster.
I fixed the GroupDevice in release 0.0.29
0.0.29 is working absolutely fine but the log gets flooded with info messages coming from the auto discovery. Is that necessary?
Log berichten
Showing 100 of 199 Messages
2020-02-23 04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
04:57:07info [pimatic]: Device discovered: pimatic-sounds: Chromecast - Chromecast Woonkamer
03:49:11info [pimatic-sounds]: Device connected
03:49:11info [pimatic-sounds]: Device connected
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic]: Device discovered: pimatic-sounds: Google Cast Group - Speakers Beneden
03:47:49info [pimatic-sounds]: Device already in config
03:47:49info [pimatic-sounds]: device ‘Alle speakers’ already in config
03:47:49info [pimatic-sounds]: Device already in config
03:47:49info [pimatic-sounds]: device ‘Alle speakers’ already in config
03:47:49info [pimatic-sounds]: Device already in config
And so on…
@bertreb said in New plugin pimatic-sounds:
play vol [0-100] on mychromecast
This seems not be possible, Am I right? I have never used it before so I don’t know if this feature was lost on the way to 0.0.30.
One thing I forgot this pops up after announcement:
)