ChromecastDevice, here’s the config of the Mini device.
{
"class": "Chromecast",
"name": "Chromecast Diele",
"ip": "192.168.178.31",
"id": "chromecast-diele"
},
New plugin pimatic-sounds
ChromecastDevice, here’s the config of the Mini device.
{
"class": "Chromecast",
"name": "Chromecast Diele",
"ip": "192.168.178.31",
"id": "chromecast-diele"
},
As far as i know pimatic-chromecast and pimatic-sounds-basic use the same approach for casting to chromecast devices. I did some refactoring some of the code for pimatic-sounds towards assistant-relay and catt. That could cause the delay.
Did you use pimatic-sounds or pimatic-sounds-basic?
I use pimatc-sounds, not pimatic-sounds-basic. I will try with pimatic-sound-basic and report back, if this changes anything
Could you please explain to me, what the differences between these two plugins are?
Test successful. With pimatic-sounds-basic the Mini reacts as quickly as pimatic-chromecast. Thanks for the hint @bertreb!
Pimatic-sounds-basic is a frozen version (0.1.23) of pimatic-sounds. It uses a chromecast solution for casting and not catt.
I’m using pimatic-sounds to develop some features like support of google assistant. You can send text commands like you would talk to a google device.
For example. Now iffft stopped interfacing with Google/Nest, I use a text command to set the temperature in a rule.
@bertreb said in New plugin pimatic-sounds:
Hi, I changed it to display the announcement text -> version 0.1.23
Unfortunately it does not work. During init sound “init sounds” ist shown, but when I sent a text still “Pimatic Announcement” is shown.
You are faster fixing problems, than I am able to debug…
With 0.1.24 it look good! Thanks!
One question regarding play ask...
this is built to work with assistent relay, right?
Its really a pity, that I am not able to disable the IPv6 in my Fritzbox what cause the problem, that AR is not working for me… I will try in the next day to get it running…