Jump to content
  • Announcements

    • T.Konopka

      DOWNLOADS - new way of sharing solutions!   01/17/18

      Dear users, We want you to have a great time here on the Forum, therefore, we are introducing a new tool for sharing solutions! DOWNLOADS - a system of file sharing for all of you. DOWNLOADS - support topics - this is a new category for support topics. Check the short guide for Downloads on how to add a solution (all files have to be approved).   Crowd's Solutions will be closed for new submissions, but still open for replies in remaining topics. We ask the authors of the solutions to add their solutions to Downloads with the link to the topic at the top of the description. We will merge the support topic with the one from Crowd's Solutions.   If you have any questions, feel free to ask our administrators - @T.Konopka and @I.Srodka!
    • T.Konopka

      DOWNLOADS - nowy sposób dzielenia się rozwiązaniami!   01/17/18

      Szanowni użytkownicy, Chcemy, abyście świetnie spędzali czas na Forum, dlatego przedstawiamy wam nowe narzędzie do dzielenia się rozwiązaniami! DOWNLOADS - system dodawania i pobierania plików. DOWNLOADS - support topics - to jest nowa kategoria z tematami wsparcia. Sprawdźcie przewodnik dla Downloads, aby wiedzieć jak dodać rozwiązanie (wszystkie pliki muszą zostać zatwierdzone).   Rozwiązania Społeczności zostaną zamknięte dla nowych tematów, jednak tematy już wczęśniej dodane będą nadal dostępne. Prosimy autorów rozwiązań do przenoszenia ich do Downloads - prosimy o dodanie linkiem do tematu na górze opisu. Połączymy wtedy temat wsparcia z tematem z Rozwiązań Społeczności.   W przypadku pytań, prosimy o kontaktowanie się z administratorami - @T.Konopka and @I.Srodka. (Rozwiązania mogą być dodawane w języku polskim!)

marbe

Member
  • Content count

    138
  • Joined

  • Last visited

Community Reputation

5 Neutral

About marbe

  • Rank
    Learner
  • Birthday 01/22/1968

Profile information

  • Gender
    Male
  • Country
    Czech republic
  • Gateway/s
    Home Center 2

Recent Profile Visitors

116 profile views
  1. Fibaro alarm panel

    Hello, I have same problem, it would be perfect to have system variables of arming and alarm states: AlarmStatus - no alarm, alarm, ... ArmingStatus - disarmed, partly armed, armed, ... I can see all this informations at AlarmPanel: - arming status - disarmed, partly armed and armed at slider. - alarm status - at beacon at top of alarm panel. Based on state of system variables then should be easier build scenes.
  2. FIBARO Icons web source

    Hello, on some forums I found code for popup messages with icons. There is written url to Fibaro web http://www.fibaro.com/sites/all/themes/fibaro/images/motion-sensor/en/motion_sensor_manual.png. Is this source available and is possible get list of icons? would be great for coding. Thanks
  3. Hello, can I ask for answer Fibaro and if some plans for future? Thank you
  4. Hello, I would like ask if is possible use FIBARO temperature and motion sensor FGMS-001 as temperature sensor for FIBARO THE HEAT CONTROLLER RADIATOR THERMOSTAT FGT-001? I know that heat controller has his own Bluetooth temperature sensor, but if I have at room FGMS-001 and I can set it to measure and send room temperature every 10 minutes via Z-Wave, then this temperature can be sent to heat controller too? Thanks
  5. FIBARO Dimmer2 FGD212 add 3 switches

    Yes, at attachment. Now it shows consumption 9.5W even if all switchs are off.
  6. FIBARO Dimmer2 FGD212 add 3 switches

    Thanks, but there is no information about software devices added to HC.
  7. Enable hotel mode UI error

    +1, for me hotel mode checkbox is every time unchecked, even if I set it more times ago.
  8. Hello, I added new Fibaro Dimmer 2 to HC2 FW 4.154 and it added more devices as expected - 1x system device (hidden), 1x remote controller(visible), 3x switches devices. Two of them have power measuring, last one not. It is correct and how should it work together, why 3x switches and what of them is main? Thank you Martin Device kind: com.fibaro.FGD212 Producer: Fibargroup Version: 3.5
  9. Hello, I want use fibaro calculateDistance service with Android Nougat on Nokia 6. My pooling is set to 5 min. But the service works unexpectedly - user distance is sent with delay, irregular, with bad accuracy, or intermittently. How should be set the phone and fibaro for properly work? I read more older topics with bad experiences with this service at past, will fibaro correct this feature? I have good experiences at past with Vera service, there is possible to set home location and the system itself generated presence state at home. Will be possible add feature like this? Thank you changes at user distance is random, with delay and irregular [DEBUG] 09:16:08: User, userDistance: 31.642596617422,09:15 15.01.18 [DEBUG] 09:25:08: User, userDistance: 804.7258307862,09:24 15.01.18 [DEBUG] 11:04:20: User, userDistance: 2507.7018718007,11:04 15.01.18 [DEBUG] 14:38:53: Change state: FIBARO Mobile User: User m., status: online, čas: 14:38 15.01.18 [DEBUG] 14:43:51: User, userDistance: 2396.928416795,14:43 15.01.18 [DEBUG] 14:44:51: User, userDistance: 2.1731997218002,14:44 15.01.18 [DEBUG] 14:49:52: User, userDistance: 4.8470816220479,14:49 15.01.18 [DEBUG] 14:58:53: User, userDistance: 9.6839699341613,14:58 15.01.18 [DEBUG] 15:43:59: User, userDistance: 10.484969379449,15:43 15.01.18 [DEBUG] 15:56:01: User, userDistance: 7.9335016254815,15:55 15.01.18 [DEBUG] 16:06:03: User, userDistance: 14.528331201125,16:05 15.01.18
  10. Yes, this is much more better, thanks. --[[ %% properties 246 thermostatState 246 mode 246 targetLevel 253 thermostatState 253 mode 253 targetLevel %% weather %% events %% globals --]] if fibaro:countScenes() > 1 then fibaro:abort() end local roomID = 5; -- room with fibaro thermostats local startSource = fibaro:getSourceTrigger(); fibaro:debug(json.encode(startSource)); local thermostats = fibaro:getDevicesId({roomID = roomID, type = "com.fibaro.FGT001"}); if startSource.type ~= "other" then fibaro:debug("thermostatState:"..fibaro:getValue(startSource.deviceID, "thermostatState")); fibaro:debug("targetLevel:"..fibaro:getValue(startSource.deviceID, "targetLevel")); fibaro:debug("targetLevelTimestamp:"..fibaro:getValue(startSource.deviceID, "targetLevelTimestamp")); fibaro:debug("targetLevelTimestamp:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(startSource.deviceID, "targetLevelTimestamp"))); fibaro:debug("timestamp:"..fibaro:getValue(startSource.deviceID, "timestamp")); fibaro:debug("timestamp:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(startSource.deviceID, "timestamp"))); local thermostatState = fibaro:getValue(startSource.deviceID, "thermostatState"); local targetLevel = fibaro:getValue(startSource.deviceID, "targetLevel"); local timestamp = fibaro:getValue(startSource.deviceID, "timestamp"); local minutes = math.floor((timestamp - os.time()) / 60) fibaro:debug("minutes:"..minutes) for i,deviceID in ipairs(thermostats) do fibaro:debug("deviceID:"..deviceID); if tonumber(deviceID) ~= tonumber(startSource.deviceID) then thermostatStateDevice=fibaro:getValue(deviceID, "thermostatState") if thermostatState == "Schedule" then if startSource.propertyName=="thermostatState" and thermostatStateDevice ~= "Schedule" then fibaro:call(deviceID, "removeSchedule", "255");-- remove manual setting end elseif thermostatState == "ScheduleTimeSetting" then local targetLevelDevice = fibaro:getValue(deviceID, "targetLevel"); if tonumber(targetLevel)~=tonumber(targetLevelDevice) then fibaro:call(deviceID, "setSchedule", "255",json.encode({["type"]="thermostat",["data"]={["setpoint"]={["type"]=1,["value"]=tonumber(targetLevel),["unit"]="C"},["mode"]=1}}),json.encode({["type"]="Minutes",["value"]=minutes}),json.encode({})); fibaro:debug(json.encode({["type"]="thermostat",["data"]={["setpoint"]={["type"]=1,["value"]=tonumber(targetLevel),["unit"]="C"},["mode"]=1}}),json.encode({["type"]="Minutes",["value"]=minutes}),json.encode({})) end end -- hold setting not implemented --fibaro:call(deviceID, "setTargetLevel", targetLevel); ---hold --fibaro:call(deviceID, "targetLevelTimestamp", targetLevelTimestamp) fibaro:debug("thermostatState device:"..fibaro:getValue(deviceID, "thermostatState")); fibaro:debug("targetLevel device:"..fibaro:getValue(deviceID, "targetLevel")); fibaro:debug("targetLevelTimestamp device:"..fibaro:getValue(deviceID, "targetLevelTimestamp")); fibaro:debug("targetLevelTimestamp device:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(deviceID, "targetLevelTimestamp"))); fibaro:debug("timestamp device:"..fibaro:getValue(deviceID, "timestamp")); fibaro:debug("timestamp device:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(deviceID, "timestamp"))); end end end fibaro:debug("--------------------");
  11. This works for me as first attempt --[[ %% properties 246 thermostatState 246 mode 246 targetLevel 253 thermostatState 253 mode 253 targetLevel %% weather %% events %% globals --]] -- change and add all fibaro thermostas IDs if fibaro:countScenes() > 1 then fibaro:abort() end local roomID = 5; -- room with fibaro thermostats local startSource = fibaro:getSourceTrigger(); fibaro:debug(json.encode(startSource)); local thermostats = fibaro:getDevicesId({roomID = roomID, type = "com.fibaro.FGT001"}); if startSource.type ~= "other" then fibaro:debug("thermostatState:"..fibaro:getValue(startSource.deviceID, "thermostatState")); fibaro:debug("targetLevel:"..fibaro:getValue(startSource.deviceID, "targetLevel")); fibaro:debug("targetLevelTimestamp:"..fibaro:getValue(startSource.deviceID, "targetLevelTimestamp")); fibaro:debug("targetLevelTimestamp:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(startSource.deviceID, "targetLevelTimestamp"))); fibaro:debug("timestamp:"..fibaro:getValue(startSource.deviceID, "timestamp")); fibaro:debug("timestamp:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(startSource.deviceID, "timestamp"))); local thermostatState = fibaro:getValue(startSource.deviceID, "thermostatState"); local targetLevel = fibaro:getValue(startSource.deviceID, "targetLevel"); local timestamp = fibaro:getValue(startSource.deviceID, "timestamp"); local minutes = math.floor((timestamp - os.time()) / 60) fibaro:debug("minutes:"..minutes) for i,deviceID in ipairs(thermostats) do fibaro:debug("deviceID:"..deviceID); if tonumber(deviceID) ~= tonumber(startSource.deviceID) then thermostatStateDevice=fibaro:getValue(deviceID, "thermostatState") if thermostatState == "Schedule" then if startSource.propertyName=="thermostatState" and thermostatStateDevice ~= "Schedule" then fibaro:call(deviceID, "removeSchedule", "255");-- remove manual setting end elseif thermostatState == "ScheduleTimeSetting" then local targetLevelDevice = fibaro:getValue(deviceID, "targetLevel"); if tonumber(targetLevel)~=tonumber(targetLevelDevice) then fibaro:call(deviceID, "setSchedule", "255",json.encode({["type"]="thermostat",["data"]={["setpoint"]={["type"]=1,["value"]=tonumber(targetLevel),["unit"]="C"},["mode"]=1}}),json.encode({["type"]="Minutes",["value"]=minutes}),json.encode({})); fibaro:debug(json.encode({["type"]="thermostat",["data"]={["setpoint"]={["type"]=1,["value"]=tonumber(targetLevel),["unit"]="C"},["mode"]=1}}),json.encode({["type"]="Minutes",["value"]=minutes}),json.encode({})) end end -- hold setting not implemented --fibaro:call(deviceID, "setTargetLevel", targetLevel); ---hold --fibaro:call(deviceID, "targetLevelTimestamp", targetLevelTimestamp) fibaro:debug("thermostatState device:"..fibaro:getValue(deviceID, "thermostatState")); fibaro:debug("targetLevel device:"..fibaro:getValue(deviceID, "targetLevel")); fibaro:debug("targetLevelTimestamp device:"..fibaro:getValue(deviceID, "targetLevelTimestamp")); fibaro:debug("targetLevelTimestamp device:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(deviceID, "targetLevelTimestamp"))); fibaro:debug("timestamp device:"..fibaro:getValue(deviceID, "timestamp")); fibaro:debug("timestamp device:"..os.date('%H:%M %d.%m.%y',fibaro:getValue(deviceID, "timestamp"))); end end end fibaro:debug("--------------------");
  12. FGT-001 The Heat Controller actions

    yes, that's very smart, thank you
  13. Hello, I cannot find description for heat controller action as described at docs actions": { "reconfigure": 0, "setDefaultPartyTime": 1, "setInterval": 1, "setMode": 1, "setSetpointMode": 1, "setTargetLevel": 1, "setThermostatSetpoint": 2, "setTime": 1 }, specially I need to set targetLevel as temperature setpoint for manual mode (mode ScheduleTimeSetting, targetLevel), this is possible with parameter setTargetLevel, and targetLevelTimestamp. For it I cannot find right parameter. Thanks
  14. Yes, this works for me, but not for my family. Advantage for they is to use temporary setting temperature from heating controller. Now I write script, but at future would be nice to have this functionality at system. Thanks
  15. Hello, I have new Fibaro thermostats with temperature sensor at one room. Al works perfect and I like it. Only ones - is possible configure more thermostats, they will work as one. I mean if I set manually one of them to manual set point, direct on thermostat, is possible, that other thermostats at same room will be set to same manual mode and temperature too. Now is necessary each of all thermostats set individually.
×