Yes. Read above, post 54. Select one at a time and be quick!
1 Like
Haha! Chrome wasn’t working with this but I moved over to Edge and it’s working ok now.
2 Likes
I finally got around to adding a Hitachi W50 speaker, The connect app discovered it immediately and created the device without issue. Unfortunately, I can't figure out how to get TTS working. Whether sending a message from the device page or from a RM trigger, I always get the response, "You've selected the text to speech function but did not enter a message."
I am hoping someone here knows if I'm missing a setting in the driver or not using some special formatting. I've been playing with this for so long today, I'm actually starting to like the default Smooth Jazz channel.
I'd also like to thank @veeceeoh and @Matthew for getting this working, and @max.leung for discovering the final bit I needed to connect.
2 Likes
When I use my Fabriq speakers from the device page, I think I used the Speak field and button.
Thanks. I've tried most of the input boxes and buttons on the device page and still get the audio message telling me I've not entered a message. I guess I'll just put this one aside and come back to it later. I tend to screw things up when I get frustrated.
the rest of us just breeze through stuff when we are frustrated 
1 Like
Anyone else having problems with the DLNAPlayer driver?
My hub has been freezing up. The support guys tell me it's:
suffocated by LAN errors. There is one that fires continuously "Unknown - HubAction: delay".
That HubAction shows up in only one place in my system. DLNAPlayer.
I was seeing the same thing too. Removed it and now everything is OK again.
You could try to comment out this section of code:
private delayAction(long time) {
new hubitat.device.HubAction("delay $time")
}
or as I just did, comment out all calls to delayAction().
It is around line 960. I have no idea if that has any other repercussions or impacts, but that is where 'hubaction' 'delay' is happening in the driver. I looked through the code and many of the places that call this delayAction() routine are already commented out. I just comment out the remaining ones. I cannot see if the speakers still work until I get home this evening.
Is there a way you can see the LAN errors? I don't see anything in my Hubitat logs?
[UPDATED:] @doug My speakers seemed to unaffected by this change (they all still worked just like before). I am interested if you can determine if the LAN traffic has decreased because of this change?
I have indeed commented it. Will see how that goes over time.
No I don’t see that in live logs. Support sees it in the backend logs.
Thanks
1 Like
I can tell you that yes, the lan traffic decreased. Unfortunately I also have to tell you that my hub still crashed last night. So clearly the incoming requests from the 3 speakers was not the problem.
In fact it seems to crash at the very same time every early morning. Within minutes of 2:10a each time. I'm still working with support to determine why.
Is there anywhere to preset the volume when sending to speaker? I'm using bigtalker with it and thought there was this option on ST but can't find on the HE versions.
Anyone have any ideas about the above?
If you use RM this allows it.
1 Like
Ah well done i missed that one been using speech device and you don't get that option.
Cheers
1 Like
This is exactly what I was looking for! I managed to load up the Custom App and Device Drivers into Hubitat and within a minute or two it discovered my D-Link M-225 Audio Render. I'm using it to drive a dumb speaker as a simple TTS device. My ONLY issue is when I send text to it, it delivers the message than then attempts to repeat the first word for just a split second. So i get: "Welcome Home Mark.....Wel". I've tried putting some spaces and commas in the text string in hope to avoid it looping back around but it doesn't seem to make any difference. Any idea what could be causing this?
I tried to capture some audio example off my phone....note volume is really LOW.
Sorry. I have no clues. I stopped using this driver when I setup the Echo Speaks app. I never experienced what you are describing and I have no clues as to what to look for to correct that. I did not create that driver, I just worked, with others, to port it over to Hubitat.
Good luck! Wish I could have been of more help.
Did anyone have any luck with Hitachi Speaker working? I can use the speaker and get the volume to go up but no speech is coming out? I know that volume is going up as i was listening to a song and when I trigger the speaker volume came up but no speech? Any ideas thanks
I used a Hitachi speaker for a while with the DNLA/Media Renderer app and driver. Originally it wouldn't speak with the built-in TTS and I has to use an external TTS service. @cybrmage tracked down the issues and I had native TTS working before I decided to stop using the speaker. Here's a link to the post detailing the changes and a link to his code.
DLNA Player and Media Render warning message
Good luck!
