Hi, Dave @djgutheinz
I have had your integration of the Samsung speakers (R1) for a couple of years and it was my most reliable Hubitat speaking device. But it seems to have dropped off and I can't figure out what's wrong. Now on 3.3.6/3.3.8. Here are some logs. If you have a moment, would you look to see what I'm doing wrong?
Check to see if you can control it from the Samsung Multiroom App. The messages indicates that something has changed. Maybe IP address or something else in your router setup.
If it continues, uninstall and then install is the only current option.
Thanks, Dave. Much appreciated.
The Multiroom app does see this speaker. But I think your tip about the IP address is on the right path. It looks like my static assignment in the router had dropped off and it was getting a random dynamic IP. I don't see a way in the app or driver to change the IP of an installed speaker. Is this possible? I'd prefer not to uninstall everything because I have about 20 rules that reference this device. Thanks again!
I added the 7 lines of code to allow resetting the IP address in preferences. This is a "test" release and the changes will be incorporated in the next formal version. (I am currently using this test version.)
location: https://raw.githubusercontent.com/DaveGut/Test-Code/master/Samsung_Wifi_Speaker_378T.groovy
Instructions: Install code, Open Driver, Add new IP address, Save Preferences Test.
Dave
Excellent. Thank you.
It definitely changed the IP because i can see it in the driver and testing from RM and the driver works. Since it works, it may be just a curiosity, but commands from the driver also generate errors in the log:
Top error. Hubitat has changed the Speak specification and I need will have to update to take the newer parameters.
lower error. Not sure at this time
Warn. Your speaker did not accept the audio format that was generate by the Hubitat TTS command (with uri generated by Amazon)? They used to accept this; however, over the years, things change. Try play text and resume again and tell me if it occurs again. If so, I will provide access to the VoicesRSS codex that works (code is already there for the soundbar).
I did a test "Play text and Resume" and it spoke perfectly but threw the errors. As long as it's working, I'm good. But if this is helpful to you, I am happy to do any further testing. Thanks!
I have to rework the entire driver set. This is on the list.
Dave
Can also confirm that recent releases gave me trouble for close to a year. Basically every day or two I would either need to hit Save Preferences in the device to clear out its queue (sometimes Clear queue would work), restart the Hubitat, or occasionally restart the R1 itself in order to get it talking again.
I downgraded from v3.3.8 on Driver and v3.3.6 on App to v3.3.4 for both a couple weeks back and it's been way more reliable, I've only had to restart the device itself once, and the queue hasn't been getting backed up all the time like it was.
Not sure what has changed, I can try to get you logs if it matters, but it sounds like you're planning on reworking it, just wanted to confirm a similar experience on my end.
Updating this weekend to address:
Testing will be on an R1 and MS360 soundbar. No group testing (I no longer user the R1's)
TEST Version Available
I wan to test this version before publishing in HPM. It should address recent issues. ( @Ecksters, @CAL.hub)
Test Driver Load Procedure:
Recover to current driver version:
There is no need to do a clearQueue or commands other than speak in a rule to cause the system to operate properly. Doing these command can actually have an adverse impact on command timing.
So I've got all my automations using playTextAndRestore because I want to be able to set the volume to 100 and return to the audio that was previously playing automatically, does Speak do that?
Yes. Speak has input parameters if text, volume, and voice. After running, my code returns the speaker to the volume before receiving the command and resumes the player. Voice and Volume are optional.
For volume, the command is speak(text, volume).
Thanks, Dave. I upgraded and tested basic functionality. So far, so good. Will advise.
@djgutheinz since it has been 2 weeks since last update am I to assume all is working and you are going to be putting the update in HPM?
Next week, hopefully.
VERSION 4.0 now available. See top of thread for release information. You will need to do a save preferences after updating driver.
I love your app and have been using for a couple of years. However since the upgrade it has stopped working. I have saved preferences. Any suggestions appreciated.
First thought is to check the data value "deviceIP" in the devices page "Data" section versus the IP address in your router. If not the same, run the application again (It will attempt to update the IP address). Final solution is to reinstall.
PS: Make sure that the Speaker has a static IP address assigned in your router (see the instructions).
Thanks for the quick response. I tried everything including full reinstall. It finds the Speaker but the IP’s continue to be different (speaker and router) Any help is appreciated.
Download the Hubitat app
