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!)

All Activity

This stream auto-updates     

  1. Past hour
  2. Installing Fibaro Devices

    Hi Peter, I tried all the above and I have been unable to get it to work with the delete function or the add function. The 30 seconds would elapse without anything happening. However, I have carried out an experiment as per the attached picture in the same room the controller is and I managed to get it into learning mode straight away. I programmed it and selected the room I wanted to install it in, then I disconnected everything once configured and installed it in that room and is working perfectly. I have now installed both modules that I was having trouble with using the same technique. It appears I have a problem with the range to the controller during setting up, but not anymore once it has been installed. Regards Gareth
  3. Hello! I´m new on this and i am looking for some help. I bought a fibaro hc lite and i whant to add my ip cam tp-link nc450 to the system. How can i do it? I have tried as other model whit no results. The firmeware has any tp-link model. Thank you
  4. It works, just I need it. Many thanks for help.
  5. Dimmer percent reading

    Thanks! Now I have learned something today!
  6. Dimmer percent reading

    1) https://developer.fibaro.com 2) http://192.168.1.36/docs/ where 192.168.1.36
  7. Aeotec MS6 PIR hanging breached

    Ha, apart from the workers wearing high viz now not much has changed.
  8. Today
  9. Dimmer percent reading

    That worked! Thank you, 10der! Is there any documentation available on such "commands" through extended IP addresses? I notice of course that http://192.168.[etc.]/fibaro/no/home/ is my home page for the HC2, but nowhere have I seen the .../api/devices/[id] described. Where can I find such things? I assume there are other smart things you can do the same way.
  10. Dimmer percent reading

    http://192.168.1.36/api/devices/5 where 192.168.1.36 HCx IP address and 5 - id of your device
  11. The issue has been fixed and the Apple Home app doesn't show the update notification anymore. Cheers! : )
  12. Dimmer percent reading

    Thanks, that looks good. My Newbie question is: How do you display this list without defining a LUA script?
  13. Dimmer percent reading

    for example or local value = tonumber(fibaro:getValue(n, "value") local value = tonumber(fibaro:getValue(n, "value"));
  14. I am glad you like it. If I can improve something, please tell me. At the moment, that is a good thing, so we are certain no script can influence the heating panel. This is intriguing, I wonder if there is a particular issue with your network, in a certain area. In an average house, I'd say 10 to 15 meters is possible (for a direct connection). If there are no obstacles, 5 m is not a lot. So this goes against the theory of a network issue. Unless you've got a source of interference. That is something to keep in mind. I see. Unless they were quickly drained, we can eliminate battery problems. But when in doubt, either swap them with another valve, or try non-rechargeable lithium batteries. Expensive, but they do last longer and a few users told me they are excellent for this purpose. Let's see how that goes. If that still does not help, and if you haven't done this already, there is maybe one thing you should try on one of the failing TRVs... But then, unfortunately, the TRV will have to relearn the response of your radiator so it may take a wile to go back to (good) regulation. And that is... Exclude it... Delete the zone... Add back the zone and include the room. Include the TRV and assign it to the room. That is the equivalent of...
  15. Welcom to the forum, @Jan Zahradnicek I understand you are new to Fibaro... I've been around here for a while and I think "temperature control" is a tough subject. Much tougher to grasp and understand than electricity. It is more difficult to measure stuff... I do not want to underestimate you... I just want to start at the basics to make sure everyone is at the same level of understanding by the end of this post. This is copy/paste with some rework from my previous posts on this forum... I'll keep repeating and improving the explanation until everyone understands it... To my knowledge, no one on this forum has attempted to explain heating systems... until now. So please bear with me... I am not a heating specialist, but an engineer and passionate about HA so boiler control and temperature is part of my hobby. In this you will find at least partial answers to your questions. I could have just answered those questions, but I prefer to give this complete post, because there is a certain structure to it... Let's get some things straight. The FGT-001 is a THERMOSTAT. Popp, Danfoss Living Connect (aka LC-12 and LC-13), Eurotronic TRVS, they are all THERMOSTATS. Technically, they are not "valves", they are "thermostatic heads" attached to a valve. It is customary to refer to the assembly (head + valve) as a "Thermostatic Radiator Valve" or TRV. I will use TRV if I refer to some sort of thermostat to control water flow. I will use FGT or FGT-001 when I talk about the "Fibaro Heat Controller". I will NEVER refer to the FGT as the "HC" because that abbreviation is used quite a lot on this forum to reference the "Fibaro Home Center". If I accidentally use HC in a topic about heating, I mean "Home Center". I'll try to avoid that... They do NOT use your controller, to regulate temperature. They do not use any sensor measurement of your Z-Wave system. They contain their own sensor (or sensors!) and the FGT has an optional external probe. That probe is not Z-Wave, it is Bluetooth Low Energy and it is specific to the FGT-001. But since the probe measurements are transferred to your controller, you will get (accurate) temperatures from the FGT. An FGT-001 without such a probe does not report measured temperature and this is by design. The Danfoss LC-12 and LC-13 do not report temperatures either. Popp does report, because it uses a modified firmware version on Danfoss hardware. But the sensor values are inaccurate because the TRV is not in the right spot to measure room temperature. They can be used for reference. You tell the TRV to go to some set-point, for instance, 22 °C and it does that for you! It does not need a controller or a temperature reference, nor does it need a room thermostat and you also do not have to buy the external probe... It is an autonomous system. It uses hot water and a battery to control room temperature. You do not have to use the "heating panel" and you do not have to write any Lua code. If you take it out of its box, mount it on a TRV, it starts controlling temperature, even when it is not included on your Z-Wave network. The FGT-001 can either use its internal sensor or the special extra bluetooth low energy "button" external probe. The extra sensor can be in a more optimal place: the right height, no direct sunlight, nearer to the spot where you want to control temperature. With this probe, the FGT starts reporting temperature too. It reports to the TRV every 10 minutes. To conserve power and reduce network traffic, the FGT only sends temperature to the controller about every 2-3 hours when the temperature readings differ by 0.5-1 degree from the last report. You can turn the KNOB (or push buttons) to change the set point. No magic involved. For instance, on the FGT-001, turn the ring until it displays "cyan" and it will regulate the valve, until the temperature averages 18 °C. It does not need the extra sensor, because there is one (actually two) and the device itself has an algorithm to go to the set temperature. It also does not really need a controller, all magic is performed by the micro-controller in the TRV. Your TRV does not need a connection to a controller to do its job. You can install a TRV, set the thing to 24 °C if you like that, and it will start to open and close the valve. So you can check the performance of your TRV by leaving it excluded, so you can be sure it is not influenced by code or "something on your controller". This way you can be sure it is not a communication problem, or a script changing the set-point. Of course, this degrades it to "a mechanical thermostatic head" - but we managed to live with that kind of control, did we not? You get more interesting possibilities, with a Z-Wave controller. You can send temperature settings to the controller via your app, or using the browser interface. Like: "go to 23 °C for 4 hours". Because FGT-001 is a FLiRS (frequently listening routing slave) device, roughly one second after you change the temperature, it will take into account your new target value! So there is no "wake up" interval (and delay) like ordinary battery operated device. Older TRVs are not FLIRS so they kind of "request settings at regular intervals" - otherwise know as "wake up interval". To my best knowledge, the only other FLiRS device on the market is the "Spirit Z-Wave Plus". Danfoss has announced the LC14, it should be FLiRS based but I don't think you can buy one yet. Some part of slowness of the "older TRVs" comes from the wake up interval. The FGT-001 has eliminated that. It will respond to commands "almost instantly". Older TRVs ask the controller at regular intervals "what is my set-point" (target temperature). It is recommended to set wake up > 300 and < 900 and set each older TRV wake up with 10 seconds difference to avoid collisions. FLiRS devices do not have such a setting because they do not need one (they are nearly instant). So, you have your TRV connected (included, added) to a Z-Wave controller? Then from now on you have a "remote control" for your thermostat. It still does not need your controller or a temperature sensor to control the temperature. Sometimes, it is more convenient to use your phone or a tablet. But it's not real automation (yet). Communication is bidirectional: the controller can set the TRVs set-point and the TRV will report the set-point if someone turns the knob. If you change the setting on the TRV, it sends that information to the controller, so you can immediately see in your app or on your browser... set-point has changed. You'll notice a timer too, this is something interesting to talk about but not right now. Just keep in mind changing the setting on the TRV acts as "an override with a timer" (it requires more explanation, I know...). The FGT-001 also reports temperature if it has an external sensor. It DOES NOT report sensor data without external sensor. To me, this makes totally sense, because the sensor is not in a good spot to measure room temperature. I have dedicated a separate topic to this. Popp is a modified Danfoss TRV. It reports temperature, but depending on your house and position of the TRV, its temperature reporting will not match the temperature at a key point in your room... If you want to know more, please read my other topic... https://forum.fibaro.com/index.php?/topic/28319-fgt-001-fibaro-heat-controller-external-sensor-evaluation-part-1/ The next step would be to use "the heating panel". The heating panel is nothing but a scheduler. It contains time/temperature settings (pairs). And all it does is send the schedule to the TRV. Again, the FGT or Danfoss is fully autonomous after it receives the schedule. Older thermostats get only a set-point change. The FGT-001 gets a complete schedule. The effect is largely the same. You can override the schedule by turning the knob, or by using the app. You get manual override and holiday mode as a bonus. You need to understand the concept of zones and rooms and maybe take into account that one FGT remote sensor can send temperature to three FGT-001 heads. It might be a little bit more complex than I suggest... one thing that trips people is how "time" plays a role in overriding the schedule. If this still isn't enough control, you can use Lua to send a set-point to the TRV. Even in this case, you still do not need an extra temperature measurement... The FGT is FLiRS and responds almost instantly to your commands. The older valves get a setting at the next wake-up (typically set to anything between 5 an 30 minutes). Of course, you can use some sensor in the room to estimate the performance of the TRV and nudge the set-point up and down, to compensate for the fact the TRV is not in a good position to measure room temperature. I do not present scripts to do this... You can use Lua with or without the heating panel,. If you want to make your own scheduler, you can do that, no need to configure the heating panel. The setting "The main thermostat:" on the "room settings tab" can be used by Lua scenes, but I do not think it is used in any other way. The setting "The main temperature sensor:" on the "room settings tab" selects the sensor for the temperature gauge in the top left corner of a room (app + browser) for display purposes. It does not in influence temperature control, unless you use or write Lua scene(s). All the TRV needs is... a steady source of hot water and battery. And this brings us to the issue of room thermostat and boiler control. The boiler should take care of the hot water problem. It has a boiler thermostat, and possibly some settings and maybe an external probe. You see, I do not mention a "room thermostat" when I talk about boiler control, this is intentional. I might discuss this another time. For sake of completeness... other TRV systems exist. If you are interested in a mains operated, completely silent actuator (not a thermostat!) look up "thermoelectric actuator". notice: "actuator" is not "thermostat"... You need a thermostat to control that kind of actuator. It is something to keep in mind: all Z-Wave TRVs make some noise! There is one rather peculiar device on the market, which causes a lot of confusion: "Danfoss RS 014G0160 Thermostat". On a HC 4.160 you can use this as a kind of remote control. It does not act as a real thermostat, because the device does not control any output (on a home center). You can use Lua to intercept "value" and "timestamp" as with any other thermostat. Also for sake of completeness...You can turn a sensor and a switch (relay) into a basic thermostat using "linked device". It only works with a relay, not a thermostat. I am not a big fan of this setup, if communication fails and the relay gets stuck "open" or "close" your room might get very hot or cold. You can by thermostats with a relay instead. FGT-001 has issues, we are waiting on a device specific firmware update. Are you still with me? Any questions? Go ahead! There are no stupid questions... I learn from people asking questions, either because it makes me formulate the answer or makes me aware of things I do not know! Thats good!
  16. Having installed my first Fibaro Dimmer 2 on the HC2, I noticed that in addition to the main unit, which has a lightbulb icon, one of the slave units was also visible (i.e. not hidden). This unit had the tag X.0.1, where X is the allocated device number. This slave unit was also equipped with an icon, a remote control, but I have no other unit installed than the basic dimmer. Other slave units are hidden as expected. It is not hard to tick off that the X.0.1 unit should be hidden as well, but is rather confusing to have extra units appearing when I am installing only one.
  17. Dimmer percent reading

    I have just installed my first Fibaro dimmer 2 and testing has started. When trying different settings on the Home Center 2, I would like to know what the actual percentage level is for the dimmer. The slider gives a rough graphic indication, but no actual percentage reading. Is there a way for the Dimmer to inform me about the precise value?
  18. Dahua integration Fibaro

    Latest firmware update in Dahua cameras has removed Basic authentication (only Digest authentication is now supported). Fibaro does not support Digest and has not announced any plans for the future support.
  19. Motion sensor being added as Door Sensor

    95% sure it is the same device. The reason for not 100% is that the delivery didn’t include the holder and battery.
  20. Motion sensor being added as Door Sensor

    Does the old (bad) one look like this one? http://www.szneo.com/en/products/show.php?id=197
  21. Hello, I would like to ask you a question as for the compatibility of the Fibaro system with the third party product - Eurotherm Spirit Z-Wave Plus Electronic Heating Thermostat. It measures the temperature and automatically adjust the heat level. Here is the link the the product details: https://www.eurotronic.org/en/products/spirit-z-wave-plus.html As I understood the Fibaro Heat Controller is a remotely controlled thermostatic head to control temperature in a room and it works as the actor. Which means that it can react on events. Exactly on the same principle works also the Eurotherm Spirit Z-Wave Plus Electronic Heating Thermostat. I would like to automatically set temperature in a room depending on day time (time schedule), like it is possible to configure in the Heating Panel. But when I try to configure the Heating Panel in my Figaro system, I can not find any actor there except the Fibaro Wall-Plug (there is not included any other Fibaro device of the type actor in my system). Does it mean the the Fibaro system can recognize as actors only Fibaro devices? I believed that it can work with any other device which supports ZWave protocol (ZWave Plus) When I click on Panels -> Linked Devices -> Linked Devices - Heating -> Add -> tab. Advanced -> Main Device : as a sensor is selected the sensor build-in in the Eurotherm Spirit Z-Wave Plus Electronic Heating Thermostat (or the temperature sensor build-in in the Fibaro motion sensor in this room). Then I click the button 'Add'. Here I can not find any actor except the Fibaro Wall-Plug. As I mentioned above, this is the only Fibaro actor in the network. I followed the same steps as mentioned in the e-learning site at http://e-learning.fibaro.com/topic/linked-devices/ but without any success. I also searched the community for the issue and checked your e-learning site at http://e-learning.fibaro.com/topic/linked-devices/ but did not find anything. Here are my system details: Device type: Home Center 2 Firmware version: 4.160 The main reason why I chose Fibaro was the fact that it is compatible with any device supporting ZWave. But it looks that it is only a marketing strategy and the reality is totally different. Thank you very in advance for any suggestion how to solve this situation. Best regards Jan
  22. Motion sensor being added as Door Sensor

    Here is an update(long answer): I requested an replacement by Amazon, and before I returned the old device I compared the devices and took a picture. External on the box it were same devices (FGMS-001 ZW5 v 3.2) The devices were not the exact version. See picture attached. The new is on the righ/bottom and white inside. I added the new device to my network and it is working as expected as a Fibaro Motion Sensor! In my view some spooky going on and I think Fibaro should be aware. For my part I can say I ordered the device as new and both the old and new device have been delivered directly from Amazon.
  23. Danfoss LC13

    I think you could use a temp sensor to get an idea of how much you have to add to or subtract from the TRVs setpoint, but to be honest I do not have code for that. I think you need some kind of PI controller to do that. I do not have the means to try this right now... Fibaro D/W 1 plus DS18B20 is accurate. D/W 2 with built-in sensor is accurate, but noisy. Yes, it is mentioned in the manual. The manual is here: https://www.eurotronic.org/en/products/spirit-z-wave-plus.html
  24. Danfoss LC13

    Regarding eurotrinics, correct me if im wrong but does It support the usage of an external temperature sensor?
  1. Load more activity
×