# Sensors Webhook from Groovy to?

**URL:** <https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562>\
**Category:** Support\
**Created:** [March 27, 2021, 3:37pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562 "2021-03-27T15:37:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mario550](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mario550](https://community.smartthings.com/u/mario550)\
**Post date:** [March 27, 2021, 3:37pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/1 "2021-03-27T15:37:39Z")

</div>

Hi,

I have a couple of simulated motion and simulated contact sensors which are being updated using a smartapp receiving a webhook update.  
This is working very well so far, except a couple of problems in the last weeks.

With Groovy going away, is there an easy way to convert this for a non Expert developer.

Trying to get ready for the future.

thanks for your advice.

Mario

---

<div class="post-metadata">

**Author:** ![Automated\_House](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/automated_house/32/99641_2.png) [@Automated\_House](https://community.smartthings.com/u/Automated_House)\
**Post date:** [March 27, 2021, 3:55pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/2 "2021-03-27T15:55:46Z")

</div>

Try the Samsung automation studio.

---

<div class="post-metadata">

**Author:** ![orangebucket](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/orangebucket/32/81590_2.png) [@orangebucket](https://community.smartthings.com/u/orangebucket)\
**Post date:** [March 27, 2021, 6:36pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/3 "2021-03-27T18:36:07Z")

</div>

> [@mario550](#):
>
> With Groovy going away, is there an easy way to convert this for a non Expert developer.

If you have your own hosting you could create a simple script in your choice of language that makes a call to the [REST API](https://smartthings.developer.samsung.com/docs/api-ref/st-api.html).

---

<div class="post-metadata">

**Author:** ![mario550](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mario550](https://community.smartthings.com/u/mario550)\
**Post date:** [March 29, 2021, 6:55pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/4 "2021-03-29T18:55:33Z")

</div>

Thanks for the info. I will try the 2 proposed solutions. Hope there is good tutorials.

---

<div class="post-metadata">

**Author:** ![mario550](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mario550](https://community.smartthings.com/u/mario550)\
**Post date:** [April 5, 2021, 3:46pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/5 "2021-04-05T15:46:02Z")

</div>

@Automated_House , @orangebucket

Thanks for the suggestion on using Samsung Automation studio. I was able to connect and control light switches, and get the **status** on a simulated motion and contact sensors. I was able to achieve the same thing using a Node Red instance with Smartthings palette hosted locally.

But I cannot force the status of the contact or motion sensor to (Open/close, Active/inactive). it is probably a capability thing!!!

My goal is to update a simulated contact sensor using a rest api without any smartapp, custom DTH and no groovy.

Any idea what the problem is.

thanks

---

<div class="post-metadata">

**Author:** ![orangebucket](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/orangebucket/32/81590_2.png) [@orangebucket](https://community.smartthings.com/u/orangebucket)\
**Post date:** [April 5, 2021, 8:08pm UTC](https://community.smartthings.com/t/sensors-webhook-from-groovy-to/223562/6 "2021-04-05T20:08:32Z")

</div>

> [@mario550](#):
>
> Any idea what the problem is.

The Simulated Contact Sensor hasn’t been updated for about three years and uses custom commands to set the contact attribute to open or closed. That’s a legacy concept and never one that was particularly encouraged.

Current integrations are capability based so I’d imagine the `open` and `close` commands just aren’t accessible.

I don’t consider the collection of ‘Simulated’ sensors as stock sensors and I’d never use one as anything but a test device.
