The speaker client is built into the HS 3 full download so you can either try doing a repair or reinstall HS3.
Announcement
Collapse
No announcement yet.
Speaker client VR, all of a sudden stop working?
Collapse
X
-
Aren't there specific IP ports used? Could this have gotten changed causing connection issue? Soumds like ur OS is fine.HSPro: 3.0.0.194
PL: Insteon PLM 3.0.5.20,Insteon Thermostat 3.0.1.1 , UltraM1G, RainRelay8, UltraECM3, UltraPioneerAVR3, BLBackup, weatherXML, Jon00 Network & PC Monitor
HW : Win 7 64bit, Intel i7-2600, 16 GB DDR3 Ram, 60 Plus Insteon Dual Band Devices, Rain8 Pro2, Elk M1 Gold, Brueltech GreenEye.
Comment
-
Where can i get just the speaker client application to see if it the cliente?- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Odd puzzle here. Checking Hector's VR stuff last night via remote control.
It is pointing more towards a software rather than a hardware issue:
1 - Basic SAPI TTS/VR functions work fine via the Wintel control panel
2 - SAPI TTS works fine via Homeseer 3
3 - SAPI VR is very intermittent via Homeseer 3. It did work twice last night.
Doesn't make sense to me. If it was a hardware issue then the basics wouldn't work.
Downgrading HS3 versions did not fix the VR issues.
Its almost as if the VR recognition tweaking and configuration has been shut off?
Geez even shutting off HS3 and enabling HS2 VR stuff didn't work.
I do not see that any of the microphone levels are being turned down by HS3 / HS2.
Anyone ever have a similiar issue?- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Can you roll back to a earlier restore point or OS snap shot?HSPro: 3.0.0.194
PL: Insteon PLM 3.0.5.20,Insteon Thermostat 3.0.1.1 , UltraM1G, RainRelay8, UltraECM3, UltraPioneerAVR3, BLBackup, weatherXML, Jon00 Network & PC Monitor
HW : Win 7 64bit, Intel i7-2600, 16 GB DDR3 Ram, 60 Plus Insteon Dual Band Devices, Rain8 Pro2, Elk M1 Gold, Brueltech GreenEye.
Comment
-
I was running Speaker Client 3.0.0.2 on W7 and HS3 3.0.0.96 on separate PC with W7 and everything was fine.
After upgrading to Clinet 3.0.0.3 and HS3 3.0.0.152, my speaker clients can't connect to the server anymore. (I don't know when it was happening as I did not use it for a while)
Have tried changing the ports, no use.
The Speaker Client starts fine on the server but claims that its connecting even if I give it any port number..
Have no Speaker or mic on the server to test its function.
Anyone have 3.0.0.3 running on separat PC towards HS3 3.0.0.152 and can confirm its working?
Comment
-
Originally posted by fermate View PostI was running Speaker Client 3.0.0.2 on W7 and HS3 3.0.0.96 on separate PC with W7 and everything was fine.
After upgrading to Clinet 3.0.0.3 and HS3 3.0.0.152, my speaker clients can't connect to the server anymore. (I don't know when it was happening as I did not use it for a while)
Have tried changing the ports, no use.
The Speaker Client starts fine on the server but claims that its connecting even if I give it any port number..
Have no Speaker or mic on the server to test its function.
Anyone have 3.0.0.3 running on separat PC towards HS3 3.0.0.152 and can confirm its working?Hector
____________________________________
Win.2003 OS, HS3
BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
MyTrigger,ACRF2,W800,Zwave
AP800,Honeywell Stat
Comment
-
Originally posted by fermate View PostNo, I cant even Connect anymore.
Can you Connect?
Can you make it speak?Hector
____________________________________
Win.2003 OS, HS3
BLDSC,BLstat,BLRadar,BLRamdom,BLOccupied
BLups,BLrain8,HSTouch,Ultrajones Weatherbug,
MyTrigger,ACRF2,W800,Zwave
AP800,Honeywell Stat
Comment
-
Originally posted by fermate View PostBut I can't even Connect so "Mute" or "Stop listen" is of no use.
What port are you using?
Post a screen shot of your speaker client setting and maybe we can spot something. The port should be 10401
Comment
-
Here when looking there (Hector's setup) the control panel SAPI applet, TTS and VR functions were fine a couple of days ago. Initially validated these functions.
It was only the VR that did not work with the speaker dot exe application. All settings and configurations were correct. No changes in microphone or speaker levels were seen when running speaker dot exe. Homeseer logging showed the connection just fine along with the speaker dot exe logging.
It was as if the function had been shut off.
Tise has caused a debaucle as Hector was utilizing TTS / VR much for his Homeseer 3 activities relating to events et al.
IE: his Homeseer 3 automation is currently disfunctional.
NO OS changes, no new plugins, no new applications were added or updated other than Homeseer 3 on Hectors Windows 2003 32 bit server.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Originally posted by Rupp View PostIt's working fine here. Is your windows firewall blocking the speaker app from connecting?
Post a screen shot of your speaker client setting and maybe we can spot something. The port should be 10401
I must have mixed up the verions, sorry.
Comment
-
Originally posted by Pete View PostHere when looking there (Hector's setup) the control panel SAPI applet, TTS and VR functions were fine a couple of days ago. Initially validated these functions.
It was only the VR that did not work with the speaker dot exe application. All settings and configurations were correct. No changes in microphone or speaker levels were seen when running speaker dot exe. Homeseer logging showed the connection just fine along with the speaker dot exe logging.
It was as if the function had been shut off.
Tise has caused a debaucle as Hector was utilizing TTS / VR much for his Homeseer 3 activities relating to events et al.
IE: his Homeseer 3 automation is currently disfunctional.
NO OS changes, no new plugins, no new applications were added or updated other than Homeseer 3 on Hectors Windows 2003 32 bit server.
Comment
Comment