Samsung Oven - APIs for setting cooking mode / setpoint / cooking time

Developer Programs Support
1

Hi all!

We recently bought a Samsung Oven, and I would like to be able to control it through a small software I’m developing which is running on my Raspberry Pi.

I would need to set the temperature setpoint, cooking mode and cooking time through the Smartthings API.

I’ve tinkered with them, and it seems that the APIs I need fall into the “Proposed Capabilities” category (not available now): Proposed Capabilities | SmartThings Developers

I would like to know if my understanding is correct and if there is another way to achieve such goals.

Thank you!

1 Like
2

Tagging @nayelyz for help!

1 Like
3

‘Proposed’ is rather like ‘your mileage may vary’. I’ve known capabilities to remain ‘proposed’ for years while being fully functional and in use in official and certified integrations. I do sometimes suspect that there are ‘proposed’ capabilities that only exist because custom capabilities aren’t permitted in certified integrations.

I’ve not got any appliances in SmartThings but from what I can tell even when they do expose capabilities in the API they may not be fully functional for end users.

When it comes to Samsung labelled devices and SmartThings it can often feel that they are not so much integrated as entangled.

Nayely has been tagged and will be better informed in this respect.

2 Likes
4

Thanks a lot for your response!

To be more specific, I can confirm that the following commands aren’t working with my Samsung Oven indeed:

  • setOvenMode (ovenMode capability)
  • setMachineState (ovenOperatingState capability)
  • setOvenSetpoint (ovenSetpoint capability)

As I send those commands Smartthings returns with a 200 HTTP Status code, but nothing happens on the oven.

The only thing I’m allowed to do is to turn the appliance off.

Also, what’s the best way to assess which commands my appliance really supports?

Thanks!

3 Likes
5

Can’t you control the oven directly with the Smartthings App on your phone or with Home Assistant on the Pi?

6

Hi Andrew, I’ve tested with HA with no luck (at the end of the day, it uses the same SmartThings API). The app works fine, but I need to trigger such commands from a custom-made automation software I’m writing.

7

Sorry for the delay.
About capabilities in “proposed” state, this is the description provided by the engineering team:

Mutable, should be supported in APIs but considered beta bugs can happen. Use at your own risk.

Also, something to consider is that OCF devices such as Ovens work at a Plugin level (ST app), not the API level. This means that depending on the configuration of the device controller, not all the info is saved in the API and commands received from there might bring unexpected results.
In this post I shared more info about the functionality:

TL;DR:
You can use the proposed capabilities but they might not work as you expect. OCF devices work best using them from the ST app. The team is aware of the requirement for an improvement of their functionality, there’s no more info so far.

2 Likes
8

Hello, I just want to +1 this request. This functionality is definitely something I am looking for as well. The app UI shouldn’t be the only possible way to start the oven. The safety feature of having to turn the remote control button on anytime the door is opened should not be overridable, IMO. Although annoying at times, it’s a very good method to make sure nothing unwanted (leftovers, pans, pets or kids) is in there before starting. But it should be possible for other controllers (e.g. Home Assistant and Hubitat) to fully interface and control the oven features with parity to the app.

1 Like
9

+1 for this request. We really need open SmartThings, I want to use 1500$ oven within Home Assistant.

1 Like
10

Same here. fucntions not working

1 Like
11

Samsung, please fix this! What’s the point of having a fancy internet connected appliance if nobody can use its API?

12

Speaking off the cuff–no Samsung Oven here–perhaps there were stumbling blocks during development or testing due to safety issues? Can one honestly say it is “safe” to turn on any heating device (gas fireplaces were heavily discussed here several years back) when one is not necessarily present at the device? What if there was a dish towel accidentally stuck in the oven door–propping it partially open, perhaps–and one commands the oven “on” to 450 degrees when leaving work???

I don’t know. Just speculating…

1 Like
13

Something has changed sometime in the last year. I’m now able to successfully start a timed oven cooking session (as in the official SmartThings app), via the SmartThings CLI as well as via direct REST calls to the smartthings api server. I haven’t explored too deeply yet, but I have been able to start various timed cooking modes (Bake, Broil, ConvectionBake, etc.), which I definitely wasn’t able to do before, and also stop cooking (which I believe already worked).

I noticed that the ovenOperatingState capability moved from proposed to production in SmartThings’ documentation at some point in the past year, so that may be when/why this started working.

I use Home Assistant, and have implemented these* as Home Assistant Restful Command actions, but it should be fairly easy for someone to adapt these to curl or any programming language that supports POST requests

rest_command:
  oven_start:
    url: "https://api.smartthings.com/v1/devices/YOUR_DEVICE_ID_HERE/commands"
    content_type: "application/json; charset=utf-8"
    method: POST
    headers:
      authorization: "Bearer AUTH_TOKEN_HERE_ABC_DEF_WXYZ"
    payload: |
      [{"component":"main", 
        "capability":"ovenOperatingState",
        "command":"start",
        "arguments":["{{ mode }}",{{ time }},{{ temp }}]
      }]

  oven_stop:
    url: "https://api.smartthings.com/v1/devices/YOUR_DEVICE_ID_HERE/commands"
    content_type: "application/json; charset=utf-8"
    method: POST
    headers:
      authorization: "Bearer AUTH_TOKEN_HERE_ABC_DEF_WXYZ"
    payload: |
      [{"component":"main", 
        "capability":"ovenOperatingState",
        "command":"stop"
      }]

  oven_set_time:
    url: "https://api.smartthings.com/v1/devices/YOUR_DEVICE_ID_HERE/commands"
    content_type: "application/json; charset=utf-8"
    method: POST
    headers:
      authorization: "Bearer AUTH_TOKEN_HERE_ABC_DEF_WXYZ"
    payload: |
      [{"component":"main", 
        "capability":"execute",
        "command":"execute",
        "arguments":["/configuration/vs/0",{"x.com.samsung.da.currentTime":"{{ now() | as_timestamp | timestamp_custom('%Y-%m-%dT%H:%M:%S') }}" }]
      }]

Add these to the Home Assistant configuration.yaml file, then use the Developer Tools>YAML> and click the reload button for “RESTFUL COMMAND” to make Home Assistant aware of them. Then you can call these actions from anywhere Home Assistant supports Actions (automations, scripts, buttons, etc).

 action: rest_command.oven_start
 data:
   temp: 350
   mode: Bake
   time: 300

Usable modes will depend on the appliance in question supporting them (e.g. my electric range doesn’t have microwave features). I think you can find what your appliance supports using the https://my.smartthings.com/advanced/ site, by browsing the device attributes and looking for supportedOvenModes (e.g. mine are [“Bake”, “Broil”, “ConvectionBake”, “ConvectionRoast”, “warming”, “Others”, “Dehydrate”] ).

Time is in seconds, and temperature is in Fahrenheit because that’s the chosen setting in the SmartThings app. My oven has device profile ‘DA-KS-RANGE-0101X’ and model code ‘NE6516A-/AA0’. I’m currently running Home Assistant 2024.10.4

YMMV!

*In addition to start and stop, I also included a set time action in the above actions, just as a nice-to-have feature. The time set action was adapted from this github repo: GitHub - nomis/samsung-oven-sync-time: Sync time on Samsung ovens

1 Like