Hi, I was using the driver successfully with a Sony Bravia X90J 75", but after about a week of use, it just stopped responding. I’ve tried restarting the TV, turning off and back on all the settings, restarting the HUB, re-enrolling and re-installing the driver, and re-adding the TV, however it doesn’t even show up in the discovery anymore. Any ideas?
I’m pushing out an update that will hopefully help with discovery and disconnects.
I had to remove this integration from my own setup last month due to the memory constraints of the v3 hub, so I’m not currently planning any significant improvements to the driver going forward and will have limited ability to help users troubleshoot.
5 Likes
Highly appreciate this
Praying this solves my connection/discovery woes
Wow !! great news !!
Can you please update regarding this new version ?
I have seen a few people also post in here that they ran through the install steps and ST just didn’t see a new device. I am having the same issue. Using the cli to look at logs I see stuff happening with the edge driver, but it never adds a device. Any thoughts would be greatly appreciated as I really want this functionality for my Sony A80J.
Running this:
smartthings edge:drivers:logcat --hub-address=192.168.0.211
Displays the following:
? Select a driver. 3
connecting… connected
2023-02-17T03:07:59.427069236+00:00 TRACE Sony Bravia TV Setup driver sony-tv with lifecycle handlers:
DeviceLifecycleDispatcher: sony-tv
default_handlers:
infoChanged:
init:
driverSwitched:
removed:
child_dispatchers:
2023-02-17T03:07:59.438502903+00:00 TRACE Sony Bravia TV Setup driver sony-tv with Capability handlers:
CapabilityCommandDispatcher: sony-tv
default_handlers:
mediaPresets:
playPreset
switch:
on
off
platinummassive43262.tvChannel:
channelDown
setTvChannel
channelUp
platinummassive43262.sonyIrccCommand:
sendCommand
audioVolume:
volumeUp
setVolume
volumeDown
platinummassive43262.pictureMute:
unmute
setMute
mute
refresh:
refresh
audioMute:
unmute
setMute
mute
platinummassive43262.sonyInputSource:
setInputSource
platinummassive43262.homeButton:
home
child_dispatchers:
2023-02-17T03:07:59.473918569+00:00 TRACE Sony Bravia TV Received event with handler environment_info
2023-02-17T03:07:59.474810903+00:00 TRACE Sony Bravia TV Received event with handler environment_info
2023-02-17T03:07:59.476244903+00:00 DEBUG Sony Bravia TV Z-Wave hub node ID environment changed.
2023-02-17T03:07:59.480446236+00:00 TRACE Sony Bravia TV Received event with handler discovery
2023-02-17T03:07:59.554633903+00:00 INFO Sony Bravia TV ===== SCANNING NETWORK…
2023-02-17T03:08:04.601005905+00:00 INFO Sony Bravia TV ===== SCAN COMPLETE!
2023-02-17T03:08:04.620248905+00:00 DEBUG Sony Bravia TV discovery device thread event handled
2023-02-17T03:09:28.065064612+00:00 TRACE Sony Bravia TV Received event with handler discovery
2023-02-17T03:09:28.066387612+00:00 TRACE Sony Bravia TV Received event with handler driver_lifecycle
My Sony TV has been showing as offline in ST with this driver recently. I resorted to deleting the device and scanning again. Nothing comes up. Seems I have lost connection permanently 
My Sony TV has been operating normally in ST with this driver.
Probably the offline problem is related to something other than this driver.
Hello,
My 2 tv’s stops responding to st integration.
Does someone has this issue too?
My Sony TV is operating normally in ST with this driver.
1 Like
Same here no respond,
My TV firmware updated a month ago, maybe this is related
My TV also stopped responding to commands about a week ago.
Hi Phil, my TV (Sony KD-65AF9) also stopped responding to commands about a few days ago, and now (no settings changed), when I scan nerby, it’s impossible to find it out.
Can you kindly help? Thanks a lot!
Is it possible that you have received firmware update to TV and you have to set TV settings again
I am having the same issue and all settings are as suggested.
1 Like
All the settings are the same as before.
It simply stopped workimg, so I deleted the TV and tried a new search, but nothing found…
It’s a pity, the driver always worked well until this happened…
Checked yesterday, everything is back normal. I can control my Sony TV via ST.
1 Like
I followed directions and got it to work yesterday.
Then this morning, it disappeared from the SmartThings app. I had to re-discover the TV.
Will see if it disappears again.
I had problems with my router over the weekend.
This issue was also seen in Sony Bravia’s operation with SmartThings.
I researched problems using smartthings edge:drivers:logcat
I noticed the following error messages in the controller log.
2023-07-16T16:17:22.498986746+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx POLLING TO KEEP CONNECTION ALIVE
2023-07-16T16:17:22.510488079+00:00 TRACE Sony Bravia TV TX > *SECHNN################
2023-07-16T16:17:22.518619412+00:00 TRACE Sony Bravia TV TX > *SEVOLU################
2023-07-16T16:17:22.526385079+00:00 TRACE Sony Bravia TV TX > *SEPOWR################
2023-07-16T16:17:22.534104079+00:00 TRACE Sony Bravia TV TX > *SEAMUT################
2023-07-16T16:17:22.541862412+00:00 TRACE Sony Bravia TV TX > *SEPMUT################
2023-07-16T16:17:22.549606412+00:00 TRACE Sony Bravia TV TX > *SEINPT################
2023-07-16T16:17:22.563111412+00:00 INFO Sony Bravia TV <Device: zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz (Sony Bravia KD-43XH8596)> emitting event: {"capability_id":"platinummassive43262.sonyInputSource","attribute_id":"supportedInputSources","visibility":{"displayed":false},"state":{"value":["TV","HDMI1","HDMI2","HDMI3","HDMI4"]},"component_id":"main"}
2023-07-16T16:17:22.610923412+00:00 DEBUG Sony Bravia TV Sony Bravia KD-43XH8596 device thread event handled
2023-07-16T16:17:22.630994412+00:00 DEBUG Sony Bravia TV Sony Bravia KD-43XH8596 device thread event handled
2023-07-16T16:17:22.824635079+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT00000001.0000000
2023-07-16T16:17:22.911390412+00:00 WARN Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx handler on driver thread encountered error: [string "st/capabilities/init.lua"]:226: Invalid value for Sony Input Source.inputSource value: {value=1.0} error: Given number for value. Required type is a string
2023-07-16T16:17:23.034410746+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT0000000000000014
2023-07-16T16:17:23.038755746+00:00 WARN Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx handler on driver thread encountered error: [string "st/capabilities/init.lua"]:226: Invalid value for Sony Input Source.inputSource value: {value=14} error: Given number for value. Required type is a string
2023-07-16T16:17:23.248560079+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT0000000000000001
2023-07-16T16:17:23.263406413+00:00 WARN Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx handler on driver thread encountered error: [string "st/capabilities/init.lua"]:226: Invalid value for Sony Input Source.inputSource value: {value=1} error: Given number for value. Required type is a string
2023-07-16T16:17:23.377703079+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT0000000000000000
2023-07-16T16:17:23.378672079+00:00 INFO Sony Bravia TV <Device: zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz (Sony Bravia KD-43XH8596)> emitting event: {"capability_id":"platinummassive43262.sonyInputSource","attribute_id":"inputSource","state":{"value":"TV"},"component_id":"main"}
2023-07-16T16:17:23.657142746+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT0000000000000000
2023-07-16T16:17:23.658109413+00:00 INFO Sony Bravia TV <Device: zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz (Sony Bravia KD-43XH8596)> emitting event: {"capability_id":"platinummassive43262.sonyInputSource","attribute_id":"inputSource","state":{"value":"TV"},"component_id":"main"}
2023-07-16T16:17:23.785397413+00:00 TRACE Sony Bravia TV sony|xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RX < *SAINPT0000000000000000
2023-07-16T16:17:23.786366080+00:00 INFO Sony Bravia TV <Device: zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz (Sony Bravia KD-43XH8596)> emitting event: {"capability_id":"platinummassive43262.sonyInputSource","attribute_id":"inputSource","state":{"value":"TV"},"component_id":"main"}
When the problem with the router was solved, the Sony Bravia in SmartThings App worked normally,
even though these error messages were printed in the log.
Greetings,
Sony Google TVs models XBR-75X910C and XBR-49X830C (the C at the end donates model year 2015) are not being discovered.
Settings:
Remote Start = Enabled
Simple IP Control = Enabled
Authentication = Normal and Pre-Shared Key
Pre-Shared Key = 1111
Renderer = Enabled
Control Remotely = Enabled
Network Status = OK
Wired LAN
TV On
Subscribed to channel and installed Sony Bravia TV edge driver.
Can see media servers in network, so not sure if this an issue with UPnP or a setting. Any suggestions on what to check next?
First, thank you to philh30 for creating this driver, it is beautifully done. I have been trying to troubleshoot the issue where it works for a few days and then goes offline. My TVs are all Google TVs, 2015 and newer (last character on Google TVs indicates model year: C=2015, D=2016, E=2017, etc). After performing some troubleshooting, I suspect is this issue is mostly happening to people who have multiple TVs (would be curious to hear from the group to verify this).
I noticed that sometimes a TV that was working would sometimes control one of the other TVs. And sometimes, it just wouldn’t work, when it did for a few days. I also noticed that it didn’t matter if the passkey on the TV matched the one in the driver settings. I tried creating unique passkeys for each TV, but the TVs still went offline (this is how I discovered the passkeys were ignored). There was an old version of this driver that used IP addresses, and worked flawlessly with a static IP address. I’m not sure how SmartThings identifies the device, but a best guess is it’s getting confused when there are multiple TVs in SmartThings. Hopefully this info will help narrow down what is causing this issue, because it’s a really sweet driver.
2 Likes