Samsung TV driver updated.
I had to follow the guide to remove device and re add (as it stopped working after the update). Hopefully every driver update won’t require this re-install going forward?
There was no reason in the driver it should have stopped working. I wanted reinstall since it was a significant functional update and I wanted to assure any existing issues did not impact the update..
1 Like
Hi @Bloodtick_Jones thanks to you and everyone involved in developing this wonderful program.
I needed to bring August Lock to HE through ST, and I wanted to maintain both Lock & Contact sensor functions. I took a shot using your contact sensor (multipurpose sensor) and replica lock code to create Replica August Lock driver. It is working for my needs - sharing if anyone looking for August lock. Please let me know if you have any feedback.
We are actively looking at locks now. The current solution does not work with Hubitat Lock Code Manager - hopefully have solution new out this weekend.
2 Likes
Ok, my August locks do not have PIN pad, so I didn't need lock code options and hence removed lock code related functions.
Is it possible to include contact sensor part (for August Locks) in the new code?
Shouldn't be a problem, but can you send me your capability JSON that is hidden in the data area of the device handler. Cut & Paste and send private using the </> preformatted text function. I can use that as a guide.
1 Like
I have sent it to you.
Is there any plans to create a driver for the Bluetooth Tags like the Galaxy Smarttag?
Device Type: Tag(BLE)
Component: main
Capabilities: alarm, audioVolume, battery, geofence, geolocation, tag.e2eEncryption, tag.factoryReset, tag.searchingStatus, tag.tagButton, tag.tagStatus, tag.updatedInfo
It would be really neat to be able to use the buttons on it and for presence to show correctly. I can send the JSON part if needed.
I tried as a Presence device but it wasn't showing any states other than the health:
1 Like
Yea, send the JSON and I can take a look. That is a new one for me...curious what it looks like.
3 Likes
Good shout @bfara83, these SmartTags are great little devices, and Samsung seems to (very slowly) add more of it's capabilities to the API, as yet I think geolocation isn't exposed, but if anyone can pull location data from it @Bloodtick_Jones can 
1 Like
Hi @djgutheinz,
As I am testing the use of this driver (Replica Samsung TV) and getting the same reaults as @dsegall got, am I kind of lost here.
My TV is also wiered to ethernet and the On/Off attribues does not seem to be updated at all.
Meaning, the On and Off comands are working just that the switch attribute does not get updated.
If that is the case and I am mostly interested in the On/Off functionality, should I go for the Replica Switch driver?
Edit: I see now that even with the Replica Switch driver, whenever I turn the TV Off it goes offline and the switch attribue stays ON with me not being to turn the TV on again using the TV HE device but only with the remote control.
In the replica app interface the device shows as Offline:
I will investigate (again - again - again) but the Hubitat interface will have the same limitations as the SmartThings interface. Even though on/off are local commands in my implementation - if Samsung can not WOL the set when connected to the LAN, then neither can I.
2 Likes
REPLICA 1.3.02 RELEASE
New release Replica 1.3.02 today to support ST event data:[:] and unit:"" arguments.
Replica Lock 1.3.2 updated to support:
- capability "TamperAlert"
- capability "ContactSensor"
- Hubitat Lock Code Manager (LCM) application
LCM support has proven difficult with the differences between ST & HE lockCode capability. ST does not expose 'codes' so if they are set local or within ST app, HE will not know the new code and update to 'local' status. Also, very little documentation (none) on how LCM actually works with data:[:] structure, so YMMV on how well it works for you.
If you use webCoRE, you can see the data:[:] value as shown below (ST lock must support):
Update 2023/02/10: Release 1.3.03. Change log here.
4 Likes
I am having a very serious problem....
I cannot find a link to "buy the developer a coffee". This is an INCREDIBLE tool!!! I cannot tell you how impressive and well thought out this is and how easy it was to configure and it "just works". The HPM integration makes it so easy. I would like to buy the developers a coffee, but failing to find a link.
Not meant as a bribe, and definitely not complaining, but Meross Garage support and TVs would be nice, but not necessary. Thank you again!
3 Likes
You made a typo, no "s", it's all @Bloodtick_Jones, You're right about the need for a coffee link somewhere, although I personally gave full access to my bank account and said "take what you need".
1 Like
Wasn't meant as an insult to the team (it's a common phrasing). I did pluralize it in the not quoted section and appreciate everyone working on this. It truly is incredible. I kept the SmartThings for the things that work "mostly" cloud based (Kasa) and have built-in support (Meross), so the connect hub breaking was devastating to my ecosystem.
I wanted to express my thanks to the team.
PS, I found the donation link. Thank you.
2 Likes
On the TV request (if Samsung). @djgutheinz has put together some great drivers here.
I don't have context on the Meross Garage, but if you can see it in OAuth and then build a simple Replica switch against it, you can pull the capability JSON and we can take a look. See this post on what to grab and how to post.
1 Like
Hi @Bloodtick_Jones ,
Been using your app with great pleasure to control my Samsung VRF AC units and with the help of @djgutheinz driver I can also control my Samsung soundbar.
Are there any plans to make the Replica drivers Homekit compatable? I know that in general HE only allow for stock drivers to integrate using the Homekit integration (due to Apple's restrictions), but I think there are some exceptions.
I am also aware of the Homebridge option but now that you made me lose interest in my RPI (was using it to run Node-Red and have ST devices integrate to HE) I would like to avoid this additional hub in the way.
What say you?
Yea, you defined the problem -- Apple restrictions for certification are a very tall fence. I am not aware of 'any' exceptions to the HE integration rules. You could build [ST Things] -> [Virtual Device] with Replica rules and have some interaction with HK. I am an Apple Fanboy so if you know a workaround...please tell on private DM.
