Vera - Smarter Home Control Forum

General => Lighting & Load Control => Topic started by: Greybeardvacationrental on June 24, 2017, 03:43:59 am

Title: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 24, 2017, 03:43:59 am
Hello all,

I installed GE dimmer switches throughout my vacation rental.  They are paddle style.  The issue I'm running into is that people don't understand that by tapping the down on the paddle will turn off the light.  Instead they hold the down on the paddle to turn off the light.  This, of course, does not actually turn it off.  It brings it to 1%.  What I would like to do is have the switch automatically turn off if the light switch hits 1% (or like 5% or lower).  Can anyone help me on how I would do this?

Thanks so much.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Z-Waver on June 24, 2017, 05:18:44 pm
There are a few ways to skin this cat, but I would use the Program Logic Event Generator(PLEG). I'd setup a PLEG that tests to see if the HallSwitch is between 1-5% and if it has been in that range for more than 2 to 5 minutes, then switch the light off.

Input:
Device Property
MyHallLevel: HallSwitch  LoadLevelStatus

Conditions
InTheZone:  (MyHallLevel > 0 AND MyHallLevel < 6)
TurnOff:        (InTheZone AND (InTheZone; NOW > 2)

Actions:
TurnOff :       Turn HallSwitch Off

Title: Re: Help with turning off dimmer when light hits 1%
Post by: Don Phillips on June 24, 2017, 05:25:54 pm
That was going to be my suggestion but Z-Waver beat me to it.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 26, 2017, 09:40:00 pm
Ohhhh PLEG.   This is a new thing for me.  I've downloaded the Program Logic Event Generator and Program Logic Core.  Once in there though... yeah... I'm gonna have to search in here for PLEG posts.  Cause I understand the concept of what you are doing up there above but how to put this in PLEG isn't as obvious.  I was able to create the "Device Property" but when I get to the conditions I begin to get that GREEN feeling LOL
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 26, 2017, 11:24:53 pm
The GE switches don't support instant status. So, you'll have to rely on polling. Just create a scene that runs every 5-15 minutes (pick an interval that makes sense to you that won't overload VERA) that polls the various switches. When the current DIM Level is found to be x% or lower, send a command to turn them off.

This is all done in LUA scripting.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Z-Waver on June 27, 2017, 07:03:08 am
PLEG Basics - An Introduction to the Program Logic Event Generator (http://forum.micasaverde.com/index.php?topic=21603.0) by @RexBeckett

Of course you could accomplish the same thing with Lua code, as @ember1205 points out. But, I think PLEG is more within reach fro most people, as compared to Lua programming. None the less: Conditional Scene Execution: Some Examples (http://forum.micasaverde.com/index.php?topic=18679.0) by @RexBeckett
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 29, 2017, 01:15:42 am
Thanks peeps!  I will check that manual out when I have some time and give it a go!  I'll keep you posted on how I do! 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Priest on July 05, 2017, 11:09:26 am
The GE switches don't support instant status. So, you'll have to rely on polling. Just create a scene that runs every 5-15 minutes (pick an interval that makes sense to you that won't overload VERA) that polls the various switches. When the current DIM Level is found to be x% or lower, send a command to turn them off.

This is all done in LUA scripting.

I just installed one of the z-wave plus GE dimmers like this and it does support instant status. Every change made by pressing the paddles immediatly showed in the Vera dashboard. If he has the new one he can avoid the extra polling.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on July 05, 2017, 11:17:11 am
The GE switches don't support instant status. So, you'll have to rely on polling. Just create a scene that runs every 5-15 minutes (pick an interval that makes sense to you that won't overload VERA) that polls the various switches. When the current DIM Level is found to be x% or lower, send a command to turn them off.

This is all done in LUA scripting.

I just installed one of the z-wave plus GE dimmers like this and it does support instant status. Every change made by pressing the paddles immediatly showed in the Vera dashboard. If he has the new one he can avoid the extra polling.

Nope. That isn't instant status. You're getting quick response because the switches do send a notification packet, and because the Vera is "directly adjacent" to your switch, it works a lot LIKE instant status. It isn't 100% reliable, as you will discover at some point in the future if you're using the operation of that switch to trigger other things to happen.

Cooper and Leviton have paid for the rights to use Instant Status in their switches, so those are the ones where you will find it (not ALL models, mind you).
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Priest on July 05, 2017, 11:30:11 am
Okay, good to know.

Everything in my house can communicate with my Vera3 (no antenna mod) directly. I dont have a little house, but the Vera is 3 feet below the floor joists on the wall in the basement and dead center of the house.  I guess im lucky that I dont actually have to rely on the mesh for things to work.

I have not triggered events off of that switch status....since I just installed it night before last. It is good to know that I'll need to be careful if I plan to in the future. I am using that type of trigger off of a couple enerwave dual relay switches and have only missed commands when Vera decides it wants to miss every command from everything. The rule then is to stop pushing buttons and flipping switches and let her sort her issues out. She usually catches up and does everything at once within about 5 minutes of the hiccup.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on July 22, 2017, 02:51:32 pm
Ok I finally was able to try this and it looks like I'm having issues with the TurnOff under the conditions.  The InTheZone seems to be going through but then it says the TurnOff is invalid.  I've checked the spacing... the parenthesis etc and it all seems to be just as you have it. 

In the action do I literally do nothing but select it and change the name and that's it?

Thanks


There are a few ways to skin this cat, but I would use the Program Logic Event Generator(PLEG). I'd setup a PLEG that tests to see if the HallSwitch is between 1-5% and if it has been in that range for more than 2 to 5 minutes, then switch the light off.

Input:
Device Property
MyHallLevel: HallSwitch  LoadLevelStatus

Conditions
InTheZone:  (MyHallLevel > 0 AND MyHallLevel < 6)
TurnOff:        (InTheZone AND (InTheZone; NOW > 2)

Actions:
TurnOff :       Turn HallSwitch Off
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on July 22, 2017, 05:34:57 pm
Ok.... Never mind...   I GOT IT!   Not sure exactly how that all happened so easily but this is what I did.  I entered the input for each of my light switches (there are a good number) just like you had in your post here.  However in the conditions I only entered the first one in your post... the In The Zone one for each switch.  Then I went over to Action and for each switch I entered the device in the part down below and in the action I set the dimmer level at 0.  Ran each one and then saved.  Rebooted Vera and now...  without having to poll or anything... whenever a light switch is brought down to 4% or less it just goes to the OFF (or zero) immediately.  That is just brilliant!  And I did it all from 5000 miles away.  LOL 

Thanks for your advice and input. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on May 26, 2018, 01:01:27 pm
So update on this idea of turning the switches off at a low % of dim.  This worked well in PLEG.  I have a vacation rental with the GE dimmer switches.  The guests don't seem to understand them so instead of just hitting the paddle down to turn off the light a few people hold them until they dim down until they think it's off.  Leaving the dimmer at 1 - 4%.  I was trying to combat the switch eventually burning out from constant on mode.  Well it was a nice thought but what I've actually found over the course of the year is that the guest dims it to 1%, Pleg in Vera then turns it off.  Unfortunately though the dimmer remembers the last setting and so when a guest hits the up on the paddle to turn the light on it goes up to that % it was last set at and then Pleg turns it off so it makes it look like the dimmer on is broken and you have to hold it up to get the full function to work again.  So... right sentiment...  not so right in actual practice. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on May 26, 2018, 03:04:31 pm
So update on this idea of turning the switches off at a low % of dim.  This worked well in PLEG.  I have a vacation rental with the GE dimmer switches.  The guests don't seem to understand them so instead of just hitting the paddle down to turn off the light a few people hold them until they dim down until they think it's off.  Leaving the dimmer at 1 - 4%.  I was trying to combat the switch eventually burning out from constant on mode.  Well it was a nice thought but what I've actually found over the course of the year is that the guest dims it to 1%, Pleg in Vera then turns it off.  Unfortunately though the dimmer remembers the last setting and so when a guest hits the up on the paddle to turn the light on it goes up to that % it was last set at and then Pleg turns it off so it makes it look like the dimmer on is broken and you have to hold it up to get the full function to work again.  So... right sentiment...  not so right in actual practice.

If you update your PLEG routine that turns it off to ALSO set a value on the variable "LoadLevelLast" to 100, that would allow the switch to come back on at 100% brightness. I can't guarantee that's the variable name you'd need to use because I don't have any of the GE Dimmers in use - mine are all Leviton. You can check the Advanced settings for the device and look at the Variables tab to find what it's actually called on your switches.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Tillsy on May 28, 2018, 12:32:37 am
Unfortunately though the dimmer remembers the last setting and so when a guest hits the up on the paddle to turn the light on it goes up to that % it was last set at and then Pleg turns it off so it makes it look like the dimmer on is broken and you have to hold it up to get the full function to work again.  So... right sentiment...  not so right in actual practice.

I can't vouch for your specific dimmers, but my Fibaro dimmers have a setting where I can control 1) Remembering the last dim level, or 2) Forcing a specific brightness each time they are turned on.

For a couple of mine I have them forcing 99% - both of them are typically turned on manually and needed at 99%, but for various circumstances their brightness will be automatically changed (eg my living room lights will automatically dim when we turn off our dining table light AND its evening, the vanity light near my kids rooms will automatically come on at 1% when we go to bed and turn off at sunrise... both are back to 99% when manually turned off and on or are turned on fresh).  The others I have retaining their prior brightness level, as they automatically come on via motion sensor association - I still auto-control the brightness as necessary, but the lights always stay at that brightness until I say otherwise.

If you don't have a setting for that then, as ember1205 suggested, just add in an extra step in your logic to bump up the brightness.  I do similar with my auto-brightness controls for the sensor controlled lights... whenever I auto-change the brightness I then have to send an off command, as changing the brightness unfortunately also causes them to turn on.

Alternatively don't even turn them off.... just set 5% or lower to instantly jump back to 99%.  Thus it's never possible to get to an "off" brightness, it just loops back to full brightness.  Thus they'll then turn them off manually (and/or a timeout so if the lights are left on more than x hours they auto-turn off).

Disclaimer - I should add that my setup above DID work well until my Vera completely shat itself two weeks ago, so I'm talking theoretical as my home is pretty well screwed and all this stuff goes batsh#t
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on May 28, 2018, 10:11:40 am
If you update your PLEG routine that turns it off to ALSO set a value on the variable "LoadLevelLast" to 100, that would allow the switch to come back on at 100% brightness. I can't guarantee that's the variable name you'd need to use because I don't have any of the GE Dimmers in use - mine are all Leviton. You can check the Advanced settings for the device and look at the Variables tab to find what it's actually called on your switches.

I'm not sure how to go about this.  I've managed to reset my switch to turn off when it's dimmed to 4% or lower.   And when I hit the On button it does not come on because the last known set was 4% and it turns it off again.  I've gone into the Action tab and have tried to add a second action from that device to set the "LoadLevelLast" to the desired % so that when you turn the light on again it will go to a set level but after picking the device for a second time in the "Select Device to Add to Current Interval" and then going to the action drop down to the right "LoadLevelLast" is not listed.  Actually the commands in this list do not match at all the commands I got when I added the device to the "Device Input" tab.

I even tried adding a whole new Device Input just for "LoadLevelLast" and putting the same conditions on it and then go to the Action.  Again the fields to choose from are completely different than the fields from the Device Input.  I do not see a "LoadLevelLast" to set in the action drop down.

Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on May 30, 2018, 03:58:20 am
Is there anyone that could possibly help me with this?  Write a script of code or something?   All of my dimmers have "LoadLevelTarget", "LoadLevelLast" and "LoadLevelStatus" in the variables under the advanced tab.  The goal:

When the switch is dimmed to 4% or less the switch turns off and sets the "LoadLevelLast" to a desired % depending on the dimmer. 

Thanks in advance to all the experienced ones out there.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on May 30, 2018, 11:49:05 pm
Create a scene that is triggered by the light being turned off. There is no immediate or delayed action, but you will need it to run a piece of LUA code to set LoadLevelTarget and LoadLevelLast to some value (same for both) which will become the lighting level when they are turned back on again.

The LUA code will need to be something like (this is off the cuff, so no guarantees here):

Code: [Select]
luup.variable_set("urn:micasaverde-com:serviceId:ZWaveDevice1","LoadLevelTarget","XX","YY")
luup.variable_set("urn:micasaverde-com:serviceId:ZWaveDevice1","LoadLevelLast","XX","YY")

XX should be the percentage you want to set the dim level to and YY would represent the ID of the specific device.

Also, be advised that turning the lights back on "right away" will possibly not work because of a delay in Vera polling the switch to find out it has been turned off. So, the resetting of the dim value may take a short bit to be populated to the switch.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on May 31, 2018, 04:43:01 am
Create a scene that is triggered by the light being turned off. There is no immediate or delayed action, but you will need it to run a piece of LUA code to set LoadLevelTarget and LoadLevelLast to some value (same for both) which will become the lighting level when they are turned back on again.

The LUA code will need to be something like (this is off the cuff, so no guarantees here):

Code: [Select]
luup.variable_set("urn:micasaverde-com:serviceId:ZWaveDevice1","LoadLevelTarget","XX","YY")
luup.variable_set("urn:micasaverde-com:serviceId:ZWaveDevice1","LoadLevelLast","XX","YY")

XX should be the percentage you want to set the dim level to and YY would represent the ID of the specific device.

Also, be advised that turning the lights back on "right away" will possibly not work because of a delay in Vera polling the switch to find out it has been turned off. So, the resetting of the dim value may take a short bit to be populated to the switch.

Thanks for the suggestion.  In a pinch it would be a solution.  If I do that though then I do lose the function of the light switch that is enjoyed by those that understand how to turn the dimmer switches on and off.  If you set your light to 75% you should be able to tap it to turn it off and then tap it to turn it back on at the same level you had it at.  What I would rather do is make it an "if/then/AND" situation.  If someone dims the light down to below 5% to "turn it off" I'm going to assume that they just don't know how it functions so I'd like the possibility of IF the light is set to below 5% THEN turn the light off AND set the LoadLastLevel to XX.   I can get the first part of that in PLEG by creating the IF below 5% then do the action.  It's just that the action in PLEG gives me the option of turning it off using "LoadLevelTarget" but it does not give me the option to of "LoadLevelLast" even though that is in the list when I create the Device Input. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Tillsy on May 31, 2018, 05:30:42 am
Does your dimmer return wattage like Fibaro and Aeon devices?

If so turn your light down to the level you would like to trigger, say 5%, and check what Vera shows the wattage as (give it a while as power levels are generally only sent at intervals).

Then create scene, select your dimmer, and select "Energy usage goes below".  Key in your wattage from above.

Then you can enter your LUA code to be executed.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on May 31, 2018, 05:39:49 am
It does have a LoadLevelStatus.    This variable shows the percentage of dim that is is currently on.  So yes.  I have that ability to see where it is at.  What I do not know how to do is write code that says

If LoadLevelStatus <= 4  then Set LoadLevelStatus = 0  AND  Set LoadlevelLast = xx

Right now I'm trying to use PLEG.  In Pleg I can create the Device Property LoadLevelStatus (P1).  And then I can create the IF P1 <= 4 then (and this is where it gets funky because when I go to the action part of PLEG It does not have any of the same variables that the switch has but it does have LastLevelTarget) So I finish my PLEG with IF P1 <=4 then ACTION LoadLevelTarget = 0.  This turns the switch off when the dimmer is set to 4% or below.  I just need to figure out how to get the AND part of that to set the LoadLevelLast to a desired number.  And LoadLevelLast is not part of the Action options even though it's a device variable. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Don Phillips on May 31, 2018, 08:08:01 pm
In the action, you can add another instance of device so it appears twice.  Here is an example of my thermostat.

You should be able to set LoadLastLevel to XX and in the second instance, LoadLevelStatus to 0.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 01, 2018, 11:54:07 am
It does have a LoadLevelStatus.    This variable shows the percentage of dim that is is currently on.  So yes.  I have that ability to see where it is at.  What I do not know how to do is write code that says

If LoadLevelStatus <= 4  then Set LoadLevelStatus = 0  AND  Set LoadlevelLast = xx

Right now I'm trying to use PLEG.  In Pleg I can create the Device Property LoadLevelStatus (P1).  And then I can create the IF P1 <= 4 then (and this is where it gets funky because when I go to the action part of PLEG It does not have any of the same variables that the switch has but it does have LastLevelTarget) So I finish my PLEG with IF P1 <=4 then ACTION LoadLevelTarget = 0.  This turns the switch off when the dimmer is set to 4% or below.  I just need to figure out how to get the AND part of that to set the LoadLevelLast to a desired number.  And LoadLevelLast is not part of the Action options even though it's a device variable.

I think you have to make a choice here... either work with PLEG and the ease of use combined with the lack of deep flexibility (like this - combining variable settings with simple controls), or learn how to write code for programming to generate your own controls and events.

If you were to drop the PLEG routine you have all together, you could replace it with a single scene in VERA that would detect that the switch had been turned "way down" (less than 5%) and then turn it off AND change the settings. Otherwise, someone turning the switch off correctly would allow it to come back on at that level. This is a MUCH more elegant solution overall (IMHO) because the scene can be set with the trigger point literally being "less than 5%" and the action being the LUA code. A normal "OFF" event is ignored.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Tillsy on June 01, 2018, 09:07:06 pm
Or, how about this... does your dimmer have a configurable parameter for minimum and maximum brightness levels like Fibaro devices?

If so, set the minimum brightness to say 10%.

Then it won't even be possible for someone to dim it to the point where they "think" it is off, the lights will still be on at a very obvious level and then they still have to turn it off.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 02, 2018, 04:34:05 am
In the action, you can add another instance of device so it appears twice.  Here is an example of my thermostat.

You should be able to set LoadLastLevel to XX and in the second instance, LoadLevelStatus to 0.

Thanks Don.  I have tried this but the options in the ACTION drop down are not the same as the parameters of the device.  There is no LoadLevelLast in the drop down in the Action part of the PLEG.  When I create a Device Property and choose a dimmer I see all the parameters of that dimmer.  But by the time I get to the Logic Actions and then try to choose what action I want those same parameters are not there. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 02, 2018, 04:37:21 am
It does have a LoadLevelStatus.    This variable shows the percentage of dim that is is currently on.  So yes.  I have that ability to see where it is at.  What I do not know how to do is write code that says

If LoadLevelStatus <= 4  then Set LoadLevelStatus = 0  AND  Set LoadlevelLast = xx

Right now I'm trying to use PLEG.  In Pleg I can create the Device Property LoadLevelStatus (P1).  And then I can create the IF P1 <= 4 then (and this is where it gets funky because when I go to the action part of PLEG It does not have any of the same variables that the switch has but it does have LastLevelTarget) So I finish my PLEG with IF P1 <=4 then ACTION LoadLevelTarget = 0.  This turns the switch off when the dimmer is set to 4% or below.  I just need to figure out how to get the AND part of that to set the LoadLevelLast to a desired number.  And LoadLevelLast is not part of the Action options even though it's a device variable.

I think you have to make a choice here... either work with PLEG and the ease of use combined with the lack of deep flexibility (like this - combining variable settings with simple controls), or learn how to write code for programming to generate your own controls and events.

If you were to drop the PLEG routine you have all together, you could replace it with a single scene in VERA that would detect that the switch had been turned "way down" (less than 5%) and then turn it off AND change the settings. Otherwise, someone turning the switch off correctly would allow it to come back on at that level. This is a MUCH more elegant solution overall (IMHO) because the scene can be set with the trigger point literally being "less than 5%" and the action being the LUA code. A normal "OFF" event is ignored.

Thanks.  I agree.  I am just making sure I'm not missing something in trying to use the system or the plug in before I embark on becoming a computer programmer.  But if it is what must be done then I will have to.  Or maybe someone with LUA experience can just rattle it off their hip because they already have the experience.  :) 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 02, 2018, 04:39:54 am
Or, how about this... does your dimmer have a configurable parameter for minimum and maximum brightness levels like Fibaro devices?

If so, set the minimum brightness to say 10%.

Then it won't even be possible for someone to dim it to the point where they "think" it is off, the lights will still be on at a very obvious level and then they still have to turn it off.

Excellent suggestion.  There is no obvious parameter in the advanced settings for the dimmers to set a minimum but I can research it or contact the company to find out if there is a command that I can add.

Thanks!
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 02, 2018, 02:57:46 pm
It does have a LoadLevelStatus.    This variable shows the percentage of dim that is is currently on.  So yes.  I have that ability to see where it is at.  What I do not know how to do is write code that says

If LoadLevelStatus <= 4  then Set LoadLevelStatus = 0  AND  Set LoadlevelLast = xx

Right now I'm trying to use PLEG.  In Pleg I can create the Device Property LoadLevelStatus (P1).  And then I can create the IF P1 <= 4 then (and this is where it gets funky because when I go to the action part of PLEG It does not have any of the same variables that the switch has but it does have LastLevelTarget) So I finish my PLEG with IF P1 <=4 then ACTION LoadLevelTarget = 0.  This turns the switch off when the dimmer is set to 4% or below.  I just need to figure out how to get the AND part of that to set the LoadLevelLast to a desired number.  And LoadLevelLast is not part of the Action options even though it's a device variable.

I think you have to make a choice here... either work with PLEG and the ease of use combined with the lack of deep flexibility (like this - combining variable settings with simple controls), or learn how to write code for programming to generate your own controls and events.

If you were to drop the PLEG routine you have all together, you could replace it with a single scene in VERA that would detect that the switch had been turned "way down" (less than 5%) and then turn it off AND change the settings. Otherwise, someone turning the switch off correctly would allow it to come back on at that level. This is a MUCH more elegant solution overall (IMHO) because the scene can be set with the trigger point literally being "less than 5%" and the action being the LUA code. A normal "OFF" event is ignored.

Thanks.  I agree.  I am just making sure I'm not missing something in trying to use the system or the plug in before I embark on becoming a computer programmer.  But if it is what must be done then I will have to.  Or maybe someone with LUA experience can just rattle it off their hip because they already have the experience.  :)

I'm not a programmer by any stretch, but have written all of my own LUA. I start with a simple "If this is true, do that" sort of writeup. Then I add detail to each section until I have what I need.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 02, 2018, 03:11:37 pm
It does have a LoadLevelStatus.    This variable shows the percentage of dim that is is currently on.  So yes.  I have that ability to see where it is at.  What I do not know how to do is write code that says

If LoadLevelStatus <= 4  then Set LoadLevelStatus = 0  AND  Set LoadlevelLast = xx

Right now I'm trying to use PLEG.  In Pleg I can create the Device Property LoadLevelStatus (P1).  And then I can create the IF P1 <= 4 then (and this is where it gets funky because when I go to the action part of PLEG It does not have any of the same variables that the switch has but it does have LastLevelTarget) So I finish my PLEG with IF P1 <=4 then ACTION LoadLevelTarget = 0.  This turns the switch off when the dimmer is set to 4% or below.  I just need to figure out how to get the AND part of that to set the LoadLevelLast to a desired number.  And LoadLevelLast is not part of the Action options even though it's a device variable.

I think you have to make a choice here... either work with PLEG and the ease of use combined with the lack of deep flexibility (like this - combining variable settings with simple controls), or learn how to write code for programming to generate your own controls and events.

If you were to drop the PLEG routine you have all together, you could replace it with a single scene in VERA that would detect that the switch had been turned "way down" (less than 5%) and then turn it off AND change the settings. Otherwise, someone turning the switch off correctly would allow it to come back on at that level. This is a MUCH more elegant solution overall (IMHO) because the scene can be set with the trigger point literally being "less than 5%" and the action being the LUA code. A normal "OFF" event is ignored.

Thanks.  I agree.  I am just making sure I'm not missing something in trying to use the system or the plug in before I embark on becoming a computer programmer.  But if it is what must be done then I will have to.  Or maybe someone with LUA experience can just rattle it off their hip because they already have the experience.  :)

I'm not a programmer by any stretch, but have written all of my own LUA. I start with a simple "If this is true, do that" sort of writeup. Then I add detail to each section until I have what I need.

Yeah I'll just have to take some time to figure out how to write LUA code.  One of these days I'll work it in.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 03, 2018, 03:48:54 pm

Yeah I'll just have to take some time to figure out how to write LUA code.  One of these days I'll work it in.

It really shouldn't be all that difficult. Right now, PLEG is detecting when the dimmer drops down below 5%. Your action is to turn the dimmer off at that point. You could change that as follows:

- Create a virtual on/off switch
- Have PLEG turn the virtual switch on when the dimmer drops below 5% (instead of turning the light off)
- Create a scene that detects when the virtual switch is turned on
- - Immediate action is to turn the virtual switch off AND the dimmed switch off
- - LUA code sets the variables we've already talked about

Done.

If someone partly dims the switch and then turns it off, it will come back on at the last level it was dimmed to.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 03, 2018, 06:19:42 pm

Yeah I'll just have to take some time to figure out how to write LUA code.  One of these days I'll work it in.

It really shouldn't be all that difficult. Right now, PLEG is detecting when the dimmer drops down below 5%. Your action is to turn the dimmer off at that point. You could change that as follows:

- Create a virtual on/off switch
- Have PLEG turn the virtual switch on when the dimmer drops below 5% (instead of turning the light off)
- Create a scene that detects when the virtual switch is turned on
- - Immediate action is to turn the virtual switch off AND the dimmed switch off
- - LUA code sets the variables we've already talked about

Done.

If someone partly dims the switch and then turns it off, it will come back on at the last level it was dimmed to.

I think I'm missing something here.  As far as I can tell this has the same end result.  If someone sets the dimmer down to 4% it won't matter if there is a virtual switch or if PLEG just does the turn off action itself.  The second that person sets the switch to 4% the "LastLoadLevel" gets set to 4%.  If they go to turn the light on by just tapping the up on the paddle it will go back to the LastLoadLevel which is still 4% and it would just go into the constant off loop.  What I need is a way to tell the switch to set the LastLoadLevel to xx% if it is dimmed to 4% or lower be it by virtual switch or by a simple PLEG.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 08:19:48 am

Yeah I'll just have to take some time to figure out how to write LUA code.  One of these days I'll work it in.

It really shouldn't be all that difficult. Right now, PLEG is detecting when the dimmer drops down below 5%. Your action is to turn the dimmer off at that point. You could change that as follows:

- Create a virtual on/off switch
- Have PLEG turn the virtual switch on when the dimmer drops below 5% (instead of turning the light off)
- Create a scene that detects when the virtual switch is turned on
- - Immediate action is to turn the virtual switch off AND the dimmed switch off
- - LUA code sets the variables we've already talked about

Done.

If someone partly dims the switch and then turns it off, it will come back on at the last level it was dimmed to.

So I've tried this using ember1205 lua code suggestions to no avail.   The switch remains in a constant off loop if I dim it to 4% or less and then try to just turn it on.  Any suggestions on what the Lua code I should put into the scene should be to set the LoadLevelLastl to XX amount?

This:   luup.variable_set("urn:micasaverde-com:serviceId:ZWaveDevice1","LoadLevelLast","100","20")  didn't do it.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 04, 2018, 09:33:42 am
You're going to need to determine what your exact variable name is. For example, I have a dimmer that uses urn:upnp-org:serviceId:Dimming1 as the name of the variable to be set as "LoadLevelLast".

Also, unless you're able to successfully set that variable, you won't have the complete "solution" and things will work as you're describing.

To determine your exact variable name, open up the device. Click on Advanced. From there, click the Variables tab. Scroll down to find "LoadLevelLast" and hover your mouse over it. The pop up box will show you the correct naming.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 09:38:06 am
You're going to need to determine what your exact variable name is. For example, I have a dimmer that uses urn:upnp-org:serviceId:Dimming1 as the name of the variable to be set as "LoadLevelLast".

Also, unless you're able to successfully set that variable, you won't have the complete "solution" and things will work as you're describing.

To determine your exact variable name, open up the device. Click on Advanced. From there, click the Variables tab. Scroll down to find "LoadLevelLast" and hover your mouse over it. The pop up box will show you the correct naming.

Yes this is exactly the same name I get when I hover over it.  My device number is 20.  And The name of it is LoadLevelLast   I have no idea if these Jesco/GE dimmers allow it to be changed.  I've written the company... as you can imagine... still waiting.

If I put this in my LUA on my scene using he virtual switch as a trigger from PLEG and then try to run the scene.. it fails.

luup.variable_set("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","100","20")
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 04, 2018, 09:50:00 am
Try:

Code: [Select]
luup.variable_set("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","100",20)
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 10:26:35 am
Try:

Code: [Select]
luup.variable_set("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","100",20)

THANK YOU!!!  What a couple little quotation marks can do.  Although now I have the daunting task of creating a couple dozen virtual switches and PLEG devices BUT it gets the job done!   Much appreciated ember1205.  You rule the day!
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 04, 2018, 10:32:16 am
Glad it worked. I didn't immediately notice it because I do it just a little differently.

In my LUA code, I first set a variable like this:

Code: [Select]
DeviceID = 20
Then I send the command like this:

Code: [Select]
luup.variable_set("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","100",DeviceID)
So, my code doesn't end up with that number being quoted.

On another note... I also set global variables with my startup LUA. I will do things like this:

Code: [Select]
DiningRoomDimmerID = 5
LivingRoomDimmerID = 7
MasterBedroomDimmerID = 10
MasterBedroomFanID = 15

Since those variables are global, I can reference them anywhere and don't have to set them within the scenes. I can change the above command to something like:

Code: [Select]
luup.variable_set("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","100",MasterBedroomDimmerID)
And not have to declare that variable within the scene first.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 10:42:29 am
Very good.   I hope I don't run into issues with the number of devices.  I think the Vera 3 has a limit.  Or do virtual devices not count toward that?  Also, is there a way to update the controller after a PLEG change without having to reboot it?
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 04, 2018, 10:52:50 am
Everything has limits.  :)

My VeraLite has quite a few items in it and it's fine. I can't imagine the Vera 3 is more restrictive. Also, if you are adding LUA code directly to your PLEG items, you wouldn't need the virtual switches. You can act on the devices directly when you detect that you're at 4% dim or less.

Can't tell you much about PLEG because I've never used it. I always wrote my own code because it was much more flexible. And free.  ;)
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 11:06:23 am
Everything has limits.  :)

My VeraLite has quite a few items in it and it's fine. I can't imagine the Vera 3 is more restrictive. Also, if you are adding LUA code directly to your PLEG items, you wouldn't need the virtual switches. You can act on the devices directly when you detect that you're at 4% dim or less.

Can't tell you much about PLEG because I've never used it. I always wrote my own code because it was much more flexible. And free.  ;)

I did try to add the code into PLEG after I found it worked with the virtual switch but it did not fly.  Not sure why.  I'll probably play with it some more as I find the time but this will work for now and the summer rental season is upon me and I don't like to play around with the Vera while that is going on.  Cause you just never know and I'm not near it to fix it.  I don't do updates during that time... and actually after the last update I won't do them anymore until I update my controller.  Everytime I have to back up, then reset the controller back to factory, do the update and then restore.  I'm not there so this was always nerve racking.  I solved it by having a web enabled power strip, a camera and a mini computer all in the cabinet with my controller.   After I backed up, and then factory reset I'd loose all my inet configuration (wifi) so I'd turn on the mini pc which was then bridged with the vera and I could then configure the wifi settings again.  But I was just there before the season with the most recent update and even with me there it didn't go well.  Backup failed, called support, they were in the unit for quite some time but finally got it but the back up they used was old so lost everything i had done the prior 4 days and didn't want to take a chance so I just reconfigured the whole damn thing and then said no more of that.  So next year I'll upgrade to a new model so I can avoid that whole mess because of lack of space. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 04, 2018, 11:28:35 am


I did try to add the code into PLEG after I found it worked with the virtual switch but it did not fly.  Not sure why.  I'll probably play with it some more as I find the time but this will work for now and the summer rental season is upon me and I don't like to play around with the Vera while that is going on.  Cause you just never know and I'm not near it to fix it.  I don't do updates during that time... and actually after the last update I won't do them anymore until I update my controller.  Everytime I have to back up, then reset the controller back to factory, do the update and then restore.  I'm not there so this was always nerve racking.  I solved it by having a web enabled power strip, a camera and a mini computer all in the cabinet with my controller.   After I backed up, and then factory reset I'd loose all my inet configuration (wifi) so I'd turn on the mini pc which was then bridged with the vera and I could then configure the wifi settings again.  But I was just there before the season with the most recent update and even with me there it didn't go well.  Backup failed, called support, they were in the unit for quite some time but finally got it but the back up they used was old so lost everything i had done the prior 4 days and didn't want to take a chance so I just reconfigured the whole damn thing and then said no more of that.  So next year I'll upgrade to a new model so I can avoid that whole mess because of lack of space.

IMHO, the way VERA pushes the firmware upgrades, requiring a factory reset, is an AWFUL process. What's worse is that the pages they link you to on how to do it don't actually give you all of the steps that are required. I've done it remote on my controller once, and it was pretty nerve-wracking. I took a slightly different approach, though. I did a full backup of the controller and ensured I had the copy of everything downloaded. Then I stripped out devices by hand until most of it was gone and there was enough room for the upgrade. The upgrade was pushed through, and then I restored a backup to put everything (including the Z-Wave network) back.

It is an abomination of a process and really needs to be addressed by VERA.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 04, 2018, 11:36:44 am


I did try to add the code into PLEG after I found it worked with the virtual switch but it did not fly.  Not sure why.  I'll probably play with it some more as I find the time but this will work for now and the summer rental season is upon me and I don't like to play around with the Vera while that is going on.  Cause you just never know and I'm not near it to fix it.  I don't do updates during that time... and actually after the last update I won't do them anymore until I update my controller.  Everytime I have to back up, then reset the controller back to factory, do the update and then restore.  I'm not there so this was always nerve racking.  I solved it by having a web enabled power strip, a camera and a mini computer all in the cabinet with my controller.   After I backed up, and then factory reset I'd loose all my inet configuration (wifi) so I'd turn on the mini pc which was then bridged with the vera and I could then configure the wifi settings again.  But I was just there before the season with the most recent update and even with me there it didn't go well.  Backup failed, called support, they were in the unit for quite some time but finally got it but the back up they used was old so lost everything i had done the prior 4 days and didn't want to take a chance so I just reconfigured the whole damn thing and then said no more of that.  So next year I'll upgrade to a new model so I can avoid that whole mess because of lack of space.

IMHO, the way VERA pushes the firmware upgrades, requiring a factory reset, is an AWFUL process. What's worse is that the pages they link you to on how to do it don't actually give you all of the steps that are required. I've done it remote on my controller once, and it was pretty nerve-wracking. I took a slightly different approach, though. I did a full backup of the controller and ensured I had the copy of everything downloaded. Then I stripped out devices by hand until most of it was gone and there was enough room for the upgrade. The upgrade was pushed through, and then I restored a backup to put everything (including the Z-Wave network) back.

It is an abomination of a process and really needs to be addressed by VERA.

Yes this last time the support guy told me about the deletion of apps and devices but really.. is that any less nerve racking for me?  No.  MORE time consuming... Yes.  I think the way they are addressing it is... upgrade your old controller.  Which I get.  I mean phones, computers, anything that has constant evolution will eventually be outgrown by it's software counterparts.  However, they could have taken the time to automate the issue all the while giving a warning that this or that will cease to be supported on a given date so we have time to plan for it.  But it is what it is.  I'm good not updating.  I just need it to work along like the workhorse it's always been.  And thanks for the help.  It would have taken me days to figure out that it was just two quotation marks.  That's why I love the forum.  Smart people like you with experience.  Hopefully someday I'll be able to help someone too.  Hell just by reading this it will help someone.  Thanks again.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on June 05, 2018, 04:07:21 am
I think the way they are addressing it is... upgrade your old controller. 

The problem is that for example Plus has less storage space than Edge, (I'm not talking about RAM, but about the room where system files are stored) and as such "upgrading" may be in fact a "downgrade" in terms of stability and reliability.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 05, 2018, 04:21:33 am
I think the way they are addressing it is... upgrade your old controller. 

The problem is that for example Plus has less storage space than Edge, (I'm not talking about RAM, but about the room where system files are stored) and as such "upgrading" may be in fact a "downgrade" in terms of stability and reliability.

Plus has less storage space?  Other threads on here contradict that.  How much less space?  Do people with a new Plus or Edge have to reset to factory default before updating?  That's all I care about.  I'm over doing that it with my beloved Vera 3
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on June 05, 2018, 05:24:23 am
The question is what memory we are talking about.
If you ssh to Vera and run "df -h" command, or run this command via AltUI OS.Command section, you'll see following results (look for "rootfs", "/dev/mtdblock7" and "overlayfs:/overlay" sections, as too much memory used here causes "no space left on device" error and problems with firmware upgrade or other issues):

For Vera PLUS rootfs, /dev/mtdblock7 and overlayfs:/overlay sections report size of 8,6MB, while for Vera Edge reported size is 9,4MB.
And this makes a difference of 800KB, which is about 10% of your total memory.

In practice, the same setup (restored from the same backup file) on Plus gives me memory filled in about 90%, while on Edge it is around 72%.
I don't know why the difference is bigger than it should be when you compare just amounts of total memory of both controllers. Probably Edge needs less system files (i.e. no Zigbee or Bluetooth files) and this gives some additional space.

Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on June 05, 2018, 05:32:16 am
The question is what memory we are talking about.
If you ssh to Vera and run "df -h" command, or run this command via AltUI OS.Command section, you'll see following results (look for "rootfs", "/dev/mtdblock7" and "overlayfs:/overlay" sections, as too much memory used here causes "no space left on device" error and problems with firmware upgrade or other issues):

For Vera PLUS rootfs, /dev/mtdblock7 and overlayfs:/overlay sections report size of 8,6MB, while for Vera Edge reported size is 9,4MB.
And this makes a difference of 800KB, which is about 10% of your total memory.

In practice, the same setup (restored from the same backup file) on Plus gives me memory filled in about 90%, while on Edge it is around 72%.
I don't know why the difference is bigger than it should be when you compare just amounts of total memory of both controllers. Probably Edge needs less system files (i.e. no Zigbee or Bluetooth files) and this gives some additional space.
But at least you can do an update without resetting.  That's all I care about.  I don't know why I'd go with the Plus anyway since I don't use zigbee or bluetooth.  I can't imagine the speed is all that much different for what I need them to do.  The Vera 3's speed is fine and it doesn't have the capacity of either.  The Secure seems like way to much money for not a lot of benefit.  I don't know, maybe the speed of the Plus and Secure is noticable?
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on June 05, 2018, 07:47:30 am
But at least you can do an update without resetting.  That's all I care about. 

That's not that obvious as it depends on your setup. Some people report having issues with "no space left on device" error on Plus, I don't remember if Edge is also affected.
I had an issue where my controller upgraded, OK, but had issues after that upgrade. I couldn't do factory reset due to lack of space on the controller - I couldn't access it remotely, when accessed locally I couldn't force factory reset from the menu ("insufficient rights"). When I did reset via reset button controller was exclueded from my dashboard, but after re-attaching it I found that all configuration still remain as before "reset".
It took me half a day to finally wipe all data, but then, after restore it I've had other issues with it.
So, basically, no, you can't be sure that you'll be able to do an update without resetting.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 05, 2018, 09:40:14 am
The question is what memory we are talking about.
If you ssh to Vera and run "df -h" command, or run this command via AltUI OS.Command section, you'll see following results (look for "rootfs", "/dev/mtdblock7" and "overlayfs:/overlay" sections, as too much memory used here causes "no space left on device" error and problems with firmware upgrade or other issues):

For Vera PLUS rootfs, /dev/mtdblock7 and overlayfs:/overlay sections report size of 8,6MB, while for Vera Edge reported size is 9,4MB.
And this makes a difference of 800KB, which is about 10% of your total memory.

In practice, the same setup (restored from the same backup file) on Plus gives me memory filled in about 90%, while on Edge it is around 72%.
I don't know why the difference is bigger than it should be when you compare just amounts of total memory of both controllers. Probably Edge needs less system files (i.e. no Zigbee or Bluetooth files) and this gives some additional space.

Apologies if this comes off as pedantic.. But memory and storage are two totally different things. I like to describe storage as the filing cabinet in the corner or the drawers in your desk - it's where you "put things away" so that you can get to them later. Memory is akin to the size of the top of your desk. How much memory you have (RAM) is directly related to how many things you can take out of the drawers and lay out on the desktop at any given time. Swapping is like having to remove a piece of paper from the desktop and putting it in a drawer so that you have room to pull a different piece of paper out and lay it on the desk.

"df -h" is a command to check STORAGE.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on June 05, 2018, 01:02:20 pm
I'm not really familiar with naming.
Vera tells about Flash Memory (128MB for all current controllers) and just Memory (depending on the controller, from 128 to 512MB).

df -h command gives status of Flash Memory, I guess. But I'm not sure as in Plus case it doesn't sum up to 128MB, but rather to about 200MB
Nevertheless, the problem is not the total amount of Flash Memory (Storage?), but sections reserved for system files (folders mentioned by me in some post above).
Here you have limited space of 8,6MB (Plus) or 9,4MB (Edge) which can be easily overfilled.
The "Memory" (RAM?) part unfortunately can also be issue and lack of this memory was most probably the reason for bricking my previous controller in a way that even Customer Care couldn't revive it.


Title: Re: Help with turning off dimmer when light hits 1%
Post by: HSD99 on June 05, 2018, 08:16:38 pm
Don't feel bad---this is an issue usually reserved for Linux system admins.  Linux commands are just like their Unix predecessors--information dense, but not friendly if you don't know what you're looking at. Embedded Linux systems use FLASH memory as the "disk drive", the permanent storage that retains data even when the power is off. "Memory" is RAM (Random Access Memory) which may be written and read as often as desired at very high speed, but does not retain data when the power is off.

FLASH memory in embedded systems has limitations on how often it may be read and written before damage occurs to the memory cells. FLASH memory controller chips or system software is supposed to be responsible for "wear-leveling" to keep track of which blocks are used and to spread the workload across all the blocks. Good system software design tries to avoid reading and writing the FLASH as much as possible.

To help this problem, Linux has software, tempfs,  that can use a portion of the RAM as a filesystem. Programs use this instead of the FLASH for temporary files. When Vera boots, all the operational code is copied from FLASH into RAM, and runs from there. Temporary files are created in the tempfs in RAM.

Vera Plus seems to allocate 50% of the RAM (128MB of 256MB total) to the tempfs. This is pretty typical for an embedded Linux system of this complexity. That leaves 128MB of RAM for all of the running code, plus buffers and scratchpad use,unless something goes wrong and an out-of-control process fills up the RAM. 128MB of RAM should be plenty under normal use, and the tempfs can be adjusted to be any size desired, if more RAM is needed.

My production VP shows this in response to the "free" command, which shows RAM use:

             total         used         free       shared      buffers
Mem:     255492    114868     140624       0        10308
-/+ buffers:           104560     150932
Swap:            0            0            0

114MB is in use, with 140MB free. This is the RAM, not the FLASH.

If you run the "du -h" command, it will show you everything in the FLASH filesystem with totals. Mine shows 119MB used. There is also a boot loader stored in the FLASH that does not show in the Linux filesystem since it isn't part of it, but does take space on the FLASH chip. If the FLASH chip is 128MB, then it's pretty full.

If we run the "df -h" command, we'll see free space in the filesystem. The first thing to note is the 128MB of tempfs, which is RAM, not FLASH. But it is part of the filesystem and is displayed in this command.

The entries for devices, e.g /dev/mtdblock10 are parts of the FLASH memory, our "disk." The devices are in turn mounted on the filesystem, for example /etc/cmh-firmware. This is how the physical device is connected to the logical device.

Here's my overlay filesystem:

overlayfs:/overlay        8.6M      5.8M      2.9M  67% /

This is after weeding out unused plug-in files, and the 2+MB of regional Z-wave HEX files.

I have no idea why Vera has such small partitions, or why they can't make the install script check before it gets into trouble, and clean up extraneous files. I took a quick look at the file system and it looks like there is a bunch of OpenWRT OS stuff that may not be needed for Vera. Perhaps they should take a look at that...

I see that akbooer has given you a script to check on the free space on /overlay. Kudos to him, and I hope it helps your system.
 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: ember1205 on June 05, 2018, 08:20:04 pm
I have no idea why Vera has such small partitions, or why they can't make the install script check before it gets into trouble, and clean up extraneous files. I took a quick look at the file system and it looks like there is a bunch of OpenWRT OS stuff that may not be needed for Vera. Perhaps they should take a look at that...


What's worse is why Vera insists on using these crazy small areas of disk to store files temporarily during an upgrade. They KNOW the limitations of their filesystem setup, yet they don't afford you the opportunity to use a different area of storage purely for the upgrade process.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on June 06, 2018, 09:17:28 am
I see that akbooer has given you a script to check on the free space on /overlay. Kudos to him, and I hope it helps your system.


I hope so.
I also did a major clearing of the remains from uninstalled plugins (I don't understand why these files are kept and saved in backups even if plugin is removed) and probably go for removing regional z-wave files as well. The question is what in case of upgrade - as I understood, regional z-wave files will be recreated at that time and my concern is what will happen if the space will be already stuffed?

Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on November 20, 2018, 10:51:02 am
Sorry been away for a while.  So let me get this straight.  If I upgrade to a Vera Plus in 2019, when I get the prompt to do an upgrade I could still get a message that tells me there is not enough disk space to do the upgrade?  That's wack.  Wiping the controller and restoring a backup everytime there is a software update makes ZERO sense. 
Title: Re: Help with turning off dimmer when light hits 1%
Post by: kwieto on November 20, 2018, 03:55:14 pm
Hard to tell.
Fist, it depends of your setup. In my case I don't need to reset Vera to make upgrade, but I have to tweak it a little afterwards to avoid having issues with storage space. Depending on how big is your setup and how many plugins you use, you may encounter the problem or not.
Second, there is a lot of things happening at Vera currently. It was taken over by Ezlo, and the new owner declares improving a lot of things. Since lack of storage memory is known and affect many users, I suppose that it will be addressed.
For now we are waiting what will happen in the near future, and there was no new firmware upgrade yet since takeover.
Title: Re: Help with turning off dimmer when light hits 1%
Post by: Greybeardvacationrental on November 26, 2018, 09:50:22 pm
Thanks.   I did contact support who came in and looked at my setup.  He assured me I should have no issue upgrading with my current setup.  I will take that with optimistic skepticism.  LOL