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


sve

Member
  • Posts

    48
  • Joined

  • Last visited

About sve

Profile information

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

Recent Profile Visitors

83 profile views

sve's Achievements

Learner

Learner (2/8)

1

Reputation

  1. Same issue here getGlobalValue or the value of a sensor return "nil" after the update I have made some quick solution with the following: while fibaro:getValue(Sensor, "value") == nil do --Something end off course change Sensor to whatever you like, this solves 99% of the nil values because it only happens every now and then. Next to that I have a fail-safe scene to check other scenes: --[[ %% properties %% autostart %% globals --]] local SceneIDTable = {19,25,183,186} local SceneIDName = {"Woonkamer","Keuken","Zolder","HALBG"} while true do for i=1, #SceneIDTable do SceneIDCount = fibaro:countScenes(SceneIDTable[i]) if SceneIDCount == 0 then fibaro:debug("Scene "..SceneIDTable[i].." "..SceneIDName[i].." not running, restarting") fibaro:call(273, "sendPush", "Scene "..SceneIDTable[i].." "..SceneIDName[i].." not running, restarting") fibaro:startScene(SceneIDTable[i]) end end fibaro:sleep(30*1000); end although dirty it does the job Anybody else solved the nil issue without workarounds such as this?
  2. use a second scene to stop and start this scene based on the time or place a time based loop around this scene
  3. as mentioned above... works as a charm. I have two version 1 dimmers and a quibino dimmer wired as stated in the manual except the switch.
  4. you'll have to program that in Pimatic. In short: read the breached value of the sensor and then turn the light(s) on for a certain amount of time Do think good about what your doing, if there is no switch and your controller or PIR is not working there is no way to turn the light on easily...
  5. Here u go Make sure the scene's that you check have the %% autostart definition otherwise you might end up that unwanted scene's are restarting... The table "SceneIDTable" contains the id's of the scene's that you want to check for running, if they return "0" the scene is restarted and sends some output to the debug screen to let you know what has happend I hope you can make good use of the code --[[ %% autostart %% properties %% globals --]] local SceneIDTable = {25,183} while true do for i=1, #SceneIDTable do SceneIDCount = fibaro:countScenes(SceneIDTable[i]) if SceneIDCount == 0 then fibaro:debug("Scene "..SceneIDTable[i].." not running, restarting") fibaro:startScene(SceneIDTable[i]) end end fibaro:sleep(30*1000); end
  6. I have had the same problem with a couple of scene's... been looking at them for hours. The problem in debugging the code is that the error occurred at random times and after a random amount of loops. Finally "fixed" it with an additional script to check if the scripts are still running, if not I'll restart them... If you like to have a copy of my code let me know.
  7. That depends on the power that you use... In my opinion it's best to give it a try without. If the lights flicker or won't turn off completely you can always order the bypass.
  8. I think not; if I remember correctly SceneActivation requires LUA. HCL does not have LUA
  9. have you tried to restart it? If you can't restart with the power button just unplug it and start it again
  10. I did stop there. You mean you udated from 3.5xx to 3.600 after 4.030 was released? How? I am currently on 3.590 and only have the option to update to 4.031...
  11. I'm using the following LUA code (in 3.590): --[[ %% autostart %% properties %% globals --]] while true do local currentDate = os.date("*t"); if ( (string.format("%02d", currentDate.hour) .. ":" .. string.format("%02d", currentDate.min) == fibaro:getValue(1, "sunriseHour")) ) then fibaro:setGlobal("nightTime", "0"); if fibaro:getGlobalValue("AutoLight") == "1" then fibaro:setGlobal("LightTrigger", "1") else end elseif ( (string.format("%02d", currentDate.hour) .. ":" .. string.format("%02d", currentDate.min) == fibaro:getValue(1, "sunsetHour")) ) then fibaro:setGlobal("nightTime", "1"); fibaro:call(9, "sendPush", "Night has been set"); end fibaro:sleep(60*1000); end I'm using the Global Variable in the rest of my scenes....
  12. what I understood is that if your running 3.5xx and press the upgrade button that it first updates to 3.600 and immediately after that it starts the update to 4.031. I don't think there is any way to update 3.600 and stop there.
  13. or reset the device; this also clears the memory (of the device) and makes it ready for include again
  14. j.nowacki, can you share a percentage?
  15. j.nowacki, I presume you can seen in some kind of back-end system how many HC2 are currently running the V4 stable system. Are you willing to share the numbers with us? If known this can give some insight in the details.
×
×
  • Create New...