I have a new Homeseer setup with 2 Z-wave doorbells with matching events to have Homeseer say "Doorbell pressed front door" and "Doorbell pressed rear door."
This has worked in the past, but the back door has recently started saying front door. As I dig into it, the events are working properly and the log even shows the correct text to speech TTS being said. The built in speaker on the server says the correct text, but the Sonos speakers say the wrong thing.
I though this may be tied to a bug in Homeseer from copying the events when I first set them up. I deleted the events and created each from scratch and get the same result - the old doorbell announcement for both doors.
I turned on sonos pi debugging and see where it is looking for wavefiles in C:\WINDOWS\system32\html\Sonos\Announcements
Oddly, there is no html folder in system32 in my setup, but I found the files here in my homeseer installation folders:
..\HomeSeer HS3\html\Sonos\Announcements\Ann_GeneralAnnouncements_0.wav
This file is the old announcement text that I am hearing. I could try deleting all of the wav files and letting it recreate them, but this is happening with other announcements as well and I'd like to make sure I have a long term fix.
It almost looks like the Sonos PI is not fully aware of where the wav files are when it checks the TTS to replace the wav with a new one, but it is aware of where they are when it plays them.
I previously updated the Sonos PI to the Beta version and made the firewall changes to get it working again in the past.
Thank you for any help.
See below and attached files for additional info.
HomeSeer Version: HS3 Pro Edition 3.0.0.368
Operating System: Microsoft Windows 10 Pro - Work Station
IP Address: 192.168.50.164 Number of Devices: 211
Number of Events: 42
Available Threads: 200
License: Registered License: 106791
User Name and Access Level: default (Admin)
Web Server Port: 80
Enabled Plug-Ins 3.0.0.33:
Current Cost 3.0.0.14:
NetCAM 3.1.0.22:
Sonos 3.0.0.76:
weatherXML 3.0.1.130: Z-Wave
This has worked in the past, but the back door has recently started saying front door. As I dig into it, the events are working properly and the log even shows the correct text to speech TTS being said. The built in speaker on the server says the correct text, but the Sonos speakers say the wrong thing.
I though this may be tied to a bug in Homeseer from copying the events when I first set them up. I deleted the events and created each from scratch and get the same result - the old doorbell announcement for both doors.
I turned on sonos pi debugging and see where it is looking for wavefiles in C:\WINDOWS\system32\html\Sonos\Announcements
Code:
DoCheckAnnouncementQueue calling SpeakToFile with Text Doorbell Rear Door has been pressed and File C:\WINDOWS\system32\html\Sonos\Announcements\Ann_GeneralAnnouncements_0.wav
..\HomeSeer HS3\html\Sonos\Announcements\Ann_GeneralAnnouncements_0.wav
This file is the old announcement text that I am hearing. I could try deleting all of the wav files and letting it recreate them, but this is happening with other announcements as well and I'd like to make sure I have a long term fix.
It almost looks like the Sonos PI is not fully aware of where the wav files are when it checks the TTS to replace the wav with a new one, but it is aware of where they are when it plays them.
I previously updated the Sonos PI to the Beta version and made the firewall changes to get it working again in the past.
Thank you for any help.
See below and attached files for additional info.
HomeSeer Version: HS3 Pro Edition 3.0.0.368
Operating System: Microsoft Windows 10 Pro - Work Station
IP Address: 192.168.50.164 Number of Devices: 211
Number of Events: 42
Available Threads: 200
License: Registered License: 106791
User Name and Access Level: default (Admin)
Web Server Port: 80
Enabled Plug-Ins 3.0.0.33:
Current Cost 3.0.0.14:
NetCAM 3.1.0.22:
Sonos 3.0.0.76:
weatherXML 3.0.1.130: Z-Wave
Comment