# Manually set sensor status value **URL:** \ **Category:** Questions & Help\ **Created:** [March 21, 2019, 10:34pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904 "2019-03-21T22:34:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\ **Post date:** [March 21, 2019, 10:34pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/1 "2019-03-21T22:34:29Z")
Hi, On rare occasions, a sensor is left in triggered status. I guess this can happen if a sensor is tripped and when untripping it faces a communication timeout. So sensor value is not tripped, but Homey still think it is. If I’m still in the house, I can just manually tripp the sensor and it will most likely untripp as it should. But how can I remotely manipulate the trip status of a sensor when I’m not home and on the go? \ Andreas ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [March 24, 2019, 2:55pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/2 "2019-03-24T14:55:21Z")
You could try to send a “basic on/off” command or a “test frame” to the sensor via the developers page. No idea if that works, you never know. It might trigger a wake-up or refresh of the values. ---
**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\ **Post date:** [March 24, 2019, 3:32pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/3 "2019-03-24T15:32:37Z")
Gr8 tip! However, I don’t think I need to manipulate the sensor. It’s the sensors state in Homey that need to be manipulated. ---
**Author:** ![HarriedeGroot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harriedegroot/32/56160_2.png) [@HarriedeGroot](https://community.homey.app/u/HarriedeGroot)\ **Post date:** [March 24, 2019, 4:10pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/4 "2019-03-24T16:10:46Z")
@aste Did you try the [developers page](https://developer.athom.com/tools/devices)? There you can manipulate the state of all your devices. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [March 24, 2019, 4:26pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/5 "2019-03-24T16:26:44Z")
That is only valid for on/off status of witches etc. You can;t change a sensor’s value. At least, as far as i know and to what my developer page shows. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [March 24, 2019, 4:30pm UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/6 "2019-03-24T16:30:31Z")
The sensor state in Home is manipulated by the sensor’s reports. So if you trigger or wake-up the sensor (manually of maybe via the developer’s page), the current values will be sent to Homey. For instance: if your tamper alarm is “stuck” in YES, triggering the alarm manually will send a new YES command, followed by the NO command after the value specified with the “cancel alarm after” setting. ---
**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\ **Post date:** [April 2, 2019, 11:44am UTC](https://community.homey.app/t/manually-set-sensor-status-value/10904/7 "2019-04-02T11:44:02Z")
@HarriedeGroot it seems like my devices lack the drop down on the PIRs for example. Just like @PetervdK indicating. Also most battery powered devices does not have a very frequent wake up interval, so I really can’t consider that to be an option. Also, manually triggering a sensor when away is not really an option 😉 I had this issue the other day again: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/8/8ef6bb0685e306e8a90af515a96aec021d3b4e7c.jpeg) Is HomeyScript able to manipulate sensor states?