Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


ErnstH

Member
  • Posts

    69
  • Joined

  • Last visited

1 Follower

About ErnstH

Profile information

  • Gender
    Male
  • Country
    the Netherlands
  • Gateway/s
    Home Center 2

Recent Profile Visitors

214 profile views

ErnstH's Achievements

Learner

Learner (2/8)

3

Reputation

  1. Hi @Sankotronic The scene seemed to be working fine. And as i eplied rebooting seemd to settle it. However, I just saw that in the debug message area there is still that the message: Missing global variable for Time Of Day - Day of week is (..) Missing global variable for Season and/or Month Now that I looked deeper into it I noticed that in function doTimeOfDay() timeOfDay is not starting with a capital, while the defined Global variable is. So shouldn't it be TimeOfDay with a capital? The same for Season and Darkness. I tried to test it by changing nly TimeOfDay. Then this message disappeared, but some lines further now there is this message: [DEBUG] 21:09:00: 2023-08-24 21:09:00.644549 [ error] timer handler failed with error: /opt/fibaro/FibaroSceneAPI.lua:155: Assertion failed: Expected string That doesn't make sense (reported error lines are often wrong in my experience): line 155 is about local luxGlo: 153 -- or you can setup global variables names that are set by other light sensors 154 -- for example {"LuxGarden","LuxShade"} 155 local luxGlo = {} 156 local luxLevelmin = 100 157 local luxLevelmax = 300 So, in summary, could it be an issue that referral to some global variables is not Capitalized? And how do I solve this new error message?
  2. Hi Sanko, i'm using your wonderful script for this home scene for years, and it was working perfect. However, since a few months, trigger times have been disturbed, and I found out in the debugging area that several variables are reported as missing: Missing global variable for Time Of Day - Day of week is Vrijdag Missing global variable for Season and/or Month I don't know why, I haven't change anything for 2 years. In the variables panel the variables do exist, although Season wasn't right. Running the scene or VD's doesn't help. Do you have any suggestion how to solve this?
  3. Hi all, I'm trying to have a graphical view of the lux value of a fibaro cateye sensor. This is in order to find a proper cut-off for a scene trigger. The values can be seen in log panels. Does anyone have a suggestion how to get these values into a graph?
  4. About users, another question. Is there a scene to find out if all users are at home or not, defined by proximity (GPS)? I couldn't find it.
  5. Hi, Is this still true? Isn't there a way to do this automatically with a script (scene)? To do this manually for several users is annoying and may lead to errors due to omissions.
  6. Thanks. I already thought and hoped so, for that text and the referred name were different
  7. Hi Sankotronic and others, Beautiful work, thanks! What I don't understand in the quoted code, is when the scene ID is referenced to, why there is a need in the previous line to use the name of the scene. What does that name add? And it seems that the name "Weekly battery check" is different than the true name "Batt_check" of the scene. Is the name "Weekly battery check" actually a name that can be chosen freely? My HomeTable doesn't have the scene ID's in it, unless it is defined at the beginning of the code of HomeTable. I couldn't find an updated version of HomeTable that includes all ID's (but maybe there isn't). Referring to a scene with jT.scene. seems the preferable way, but in my case only works when I defined it initially.
  8. Hope so, getting curious...?
  9. Hi 10der, Looks good though quite complicated. But I understand it. I pasted it into my script and it returns an error, that hmstr seems to be undefined yet: [DEBUG] 20:46:20: nil nil [DEBUG] 20:46:20: 2020-08-11 20:46:20.915000 [ fatal] Unknown exception: /opt/fibaro/scenes/5.lua:47: attempt to index local 'hmstr' (a nil value). Shouldn't that as well as margin be defined before the function? Nearly there I guess...
  10. That's okay, that's what forums should do sometimes. ? Meanwhile, my question remains unresolved.
  11. Thanks for the suggestion. I looked into that. Not just what I'm looking for, it is code I already have. Just displaying sunset time. Not with a calculation. I think I need something like os.date("%H:%M", os.time() = sunsetHour - tonumber(BeforeSunset)*60). But I need a better syntax. maybe, but how do I open or import this type of file?
  12. That is not the problem. I do have such a code: if os.date("%H:%M", os.time()+tonumber(BeforeSunset)*60) == sunsetHour This works fine. But I want it the other way around: with a print of debug command I want to display the time lamps go on today. Thanks for trying to help.
  13. Hi all, I would like to display a debug message with the time of sunset + an x amount of minutes. So there needs to be a calculation. I have a few scenes whose start is dependent of the month, turning lights on earlier or later. My debug message should be something like "today lights will be on at 21:15". That 21:15 is the calculated time. I have these declarations at the start of scenes: local sunsettime = fibaro:getGlobalValue("SunsetTime"); local sunsetHour = fibaro:getValue(1,'sunsetHour') But I can't figure out how to do this. Shouldn't be very complicated, but i'm not good in LUA programming with time. Hope someone can help me out.
  14. Where do I find the frequency of my system?
  15. Thanks, found it (more precise, the products are here: https://www.silabs.com/search#q=ACC-UZB3&t=Products&sort=relevancy) 25$ is not too expensive, so I'll give it a try. Googling for ACC-UZB3 I found that these can be bought at several sites. In the meantime I'll rewrite some scenes adding sleep for 100ms.
×
×
  • Create New...