Activating scenes whilst switching off associated schedules using urls or batch

I have three problems

1: let’s say a family member sets a scene and someone else comes home how can they tell what scene is running it only seems to flash onto the dashboard overview for a few seconds when setting
I do realize that the active devices are shown but these devices are included in different scenes on my setup how can you tell what scene is running
2: activating a scene using any of the urls below or running a batch file causes a unwanted download request in the browser the scene does activate but I don’t want the download option
3: the final problem is scene one has a schedule running using the code below to activate a different scene does not deactivate the schedule associated with scene one but does activate the required scene
What I need is one scene at a time and if there is a schedule for that particular scene for the to be deactivated with a different scene being requested
http://192.168.10.1:3480/data_request?id=lu_action&output_format=xml&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=3
http://192.168.10.1:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=3
This code is what the browser wants to download

<?xml version="1.0"?>

<u:RunSceneResponse xmlns:u=“Unknown Service”>
OK
</u:RunSceneResponse>

This is the code used in the batch file
@ECHO OFF
wget -q -O NUL http://192.168.10.1:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=3

Kindest Regards

Turby

Hi Turby,

You talk of scenes as if they have a duration or a lifetime. They don’t, really*. They run, they do their tasks in (close to) an instant, and then they vanish. There’s no “memory” of the last scene that ran.

Why don’t you describe what you want to achieve, and we can suggest something else that can do it?

As for the browser trying to save the scene result, that’s probably unavoidable. I was going to suggest that you script it with wget or curl but you are already doing that.

  • You might be able to argue that scenes with delays have a “duration” but there is no way to identify scenes that have started or to prevent their delays from executing. Probably not what you want.

Long Schedules in Vera have problems. If Vera reboots any remaining scheduled steps are lost!

Schedule has different meaning in different contexts. As used in the UI5 Scene naming, a schedule indicates when a scene should be started. It does not have any influence on how long it runs. Here a scene can be started at a specific time(s) or at periodic intervals.

On the device page for scene you “Manage Delays” which is like a schedule. Some things happen now … and other things happen at a later time. It’s this schedule that has a problem if Vera reboots. If the “Immediate” command turns something on … and you want it to go off in 10 minutes … you can create a delay for 10 minutes and then run some more commands then. The problem is that if Vera reboots during the delay it will NEVER shut off your device. If that is something like a heater or pump that might be a problem. There is no way to dynamically change this delay.

What people have used is separate ON and OFF scenes and use things like the Countdown Timer or a plugin I just released called the Program Logic Timer Switch to trigger these scenes witch indirectly controls your devices. And they do it in a manner that works properly even when Vera is restarted/rebooted.

To get the kind of control you want you may want to just control the ON and OFF status of devices your self.

You can run scenes or send commands from an external controller as:

[ul][li]http://VeraIPAddress:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=x[/li]
[li]http://VeraIPadress:3480/data_request?id=lu_action&output_format=xml&DeviceNum=10&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1[/li][/ul]

For the latter the content (serviceID, action, and arguments) is different for the different types of devices in Vera. The example shown is for a binary on/off device.

@turby

Some thoughts, I may well be way off but sharing them anyway :wink:

  1. do you include a notification as part of your scene, so when it is running people can check an email mail or another system and see what was run last. E.g I use Prowl on my ios devices and can check to see if and when a scene was executed or not etc.

  2. as part of your scenes can you turn on/off any flags e.g use a virtual switch ? That could then allow your code/scene to check at certain intervals if something else has occurred or not via another scene ? Run one scene turn Vswitch on, in other scene check if vswitch is xx or yy etc. etc.