I had a similar issue. You need to take Incontrol Offline and Online again and it should work as expected after that.
Version 3.88 ALPHA: Multi-channel and preserved virtual device state
- 363 Views
- Last Post 11 May 2014
I'm on the alpha,
No MC devices yet (have to buy some later) except an appliance control that has energy monitoring. Will try to get it going.
http://www.smartliving.com.au/home-automation/z-wave-in-line-switch.html
Do have multiple virtual devices.
Win 7
Josh
Is MC only for power devices?
The item I linked above supposedly does energy monitoring.
In InControl it shows up as a Light Control and there is no option to break out the device to monitor the energy consumption.
Josh
I'm running 3.82a, I'll install 3.88 tonight.
From Josh's comment I'll also ask, can InControl log the data of Z-wave devices that have built it energy monitoring besides having a dedicated Z-wave energy monitor device?
This is the MC device that I use that support energy monitoring - http://www.smartliving.com.au/home-automation/lighting-control/z-wave-aeotec-2nd-edition-micro-double-smart-switch.html
MC - is typically for devices that have multiple control points built into it. For example, Aeon Labs recently released their smart power strip where 4 of the 6 sockets can be controlled independently of the rest.
As for energy readings and other sensor values, those are typically handled with z-wave reporting, which is already built into InControl. However, most devices do not come pre-configured to send their reports... instead, they selfishly horde them and tell no one about the power being used. You'll likely need to do two things: 1) Associate the device with your USB stick and 2) Use the "Params" button to configure the device to send reports. This is a trickier one because you'll have to Google around and figure out what params need to be changed.
P.S. This has got me thinking about creating a forum specifically for these special configurations. I'll do that after this post - the idea is of course to share what you configured on the device so that it can be a help for everyone.
I installed the alpha yesterday and today at 8:15am the service stopped on its own. From the log file it looks like it was the cloud connect that caused it. I don't think that has ever happened to me before.
Is it just me doing something wrong or does Scene Condition (Device At State Condition for Time Condition) not work?
I previously read that I should use Scenes instead of Rules.
What I've been trying to do it switch off a light once it's been on for X minutes.
Devices: Light I'd like to switch off, set to OFF
Triggers: "Light" change to level 255
Conditions: "Light" has been >= 100 for 1 minutes
I've also tried >= 255, > 0, = 100, = 255
The light stays on after 1 minute.
Only other thing that's made this work is if I don't have any Conditions and I set "Start Delay" under Devices with the time when I want to light to switch off.
MC - is typically for devices that have multiple control points built into it. For example, Aeon Labs recently released their smart power strip where 4 of the 6 sockets can be controlled independently of the rest.
As for energy readings and other sensor values, those are typically handled with z-wave reporting, which is already built into InControl. However, most devices do not come pre-configured to send their reports... instead, they selfishly horde them and tell no one about the power being used. You'll likely need to do two things: 1) Associate the device with your USB stick and 2) Use the "Params" button to configure the device to send reports. This is a trickier one because you'll have to Google around and figure out what params need to be changed.
P.S. This has got me thinking about creating a forum specifically for these special configurations. I'll do that after this post - the idea is of course to share what you configured on the device so that it can be a help for everyone.
Where is this params button, I can't for the life of me find it.
Josh
Where is this params button, I can't for the life of me find it.
Josh
Select your device and the params button is on the bottom right.
Associations | Mirrors | [b]Params[/b] | Delete
I Installed the new version yesterday. The Virtual devices are indeed retaining their status after a reboot.
Thank You!
I have not noticed any problems with this version. The system as a whole seems to be more responsive than before and distant devices appear to be more willing to report status.
So far it's all good.
Thanks again!
N0VTN
We've released an ALPHA version of InControl. This update has support for multi-channel devices as well as logic that will preserve the virtual device values through a reboot.
Note that it's an alpha version which has a brand new z-wave engine, so you might experience some oddness. Though if you do, please let us know so we can get this build out of alpha and into production.
Grab the latest from our downloads page.
P.S. If you run this version, please let us know by replying here so that we can get a tally of who is using it.
Rules -> Conditions do not work for me on my Pro serial. It keeps asking for registration or upgrade.
I'm on the Alpha too. I set up the smartpower strip and have one that controls the whole strip and 4 others that work each outlet independently. So far so good. I also set up a sensor for each of the outlets - these are reporting a value of either 0 or 255 depending on whether the power is on or off. How do I get them to display the energy usage? Also noted that the app shows the sensors and I get the set timer option on these. Should the sensors be display only?
Read your post about changing the device to Energy/Monitor and that gets the display to come up but it's reading as 255 watts per device.
I'm on the Alpha too. I set up the smartpower strip and have one that controls the whole strip and 4 others that work each outlet independently. So far so good. I also set up a sensor for each of the outlets - these are reporting a value of either 0 or 255 depending on whether the power is on or off. How do I get them to display the energy usage? Also noted that the app shows the sensors and I get the set timer option on these. Should the sensors be display only?
We are still trying to work out the energy readings. Just waiting for some info from Aeon Labs.
Just upgraded to 3.89.5145.33863, and the "Rules going away" message every time I click on a rule is [b][i]extremely[/i][/b] annoying, especially as I kept having to click "OK" to three messages when I'd flip from Scenes to Rules to check just when exactly I was triggering rules when I was recoding them as scenes. Also, because of the pop-up, I can't delete the rules now that I've recreated them as scenes.
Also, because of the pop-up, I can't delete the rules now that I've recreated them as scenes.
I suspect that the rules won't delete because they have conditions. If you remove conditions, you should then be able to delete the rule.
Also, because of the pop-up, I can't delete the rules now that I've recreated them as scenes.
I suspect that the rules won't delete because they have conditions. If you remove conditions, you should then be able to delete the rule.
Ah, that was totally it, thanks! I'd been trying to remove the rules as I recreated them as scenes.
Just installed Version 3.88 over the weekend and will install 3.89 tonight. Will give it a look over and see how it goes.
Thanks,
Jim
Version 3.90 has been released as an Alpha. Here it here.
I am using 3.90.5149.26375 with an Aeon ZStick.
A quick question about Scene conditions, They seem to only get used if the scene is triggered by a trigger and are ignored if the Activate Scene button on the GUI is used or from the IPAD or Android app. Is there away to have them applied when manually activating a scene?
I am trying to create a Garage Door Open scene and only want it to run if the door sensor is reading closed. If it can't check the sensor it will just toggle the door which is not wanted.
A possible work around brings up another question, is there a command I can put in the Pre-script that can abort the scene? This could be used to check the sensor and abort if it is not correct.
- Michael
update:
I did manage to do this using a scene to turn on a virtual button that is a trigger for the real scene and the conditions work. But that is an extra scene and a virtual button needed to pull it off.
I am using 3.90.5149.26375 with and Aeon ZStick.
A quick question about Scene conditions, They seem to only get used if the scene is triggered by a trigger and are ignored if the Activate Scene button on the GUI is used or from the IPAD or Android app. Is there away to have them applied when manually activating a scene?
I am trying to create a Garage Door Open scene and only want it to run if the door sensor is reading closed. If it can't check the sensor it will just toggle the door which is not wanted.
A work around is another question, is there a command I can put in the Pre-script that can abort the scene? This could be used to check the sensor and abort if it is not correct.
- Michael
I was about to ask a similar thing. To have the ability to Activate Scene which is what it does now and doesnt use triggers/conditions, but another option of another button that actually activates the scene, but it takes into account triggers and conditions configured. Hoping this can be added in the near future.
Also in the scene devices when you add a "Pause" in the scene device can you add an option like a drop down for (ms, sec, min, hour) instead of just a field to type in a value in ms.
Any feed back on this question?