Is it possible for someone to supply/build a Replica driver for the newer Roomba 505+ ?
I don't seem to be able to find one yet.
Have you attempted matter integration with Hubitat? There are no Replica drivers for vacuums.
Yes. I set it up through Smartthings, then had Hubitat connect to the Roomba via Matter. Unfortunatly Hubitat only set it up as a "Device". The log shown "Created Unknown Matter Device". I tried using one of the Home Assistant device drivers, but that didn't work.
Thank you! I was able to add my two Samsung TV's as replica devices on my Hubitat.
All the basic functionality is there except the one command that brought me here in the first place- PICTUREMODETOGGLE (or alternatively, Set Picture Mode). With either of these commands I get an error message of "} status:422 reason:Unprocessable Entity"
Does anyone know if it's possible to enable this particular functionality? I have a number of different lighting scenes for different times of the day and when one of them triggers, I want the TV to automatically change to either "AI Customization" (for daylight viewing), "Optimized" for early evening, and "EyeComfort" for nighttime.
The only way I've been able to accomplish this is with a clunky scene where I go through the motions manually to pull up settings on the TV, right arrow, select, picture mode, select, down arrow, select, etc. to finally navigate to what I want. It works but it's slow and clunky obviously. Being able to just toggle picture modes with a single command would be heaven.
Doing this the long way, so you can fix this if it happens again in the future...
Not sure if this is the same for your TV, but it looks like Samsung changed the API (again) and the default rules will error for you. You can tell by going to the Samsung Advance page and finding your TV.
You should find the command there, probably 'now' looks like this:
If you notice the capablity is set 'now' by: samsungvd.pictureMode and my bet the error you are seeing when you attempt to set is attempting to set custom.picturemode like so:
To fix this, go into the Replica app and select your TV and delete the following commands and then re-add them:
delete example:
add example (with Show attribute.. turned on)
You can see the new capability value (if you have the Show attribute setting on)
for even more fun, looks like they require you to use the id now, you can see them here:
Welcome to Samsung SmartThings, where something is usually different every day.
DM me if you get stuck.
Added Note: FWIW, I have a 2025 QN65S95FAFXZA that is using the new API, and a 2022 QN43QN90BAFXZA that is using the old API.
2 Likes
This is amazing; thank you so much for the detailed reply! I'll give this a shot and report back. 
I did push an update this morning to help, you can update via HPM.
You will find a "Device Default Replica Rule Set" in the preference section now. If you set that to '2' and select 'Reset Device to Default State'.
It should update your rules and update all the values to this newer API. YMMV.
To note, it looks like the mode will change if the TV is in HDR mode!
And that makes it more difficult. So I put a helper in to grab all the values and try them.
This should be a similar JSON you see now in the state after doing a SDR and HDR:
[{"name":"Dynamic","id":"modeDynamicHDR"},{"name":"Eco","id":"modeEcoHDR"},{"name":"FILMMAKER MODE","id":"modeFilmmakerModeHDR"},{"name":"Movie","id":"modeMovieHDR"},{"name":"Standard","id":"modeStandardHDR"},{"name":"Dynamic","id":"modeDynamic"},{"name":"Eco","id":"modeEco"},{"name":"FILMMAKER MODE","id":"modeFilmmakerMode"},{"name":"Movie","id":"modeMovie"},{"name":"Standard","id":"modeStandard"}]
You can see that "Dynamic" actually has two values of "modeDynamic" and "modeDynamicHDR". If you do a (not case sensitive)
setPictureMode("Dynamic")
The code will try both IDs so you don't need to guess.
Of course you could set a rule to send both "ids" as well.
I would expect your TV to look something like this using the new rules:
Here is the 2022 TV:
1 Like
Thank you so much again! So I'm still stuck and here's what I've done:
- Deleted my old HubiThings TV on the Hubitat.
- Updated the app with Package Manager
- Re-added my TV as a HubiThings device through the App.
- Initialize/config. All of the basic functionality works just fine on the replica TV device on Hubitat.
- Now when I go to "Set Picture Mode" I'm still getting the same errors.
-
I have three options on my 2025 TV: EyeComfort, Optimized, AI Optimization.
-
If I just type in "EyeComfort" for example (no quotes), I get the same error message I had before "unprocessable entry."
-
I logged in through SmartThings and noticed that "setPictureMode" doesn't actually use the name of the mode, but a different string. For example, EyeComfort is actually "modeGen_589826"
-
Ok, so I went back to Hubitat and tried that string instead for the Set Picture Mode option. Same error (tried it with the quotation marks as well, no dice).
-
I also tried your new feature (thank you agin!) and switched to Rule Set 2. Unfortunately I got all the same errors. I tried inputting both EyeComfort and modeGen_589826
My feeble mind is again stuck LOL. Oh and here at the attributes I show on the HubiThings "Main TV" device in Hubitat:
Well damn, ignore everything I just said. I forgot your step of "Reset to Default Mode." I foolishly thought I didn't need to hit that since I reinstalled the device.
THAT WORKED! You are amazing and I can't thank you enough for all of your work!
1 Like
Is it possible to use Hubithings replica to mirror Hubitat devices into Smartthings cloud withOUT a Smartthings hub, essentially using Smartthings as a cloud-based dashboard?
I've got all authorizations set up, but I can't figure out the steps to create the devices to be mirrored, if it's even possible.
You can using 'Create Virtual Device, Mode or Scene ' to create virtual devices in SmartThings. It isn't the best solution to be honest and is limited in functionality. Mira does a better job but you do need a hub for that.
Hi, I'm thinking about installing this driver and want to replace my current used one. The question on my end, is it currently possible to start the Samsung washer remotely?
Somewhere it says it's possible to start the washer somewhere it says Samsung blocked this for safety reasons.
Thanks
If you can do it from this SmartThings Advance Website. You can probably do it remotely.
Thanks for the response. One question, currently I'm using the Samsung washer from Dave Gutheinz. I still have an Samrthings API Key and Smartthings Device ID using with this driver. It seems I cleared my Samsung account when I ditched the TS hub. I do have the account but no device is listed.
The status of the washer is still working fine in hubitat.
@Bloodtick_Jones What would be the next (best) step if I would like to try out HubiThings Replica?
Add the Samsung washer to my Samsung account again, or just straight away setting up the app and using the ST ID and ST API Key in combination with HubiThings Replica?
Any advice?
Thanks
Not sure this is perfect advice, but the washer should show up in your SmartThings account either way.
I’d try this order:
- Set up HubiThings Replica and use your existing PAT (API key) first.
- When HubiThings sends you through the OAuth authorize step, check if the washer is listed.
- If it’s there, you’re good. Go ahead and try Dave’s HubiThings driver.
- If it’s not there, you’ll need to get the washer re-added into SmartThings first (you shouldn’t need a SmartThings hub for a washer), then retry HubiThings.
On the token side: it sounds like your PAT is one of the older long-lived ones. If you end up needing to create a new token to get HubiThings working, SmartThings tokens can be short-lived, but HubiThings should keep its auth token refreshed so it continues working.
Also, if what you have today is already working, I’m not totally sure you’ll gain a lot moving to HubiThings beyond possibly better real-time events.
One thing I would not do: don’t delete your existing washer device in Hubitat while you test HubiThings. Leave the current setup in place until you confirm HubiThings is stable. Both setups should be able to coexist during testing as long as the PAT has the right scopes.
@djgutheinz for any additional commentary.
Good news, found the correct Samsung/Smarthings account where my washer is listed. I think this makes things a bit easier. So please forget the nonsense I wrote before that my washer isn't misted and sorry for pushing you in the wrong direction.
Being able to see my washer in my account I can setup HubiThings Replica more easily, right?
You mentioned in your inital response that I could try to remote start my washer using the account. Can you please briefly explain how to do that and what's starting from that point the best way to set up HubiThings Replica?
And sorry again for messing this up
Correct. I didn't think it would work without to be honest.
Follow the directions at the beginning of this thread. From there the application does a reasonable job of walking you through next steps. You will need both the Replica application and Dave's supplement driver package. Everything is in HPM.
1 Like
Good evening. I'd like to start by thanking @Bloodtick_Jones for all the work put into this - 99% of my setup has been phenomenally smooth and it's made it much easier to slowly move from Smartthings to Hubitat. I am, however, having one problem that I haven't found an answer to in the thread here - hoping someone might have run across it.
One of the devices I have running in my house is a Konnected Alarm Panel Pro which ties in all the wired sensors and sirens/speakers from my former alarm. Yes, I know Hubitat can talk directly to Konnected but I need to reflash the firmware on the Konnected to enable that and the board is in a place I can't get to right now - long story - so I need to access it through SmartThings for now. All of the sensors have come over perfectly, but the one problem I have is with the control for the piezo. In SmartThings this is a c2c-switch that has a Momentary profile. It supports 2 commands: healthCheck and momentary. However, when I create this device as a Replica Switch the piezo does not respond and, looking at the rules, there is no option to configure a rule to send a Momentary command, just a push() which does not trigger the Momentary. I tried this as a Virtual Switch and a Momentary Button as well, but none of them generated the right command.
I assume I'm missing something obvious but I've run out of ideas. Appreciate any help others can provide on how to send the right kind of signal to Smartthings.
The SmartThings API does not natively support momentary anymore so this might/must be a custom skill. Go to the "support new device" tab and post me (as preformatted text) the CAPABILITIES and STATUS json structures and I can try to see what they are doing.
@hayfever looking at the json structures, I don't think Replica can accomplish what you want exactly...but here are some options.
You should be able to create a POST command via Rules Engine or webCoRE. Use this with YOUR_DEVICE_ID and YOUR_PAT_TOKEN:
curl -X POST "https://api.smartthings.com/v1/devices/YOUR_DEVICE_ID/commands" \
-H "Authorization: Bearer YOUR_PAT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"commands": [
{
"component": "main",
"capability": "momentary",
"command": "push",
"arguments": []
}
]
}'
You can see the API documentation here and the momentary capability here. Running commands that are not present in the capability JSON is an odd thing, and honestly I think that is something incomplete in the ST device, so YMMV. If you can get that working with a PAT, you should be able to use the OAuth authToken. Look in the HubiThings OAuth and you will see links to fetch the current working authToken.
ANOTHER method might be to run a routine in SmartThings using a virtual switch extended from Hubitat that activates your momentary push button. You can build one in Replica under “Configure Virtual…”. This is just a guess on whether it works in SmartThings since again this device looks incomplete without the 'push' in the capability JSON.
