Welcome to Smart Home Forum by FIBARO
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!
Smart Home Forum by FIBARO Team
Search the Community
Showing results for tags 'error reporting'.
Found 2 results
QA stop(script problem) but not print error problem [SOLVED]
jwetzel posted a question in Home Center 3I have a weird behavior with my HC3. When I make an error in my code, the program stops but there is no error showing in the console. After a few seconds, it automatically restarts the program. It only shows me parentheses errors, "end" missing or = missing or handlejson error. But nothing else. It also often happens that the HC3 is no longer accessible for several minutes following an error without it being a loop problem. And still without displaying an error in the console. Is it normal ? Thanks for your help.
Error reported seems incorrect or unexpected
AutoFrank posted a question in Scenes and InterfaceHI, I'm reasonably sure I did't see this prior to 4.120 With the following code if (tonumber(os.date("%w")) > 0 and tonumber(os.date("%w")) < 6 and fibaro:getGlobalValue(schoolState) == schoolStateMapping.No then fibaro:debug("Info: Running weekday and no school main code sequence..") buildMsg() weekdayOff() MumDadGreeting() return end I am getting the following error The problem is typo and I have one too many parenthesis (just after the if) It is reporting the correct line # but I thought that prior to 4.120, this would have been reported as something like "expected ( after blah' or 'expected then after blah' Perhaps it was always there but it seems like a poor description for what was actually wrong in the code Thoights -f