Can I create a dummy/ virtual device switch?

[Abusyhouse]

I am just starting my foray into the world of home automation.  I was playing with the homeseer, but found the lack of "else" statements and lack of scenes frustrating, so I am giving the ISY a go.  I am using Insteon devices.

 

In Homeseer, I was able to create virtual devices.  the advantage is that they look exactly like a regular switch can be accessed nicely from a basic user screen, and they allow for changing settings easily.

 

Question:  is there any way to create or trick isy into thinking I have a switch when I don't really have one?  I have tried entering random address and picking a device type, but it doesn't find the device and thus it is not created.

 

I could use a program instead, but I find the interface for running the program much more cumbersome, and figuring out the status of the program or variable difficult from any of the mobile interfaces.

 

In this particular example, I'd like to have a virtual button that toggles "are we home for dinner - yes/no".  this way, my wife could easily toggle this option from her phone, and it would then drive various variables and programs to then change our house lighting settings.  right now I'd have to create two programs, one called "we are home for dinner" and another called "we are not home"; regardless, it would be hard to quickly run, and then I would not know the current status from the basic mobile screen as to whether it is a night home or not.

 

Interestingly, I did notice that even if I turned off my 8 button remote, I could still modify and use the buttons.  it would be great if I could somehow trick the system and change it's address to a virtual device and then still use the 8 button remote as a real switch.

 

any insights would be great.

[stusviews]

If you're willing to give up a secondary KPL button, then

 

Create a scene with only that button as a member

 

Create a state variable, for example, sHome that can take on values 0 (home) or 1 (not home).

 

Create two programs, one that changes the variable to 0 if the button is off and 1 if it's on

 

Create a program folder, for example: DinnerAtHome

 

Place a condition on that folder to run programs within that folder if the state variable is 1

 

Place the "yes, we are home for dinner" program(s) in that folder, including any program that runs dinner at home scenes

 

BTW, turning that button on while at home will run those programs and scenes

 

 

[Michel Kohanim]

Hello ABusyHouse,

 

There will be shortly and in our next few 5.x related releases.

 

With kind regards,

Michel

[oberkc]

If you're willing to give up a secondary KPL button, then

 

Create a scene with only that button as a member

 

Create a state variable, for example, sHome that can take on values 0 (home) or 1 (not home).

 

Create two programs, one that changes the variable to 0 if the button is off and 1 if it's on

 

Create a program folder, for example: DinnerAtHome

 

Place a condition on that folder to run programs within that folder if the state variable is 1

 

Place the "yes, we are home for dinner" program(s) in that folder, including any program that runs dinner at home scenes

 

BTW, turning that button on while at home will run those programs and scenes

Or, even simpler, forgo the program and variable. The folder condition could be as simple as

 

If status kpl button is on

Then

Enable programs in this folder to run

 

This is how I do it. Unfortunately, this does not solve the virtual button problem. I use a combination of tasker and mobilinc to create buttons on one of my android home screens, but I have yet to find a way for that virtual button to change (light/dark) as an indication of current status. I understand tasker widget icons are static images. Perhaps I am missing something.

[Abusyhouse]

thanks for your timely responses!  I really don't want to use a physical KPL, because although I gave one such above example,   I have many such "switches" planned for my overall workflow, the majority of which will be accessed on occasion from a mobile screen.  it would not make sense to dedicate a few dozen kpl's for that.

 

In our specific case, the plan is that we have an overall weekly light schedule, but when planning a weekend or other holiday, there are many variables that we want to set on the fly like "are kids sleeping in on Saturday", "are people coming over for dinner",  "we have a guest staying over in the guest bedroom" or even something as simple as "temporarily remove our son's light from programs".  Each of these need to be a quick on/off toggle for my wife to access easily from a mobile screen, and see the current status of that condition.

 

I am very excited to hear that the virtual switch is on it's way, since from reading this forum, this has been brought up as an issue for a while,  so I consider it lucky that I am starting at the right time. 

Any idea timewise when we might expect it?

[oberkc]

I think were I to desire to do what you described, the best approach I can think (until isy v5) would be a combination of mobilinc and programs. Create a program for each interested condition (dinner guests, weekend away, overnight guests, etc....). Each program would be completely blank (if triggered entirely from the phone)

 

If

Nothing

Then

Nothing

Else

Nothing

 

Once established, these programs are visible from mobilinc. Using mobilinc "run then" or "run else" clauses for any of these, you would be setting the programs as TRUE or FALSE. This program status could then be used as conditions for other programs and react accordingly.

 

It is an approach only a mother could love, but it would be functional.

[Abusyhouse]

very interesting;  I will give that a try

[Michel Kohanim]

Hello Abusyhouse,

 

Virtual nodes and variable enhancements are on top of our priorities for 5.0x. I cannot give you a timeline (since I am usually off) but I can tell you that we are working on them right now.

 

With kind regards,

Michel

[bernieb]

That's good news, I had a similar request a little over a week ago.

This is one of the feature that I liked about Homeseer, they would allow you to create virtual devices with unused X-10 house codes.

Since X-10 has a possibility of House Code A to P and 1 to 16, the virtual devices had House Code Q to Z and 1 to 16

[builderb]

Before my ISY, I was using Indigo on my Mac for HA. I just got an email from them about a new plugin that is available that aims to provide a framework for virtual devices. The first module for it allows you to create a virtual thermostat from a temperature sensing device, and say, a relay module. So, if you had a temperature sensor, and a small space heater connected to an outlet linc in a small room, you can interact with them as a single thermostat device.

 

Interesting concept.

[Abusyhouse]

I think were I to desire to do what you described, the best approach I can think (until isy v5) would be a combination of mobilinc and programs. Create a program for each interested condition (dinner guests, weekend away, overnight guests, etc....). Each program would be completely blank (if triggered entirely from the phone)

 

If

Nothing

Then

Nothing

Else

Nothing

 

Once established, these programs are visible from mobilinc. Using mobilinc "run then" or "run else" clauses for any of these, you would be setting the programs as TRUE or FALSE. This program status could then be used as conditions for other programs and react accordingly.

 

It is an approach only a mother could love, but it would be functional.

thanks for all of your responses, and in particular oberkc for the above suggestion, It works quite well, especially with the mobilinc app, as I can quickly see and change the state from the same one button that I push (I still have to go down one screen level, but is quite workable).  I will await the update!