[SCENE] Main scene FTBE v1.3.4

[Sankotronic 2,093]

Main scene FTBE v 1.3.4

 

Hello everyone!

 

NEW version is OUT!

 

More about scene and download you can find here:

 

WHAT'S NEW:

 

• Main scene FTBE 1.3.4 - changed function for time of day calculation and added use of SleepState global to set time of day to morning when Awake  regardless of current time
• Main scene FTBE 1.3.0 - cleaned some bugs, added some more checks to prevent scene from stop running due to errors. Optimized and compacted code, removed unnecessary comments. DemoMode only stops changing timers while user code and scheduled events will continue to execute. Darkness can now be changed by measured lux level or global variable that is set to lux value measured by light measuring devices placed outside. Scene is now running on setTimeout function instead on sleep for better timing and also aligns to 0 seconds or exact minute.
• Sunrise & Sunset VD v1.4.0 - Modified main loop code to better handle global variables. Variables are now automatically repaired and are not reset to default settings after HC2 reboot. Added variable SunriseIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically.
• Home Status VD v1.1 - Added variable HomeStatIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically. Added label that shows most important values on VD when closed.
• Home Timers VD v1.1 - Added variable HomeTimersIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically. Added label that shows most important values on VD when closed.

 

 

Please login or register to see this attachment.

 

 

NOTE - This version is compatible with previous versions so need to do any changes in your current code of other scenes and VD's.

 

REQUEST - If you like my work and found it useful please give me support by rating and writing short review. Thank you!

 

PS

Dear friends from Slovakia you can find this scene and VD translated to your language here: 

Please login or register to see this link.

 

 

Edited December 30, 2019 by Sankotronic
Updated to new version

[Sankotronic 2,093]

29 minutes ago, jompa68 said:

I found blind time in this VD, how do you use that and how-to setup in you main scene?

 

Hi @jompa68,

 

I removed blinds control from Sunrise & Sunset VD in new version I'm testing now since I'm making separated controls for blinds that should be easy for users to setup regardless of number of rooms and blinds. Of course for that one I will need testers since I have six blinds only in living room and dining room. I plan to add more in future but first things first.

[Flash226 3]

I have a problem with the main scene. Every day I get this error and the scene does not work anymore.

Please login or register to see this attachment.

 

The scene is very convenient for me. What can I do to make it work?

 

[Sankotronic 2,093]

10 minutes ago, Flash226 said:

The scene is very convenient for me. What can I do to make it work?

 

 

Hi @Flash226,

 

Try not to use SAVE button in variable panel until I release new version of the scene. Pressing button in variable panel unfortunately destroys values of some of the global variables and that makes scene to stop with error. To correct global variables you need to open Sunrise & Sunset VD for editing and press save button there. It will rebuild variables but you will have to adjust times after that.

 

New version of Main scene and Sunrise & Sunset VD will not have that problem anymore. I'm working hard to finish new version that will have some nice features that you can check here:

 

[MarcoT 2]

Hello,

 

this evening my variable timeofday automaticaly switched to "night" even before 22:00. In the VD Timers v1.0.1 I switched timeofday back to "evening" manually but it moved to "night"  approx 10 sec.later.

Any idea what  went wrong?

Usually time of day switches to "night" after 0:00

 

Thanks Marco

[Sankotronic 2,093]

7 hours ago, MarcoT said:

Hello,

 

this evening my variable timeofday automaticaly switched to "night" even before 22:00. In the VD Timers v1.0.1 I switched timeofday back to "evening" manually but it moved to "night"  approx 10 sec.later.

Any idea what  went wrong?

Usually time of day switches to "night" after 0:00

 

Thanks Marco

 

Hi @MarcoT,

 

Check settings in Sunrise & Sunset VD and status of SleepState.

[MarcoT 2]

Hi @Sankotronic,

 

The sleepstate is "awake" an the settings in Sunrise & Sunset VD you find in the attached screenshot.The settings looking OK and have not been changed.

 

Thanks

Marco

 

Please login or register to see this attachment.

[Sankotronic 2,093]

3 hours ago, MarcoT said:

Hi @Sankotronic,

 

The sleepstate is "awake" an the settings in Sunrise & Sunset VD you find in the attached screenshot.The settings looking OK and have not been changed.

 

Thanks

Marco

 

 

Well then, what happened at that time when TimeOfDay was changed to Night? Something was changed at that time so logic, which never mistakes, changed it to Night.

 

Oh, you can change TimeOfDay to other time with Home Timers VD, but if Demo mode is not turned On then scene will set it back to the time defined by settings on next run.

[MarcoT 2]

Hi @Sankotronic 

when it set the Demo mode  "on" and change manually the status of TimeOfDay to "evening" it stays at evening. but directly after switching the Demo mode off, TimeOfDay change to night.

 

I watched the state of TimeOfDay tonight and it changed from day to night immediately.

After disabling the Main scene for time based events the variable TimeofDay stays at "evening".

I didn't change anything in all configuations before this behaviour occurred.

 

I already removed the variable TimeOfDay and created a new one but this even did not change anything.

Is there any way to find out which script change the state of a variable?

 

Thank you

Marco

[Sankotronic 2,093]

24 minutes ago, MarcoT said:

when it set the Demo mode  "on" and change manually the status of TimeOfDay to "evening" it stays at evening. but directly after switching the Demo mode off, TimeOfDay change to night.

 

Hi @MarcoT,

 

That part is then working as expected. Demo mode with Home Status and Home Timers VD is provided for testing.

 

26 minutes ago, MarcoT said:

I watched the state of TimeOfDay tonight and it changed from day to night immediately.

After disabling the Main scene for time based events the variable TimeofDay stays at "evening".

I didn't change anything in all configuations before this behaviour occurred.

 

Problem is that you set night time to start at midnight. Midnight is "00:00" what is then less or smaller than sunsettime and that is why day goes directly to night time. Try to set night to start at "23:59" and then there will be evening time. If you want night to start at midnight or even later then script has to be changed. I just didn't predict that there will be anyone to set night to start after 23:59. Thanks for pointing this out. In new version I will do smarter script with better checks and more liberty with settings.

 

[MarcoT 2]

Hi @Sankotronic

That's it. Great job!

I'm really looking forward to the new version.

 

Thank you

Marco

[ErnstH 3]

Hi, new problem...

After exclusion and re-inclusion of some devices I decided to use the HomeTable. Seems convenient and works fine.

however, in a virtual device which has a few buttons and sliders, the buttons work fine but the sliders do not. And I get these error messages when I test in debug of the sliders or buttons:

[ERROR] 17:25:57: line getGlobalValue("HomeTable"))..."]:49

49 is 27 in other occasions.

I removed all references to the HomeTable (so it is just as before I introduced HomeTable, but the error messages keep appearing in debug.

Any ideas what could be wrong? Thanks for suggestions.

[Sankotronic 2,093]

1 hour ago, ErnstH said:

Hi, new problem...

After exclusion and re-inclusion of some devices I decided to use the HomeTable. Seems convenient and works fine.

however, in a virtual device which has a few buttons and sliders, the buttons work fine but the sliders do not. And I get these error messages when I test in debug of the sliders or buttons:

[ERROR] 17:25:57: line getGlobalValue("HomeTable"))..."]:49

49 is 27 in other occasions.

I removed all references to the HomeTable (so it is just as before I introduced HomeTable, but the error messages keep appearing in debug.

Any ideas what could be wrong? Thanks for suggestions.

 

Hi @ErnstH,

 

Can you post code from slider?

 

[ErnstH 3]

Below is my code.

I entered it step by step, first using Id numbers, later selfId and the hometabel references.

It seems to work fine.

Then I removed all comments and debugs, and then it goes wrong. Why?

 

local debug = true
local jT = json.decode(fibaro:getGlobalValue("HomeTable"))

--fibaro:debug('ID = '..fibaro:getSelfId())
local selfID = fibaro:getSelfId()
if debug then fibaro:debug('ID = '..selfID) end
local LfGewenstePositie =
    --tonumber(fibaro:getValue(159, "ui.Slider1.value"))
    tonumber(fibaro:getValue(selfID, "ui.Slider1.value"))
if debug then
    fibaro:debug('eindpositie = '..LfGewenstePositie)
end

--fibaro:call(125, "setValue", LfGewenstePositie)
fibaro:call(jT.Serre.Luxaflex, "setValue", LfGewenstePositie

 

After stripping, it is like this, and then the errors comes in:

local selfID = fibaro:getSelfId()
local LfGewenstePositie =
    tonumber(fibaro:getValue(selfID, "ui.Slider1.value"))
fibaro:call(jT.Serre.Luxaflex, "setValue", LfGewenstePositie)

 

Hope you'll find it....

[Sankotronic 2,093]

Hi @ErnstH,

 

Try this code:

Please login or register to see this code.

 

[ErnstH 3]

Brilliant, that works!

 

I still don't understand why the other code didn't do it, but I'm fine with this one.

Thanks, Sankotronic!

[Sankotronic 2,093]

If above code you posted is correctly copied then in stripped version you stripped too much and removed line where you are getting HomeTable:

Please login or register to see this code.

That line must be in each code of each button, slider, main loop and scene where you need reference to the devices.

[ErnstH 3]

Simple. By editing I deleted that I'm afraid.

Now I need to find out how to adjust the slider when the blinds have been changed by another command.

I suppose need to put that in the main loop.

[Sankotronic 2,093]

28 minutes ago, ErnstH said:

Simple. By editing I deleted that I'm afraid.

Now I need to find out how to adjust the slider when the blinds have been changed by another command.

I suppose need to put that in the main loop.

 

You can use this code to change slider value:

Please login or register to see this code.

First one is also executing code for the slider so if you want only to update position of the slider then use second one. When you test code, use mobile app to check because changing slider value or position is not properly updated on the web GUI interface! It is shown only after refreshing page in browser.

[ErnstH 3]

Both don't work. I put it in de Main Loop.

Shouldn't I first need to state a definition of id and position?

Moreover, I have 2 sliders: one for up and down and one for turning the blinds.

I'll be back tonight.

[Sankotronic 2,093]

On 5/11/2017 at 7:06 AM, ErnstH said:

Both don't work. I put it in de Main Loop.

Shouldn't I first need to state a definition of id and position?

Moreover, I have 2 sliders: one for up and down and one for turning the blinds.

I'll be back tonight.

 

Hi @ErnstH,

 

Those above are examples and of course you need to define id and give some value between 0 and 100. If you put code in Main loop then it can look something like this:

Please login or register to see this code.

In above code you need to change ui.Slider1.value if your slider has different ID, jT.living.blinds1 with reference to your desired device which value you want to put on slider.

Remember, slider position will not show correctly in web GUI interface after it is updated with main loop, only after you refresh page. Also if you move slider to a new value it will jump back, depending on the time needed for blinds to reach desired position. Also in above example loop will execute every 3 seconds "fibaro:sleep(3000)". 

Edited May 13, 2017 by Sankotronic
Rectified code