Comments (8)
mmende
commented on August 16, 2024
Hi,
Nice to hear you made it half way through.
At the moment it is necessary that the plugin discovers the device itself before the device will show up as external accessory because it fetches some additional device infos and uses upnp also to keep track of possibly changing ip addresses and upnp location. However, the error might lead to crashing homebridge before the device discovery even starts. The problem seems to be caused by node-persist trying to create the persistent directory at /.node-persist. You might just try to create the directory yourself and change the permissions of that folder generously for testing like mkdir /.node-persist and chmod 777 /.node-persist. I hope this leads to homebridge not crashing anymore and showing your tv correctly with the usn (remember to turn your tv on before restarting homebridge).
PS: If you know the user homebridge is running under, it would be better to make this user the owner of this directory
chown homebridge:homebridge .node-persist (if the user is homebridge e.g.) instead of making the directory read/writable by every user what the previous command does
PS2: I might add an option to add tv's that can for some reason not be discovered over upnp even though this would require setting up a static ip for the tv and finding out some values yourself.
from homebridge-samsungtv-control2.
mmende
commented on August 16, 2024
I will also change the default location, node-persist is using to the homebridge storage path in the next release... this hopefully solves the problem once and for all.
from homebridge-samsungtv-control2.
ggroel
commented on August 16, 2024
👍
Gastón
… El 26 jul. 2020, a la(s) 15:02, Martin Mende ***@***.***> escribió:
I will also change the default location, node-persist is using to the homebridge storage path in the next release... this hopefully solves the problem once and for all.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
from homebridge-samsungtv-control2.
ggroel
commented on August 16, 2024
Martin , you still think that the plugin can work for my TV (2010)... ? Jeje
Gastón
… El 26 jul. 2020, a la(s) 15:56, Gastón Groel ***@***.***> escribió:
👍
Gastón
> El 26 jul. 2020, a la(s) 15:02, Martin Mende ***@***.***> escribió:
>
>
> I will also change the default location, node-persist is using to the homebridge storage path in the next release... this hopefully solves the problem once and for all.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
from homebridge-samsungtv-control2.
ggroel
commented on August 16, 2024
Martin,
Trying various things I have found some stuff that maybe can help you (or help me jejejej). With the Samsung_tv plugin (https://github.com/danimal4326/homebridge-samsung_tv#readme) I was able to configure my 2010 samsung to see the status (on / off), I can't actually turn it on or off, but I can see the status at least. On the other hand, with the homebridge-upnp plugin (https://github.com/langovoi/homebridge-upnp#readme) I was able to recognize my TV and it adds a lightbulb to control the volume (and it works !!!). The interesting thing about this last plugin is that it discovers all upnp devices and found that the USN of my Samsung TV is "uuid:f7b6d1b3-847a-3459-3e1e-f8a03ff7bc32::urn:schemas-upnp-org:device:MediaRenderer:1” and it worked when I entered it complete and not just the uuid part.
I mean, thanks to these two plugins I can see the status of my TV and control the volume. Is there any chance that you “blend" these two things on one platform (at least for Samsung <2014)? THANK YOU THANK YOU THANK YOU!!!
On the other hand, I tell you that for 2 or 3 versions of your plugin, the log shows me that the platform is initialized, but it does not find any device, but in previous versions it indicated that 1 device had been found (it did not work later , but at least he informed me that he had found something ... not now). Thank you!!
Gastón
… El 26 jul. 2020, a las 16:01, Gastón Groel ***@***.***> escribió:
Martin , you still think that the plugin can work for my TV (2010)... ? Jeje
Gastón
> El 26 jul. 2020, a la(s) 15:56, Gastón Groel ***@***.***> escribió:
>
> 👍
>
> Gastón
>
>> El 26 jul. 2020, a la(s) 15:02, Martin Mende ***@***.***> escribió:
>>
>>
>>
>> I will also change the default location, node-persist is using to the homebridge storage path in the next release... this hopefully solves the problem once and for all.
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APBDDDEW34AOLCKF257EIILR5RVUDANCNFSM4PH5K73Q>.
>>
from homebridge-samsungtv-control2.
mmende
commented on August 16, 2024
Thanks @ggroel ... That actually helps and I have an idea now why your TV (and some others) are not being detected by the device discovery now. I post some more details tomorrow.
from homebridge-samsungtv-control2.
MBarti
commented on August 16, 2024
@mmende Martin, great tips! Now it works fine. The TV is detected properly and I've added it to homebridge without problems. Now I can finally use it in automations! Thank you!
Ps. For other users: The H/J-series TVs (and maybe others) allow one to turn the TV off, but not on (not even wake-on-lan). So to turn it on in automations I use the Apple TV (via CEC).
from homebridge-samsungtv-control2.
mmende
commented on August 16, 2024
Awesome... nice to hear that.
from homebridge-samsungtv-control2.
Related Issues (20)
- Connect but the TV asks for confirmation of every command
- Does not appear in homekit
- Error controling TV
- Toggle Log Entry for 'Found unparsable model name....'
- HTTPError: Response code 404 (Not Found)
- HomeKit issues
- Pairing with bridge seems to work but no control possible from homekit HOT 3
- Pairing issue HOT 1
- Paired but not working ON/OF
- TV volume working but cant turn off, I get this error? Any help pls?
- UE40F6400AK always OFF in HomeAPP
- DEPRECATED user supplied a custom 'mdns' option. HOT 2
- Unable to pair UE65KS8005 HOT 2
- Samsung UE48J5510, power off ok, power on does not work HOT 1
- Control without discovery?
- Can't control TV
- Can't control TV, successfully added though!? HOT 3
- Found unparsable model name xxxx for device xxxxx, usn: "uuid:xxxxxxxxxxxxxx". Skipping it. HOT 2
- SIGTERM Homebridge 1.5.1 HOT 1
- How to use Legacy Mode? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homebridge-samsungtv-control2.