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
Search the Community
Showing results for tags 'HC2'.
-
I am progressively excluding my HC2 devices and migrating them to HC3, but I have a bunch that seem to not be responding to triple clicks...this was for exclusion initially, but then on re-inclusion after I managed to exclude after the 20th try for one dimmer. I think there are/could be multiple causes here: Dodgy switch wiring (there was one light that was finicky even on a directly wired setup and it took ages to even unpair) Devices not where I think they are - behind switchplate - I've already found a few by moving the HC3 closer to the ceiling or pulling a downlight out and seeing a Fibaro device come trailing behind it Connected to S2 instead of S1 by lazy sparkies (possible, unverified) Devices behind brick external walls/internal insulation, and now part of a much populated HC2 network I plan to wait for a dry/cooler day (aussie summer) to trapse my HC3 around the house to likely candidate points, but it would be easier if I could rely on extenders, a secondary controller (Aeotec Gen 7 with Silicon Labs PC controller*), or even just find the devices myself withmy Aeotec Gen 5 stick, running as a sniffer might be a better approach. My questions are: Would a sniffer on a USB stick (small, internal antenna) be of any use to try to triangulate the device's location? (I was thinking to monitor the RSSI or something) If so, does an excluded/factory fresh device send any z wave signals when interacted with via S1 switches? (I have at least one that is now excluded but still in an unknown location with an unresponsive triple click) Do exclusions get passed and processed network wide? Or only in direct range of controller? The 'remove' function lacks an NWI flag. I have added some extenders in the general areas I am having issues, without much change. Can exclusions and inclusions get passedand processed by a secondary controller? If so, do you need to run the process on the secondary (in my case through Silicon labs PC Controller),or start the exclusion on the HC3 and trust the secondary will mediate? Would powering down my HC2, Zniffer, Secondary controller make it easier for the HC3 to find devices through a normal include? *Not sure if relevant, but: All of these 'can't exclude' devices are functioning fine on the HC2 network, though I know each one I exclude changes and limits the mess on that network. I am running Engine v 3 on the HC3. None of the diminishing HC2 networking are security connected, but pretty much all of the HC3 network has been included as S0 or S1. The 700 series controller is behaving a bit odd as a secondary for the HC3 compared to the HC2. It's definitely getting included, finding devices etc, but any mapping and node tracing functions seem to get null results or error out. (the standard APIs also get nulls when tracing last route on the HC3 - I need to use the new engine API to get those details....but I didn't think the silicon labs devices would know/care about that? -
Hi, I am looking to purchase a UPS to make sure my critical devices (HC2, NAS, Pi, etc) are powered down gracefully in the event of a power disruption. I was wondering what people use and how it is setup and if it is suiting your needs any input appreciated Thanks _f
-
Hello. I wanted post it here: https://forum.fibaro.com/forum/129-other-solutions/ but i have no rights for it. First of all I want to say that it is totally not recommended to do it. If you have similar problems - ask for support first! DO IT ON YOUR OWN RISK! Probably this will end your warranty (but my already ended). Two days ago a need to do some electric works and I shutdown my HC2 by pressing power button. Then, when I finished - I switch it on leds start to blinking... but nothing hapened. I tried to boot to recovery but it did not boot also. I unscrewed left panel of HC and attach monitor to see whtats hapening. And I sawed that it is immediatly reboot after selcecting a boot device. It was a GRUB problem. This tutorial is for linux users. Btw, my HC2 version is 4.550. 1. You need: >=1Gb flash drive Keyboard Monitor with VGA connector Linux PC (you can prepare USB drive on Windows, but I do not know how, sorry) 2. Preparing flash drive Download Debian 6 image: https://cdimage.debian.org/mirror/cdimage/archive/6.0.10-live/amd64/usb-hdd/debian-live-6.0.10-amd64-rescue.img And flash it to usb drive (this will erase all your data on flash drive): dd if=debian-live-6.0.10-amd64-rescue.img of=/dev/sdc /dev/sdc - is your USB Flash. 3. Boot with prepared flash drive Power off HC2. Insert USB Flash. Remove fibaro recovery usb-drive. Press F10 like crazy after power on. Select your USB flash in menu. 4. Fixing grub When GRUB of flash drive appering - select failsafe mode and press enter After boot sequence will compleate you have about 5 minutes to fix your problem (after sometime something will reboot your HC2). Determine system drive device: ls -al /dev/disk/by-label You will see something like: ... lrwxrwxrwx 1 root root 10 Nov 9 14:38 SystemFS -> ../../sdb2 ... So, sdb is your target drive. Mount SystemFS with write permissions: sudo mount /dev/disk/by-label/SystemFS /mnt -rw Install GRUB to your target device. sudo /usr/grub/grub-install --root-directory=/mnt /dev/sdb Now you need to fix grub.cfg vi /mnt/boot/grub/grub.cfg grub.cfg should become like this: set default="0" set timeout="5" menuentry "Buildroot" { set root=(hd0,msdos2) linux /boot/bzImage initrd /boot/initramfs boot } 5. Reboot Do not forget to remove your flash drive. It shodl boot normaly now.
-
In making the transfer from HC2 to HC3 based on a cloud backup (update 4.581 Beta) it is stated that "scenes will not be moved and need to be created again". That's OK, but it would be helpful when planning the transfer to know what the differences are (in syntax and available functions) between the two LUA versions. I know that the new LUA editor is documented in https://manuals.fibaro.com/home-center-3-lua-scenes/ . What I would hope to see in addition, is a side by side comparison of all the crucial differences, to enable a pre-edit of the old LUA scenes before entering them into the new editor. Something like this: If you used this in HC2 LUA: You need to do this in HC3 LUA: fibaro.debug("txt") fibaro.debug("tag", "txt") os.time() ??? etc. If we all contribute to such a table as we identify all the differences, we may be able to help each other prepare for HC3. Not all differences can easily be summarized in the simple two-column format above, however. For the new definition of conditions and triggers, it seems it would be more appropriate to give a few examples of old codes (with triggers) converted to new codes. PS: I haven't even decided to buy the HC3 yet! But getting a feel for the amount of re-programming needed to convert my scene is an important factor in making that decision. The suggested table is now shown in a pdf file attached to this post, see below. It is regularly updated as new contributions are posted. LUA HC2 vs HC3.pdf
-
Hi all. Wonder if anyone can help with this issue i have. I have setup a plugin for WOL (Wake On Lan) so i can press a virtual button on my phone and it turns on a PC. I now want to include this in to a scene so when i start the scene, the PC turns on with other devices. Ony wanted this since getting the amazon Echo service working with my setup. Idea is to walk in the room and say, Alexa, Turn on Cinema and all will just turn on and work. Issue is, i can't add in the WOL plugin with a scene. Has anyone managed to do this and if so, how? Thanks, Hal
-
Cannot select a different Home Center to use with Alexa Integration
Ploudo posted a question in Amazon Alexa
Hi, I have multiple HomeCenters (2x HC3 and one HC2) in 3 different homes. Two of these homes are mine, but are in different geographical locations. I've created two seperate amazon accounts, both of which use alexa. The problem I'm facing is that when setting up the Yubii integration on Alexa, I don't have the opportunity to chose which HomeCenter I wish to use. This results in the devices of my main home being all added to my 2nd home (as these devices were previously added to the Alexa over there) and no way at all to ad the new HC3 and al of it's connected devices. This is particularly annoying as Fibaro (or Yubii now, idk) give you acces to multiple HomeCenters from home.fibaro.com/... . But I have no way to select any of these devices when setting up alexa with Yubii. Is there any way to specify WHICH home center to use when connecting Yubii to Alexa with the skill? Thanks for any help. -
Hi, is there a way to move all config from one HC2 to an other HC2? I also have a HCL, is it possible to move all config from a HC2 to a HCL and the other way around? Stupid questions perhaps, but I do have 2 HC2's and one HCL and would like to move these around in my different houses. Thanks Tony Levis Sweden
-
I use a managed laptop from my work to manage and program my hc2. Some time I can't log in on my hc2. I get the login screen an can fill in my credentials. But pressing enter or clicking on login does not give any reaction. I tried with Microsoft edge and with Google chrome. On my very old en very slow Mac Mini I tried to login with Safari and with Google chrome and both work! I think my company has set some security settings in my browsers on mij laptop. What browser settings are necessary to use the hc2 interface? My be I can set de settings my self or i can ask my company's it to set it for me. Thanks in advance for any tips!
-
Version 1.0.3
1,563 downloads
UHAS v1.0.3 (Universal Home Automation System) for HC2 UHAS INTRODUCTION UHAS is a set of scenes and Virtual Devices (VD) that provide the following capabilities: Auto translation of all scenes, VD's, predefined global variables, and messages to 31 different languages (19 directly supported by HC2) (NOTE – not all languages are translated, and users are very welcomed to help with translations that are not yet done) Scheduled and repeating events based on time of day, week, month, and season including Scene FTBE which provides repeating and scheduled actions Advanced Notification Center (ANC) brings centralized notifications with support for most popular services like Pushover, Telegram, GroupMe, WhatsApp and Signal, Sonos TTS and LaMetric TIME smart clock notifications Advanced Lighting Control (ALC) with integration for Philips HUE, Nanoleaf, LIFX and Blebox devices (will be provided in separate package) Very Smart Blinds (VSB) automation Presence monitoring and control with geofencing and Netatmo presence Weather state and forecast with notifications and integration for Netatmo weather station and WeatherFlow and Tempest weather stations Home consumption monitoring and recording Appliance monitoring - with notifications Safety alarms fire and flood Security alarm integration ready with provided global variables Irrigation control based on FIBARO devices Scenes ready to use with Fibaro dimmer 2, Fibaro keyFob, Fibaro Swipe, Fibaro Button and Remotec ZRC-90 central scene activation with built in support for ANC HC2 system status notifications, automatic backups and many more... UHAS OVERVIEW UHAS has been developed for the Fibaro Home Centre 2 (HC2) home automation controller, as a series of modules, which are responsible for one particular action or job, and the user can interact with them as a group, or on their own. UHAS provides an advanced Home Automation (HA) set of features, ready to be used out of the box with minimum user effort to set up and run. Running code is provided as part of the system, doing most of the settings for the user or a systems installer. UHAS is primarily intended to be used by users of the Fibaro HC2 system who wish to have fully featured HA without the need to learn LUA programming and spending a lot of time with coding Virtual Devices and scenes. UHAS can also become a part of a mature Fibaro system installation which has developed with many modules to cover more advanced HA and more devices. UHAS Virtual Devices and scenes use proprietary code developed by author. This code is developed to minimise users involvement in installation and setting of the system. Most of the necessary setting is done by the UHAS components and other settings are simplified and minimised as much as possible. This was also possible because all UHAS VD's and scenes use role system that is used to find necessary components for actions to be performed. UHAS Virtual devices category is set automatically during translation or changing of the main icon. This means that most of the VD's should show in proper category in new mobile app as lights, blinds, gates, ambience, climate, safety, security, multimedia, remotes and other. The same goes for scenes, when scenes save their settings after first manual run then also category is set. UHAS PREREQUISITES Fibaro Home Center 2 (HC2) with firmware version 4.120 or higher (recommended but not necessary expanded RAM memory to at least 2Gb) Configured and installed z-wave devices – I.e., light switches, motion sensors, lux detectors etc. INSTALLATION AND UPGRADE NEW USERS - Please download provided UHAS v1.0.3 Installation package and UHAS Installation and User Manual v1.0.3 EN EXISTING USERS - if your UHAS is: Not yet started with installation then please download full package UHAS v1.0.3 Installation package and install. Still on v1.0 or V1.0.1 then please first download UHAS v1.02. upgrade package and install. Lastly download and install UHAS v1.03. upgrade package Installed v1.0.2 then please download UHAS v1.03. upgrade package and install. NOTE - Upgrade instructions are provided in UHAS Installation and User Manual v1.0.3 EN ADDITIONAL NOTE - In UHAS Installation and User Manual v1.0.3 EN instructions for ALC scene upgrade say: UPGRADE INSTRUCTIONS – This upgrade is recommended. To upgrade and keep your ALC Scene settings please copy new code from ALC Scene v1.3.3.lua from line: -- NEW v1.3.3 - copy code from here to the end of scene code to keep your settings above this line to the end of code. The mentioned line I forget to add to the code before making upgrade package, therefore please copy new code from line: -- THE CODE BELOW DOES NOT REQUIRE MODIFICATION BY THE USER to the end of code. Thanks goes to @MiZ for pointing that out 🙏 IMPORTANT NOTE UHAS uses its own unique global code variables. This means that UHAS will NOT influence the current system scenes, scripts, or virtual devices in any way, even if any of Sankotronic’s earlier UHAS beta versions and standalone scenes or VD's (Virtual Devices) are being used. There is no need for any changes to be made to the existing code before the installation of UHAS. The UHAS global variables are created and controlled automatically by the system so that you do not need to maintain them manually. UHAS INSTALLATION PACKAGE CONTENT (29.1Mb) 92 Virtual Devices 53 scenes Icon sets for all the above VD's and scenes THANK YOU! ❤️ I want to BIG thank to @clowg for helping me with translations and writing manual these last days speeding up publishing UHAS. BIG thank to @gucio1234 and his son Cyprian for making logo for UHAS and 3D printed with real gears! I just love it ❤️ I also want to thank many of you who helped during testing of UHAS beta versions and with translations! @clowg, @speedoxx007 ,@Bodyart, @jimicr, @gucio1234, @jompa68, @Sjekke, @robw, @rbhun, @lennypenny, @FunkFib, @MarcoT, @Orgli, @MarcoTorino71 and many others. Your help is greatly appreciated. Apologies to all other not mentioned nice people who contributed in making UHAS. I also want to thank gurus of this forum @petergebruers, @jgab, @cag014, @SmartHomeEddy and others for help with coding in LUA. And of course a BIG thank to Fibaro for providing Home Center 2 and Home Center 3 for developing purposes! BIG THANKS! also to all UHAS users for their donations! Your support is greatly appreciated! 🙏 TERMS AND CONDITIONS Permission to use, copy, modify and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement is hereby granted, provided that the copyright notice, with "Terms and conditions" and "Disclaimer" appear in all copies, modifications and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author. DISCLAIMER This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Fibar Group S.A. and their employees are not responsible for support of the UHAS. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. -
Version: 4.510 HC2 REST API Hi guys, since update to version 4.510 i get sometimes this email: "Suspicious Login Attempts Prevented: We noticted 5 failed login attempts to your HC2 that seemed suspicious. For your security, the following IP address xxx has been locked for 30 min" Why? The REST Auth are right. At start status code 200 with successful result and a little bit later 401 bad user and pass. All request, in the previous version, ran flawlessly...
-
I have a fibaro motion sensor and it keeps detecting motion even though there is none about every 10 seconds. turned off all scenes that interact with the motion sensor - still does the same thing. I restarted my HC2 - does the same thing. Motion sensor on latest firmware. *the only time it stops for a while is when the lux in the room goes to 0. but then it will detect motion again. **I do have the sensitivity really low, when I raise it above 20 it seams to go back to "normal" I don't want this at 20 rather it be 8-10. I have two other fibaro motion sensors set to 8-10 with no problems. @T.Konopka do you know what this could be? a bug?
-
Hi all, I 've just bought my new HC3 but before I do the migration I have one issue: After the migration the z-wave devices will network anymore ->ok But I have some VDs only HC2 where I do not have an idea on how to migrate them to HC3, somy Idea was to keep those on HC2 and leave them running, if that is possible at all? e.G. I have one VD that is doing call handling (sending messages on Calls) with my router (fritzbox). This one is actually quite stand-alone, and does not need other devices. Would that work in general, or are all VDs not communicating anymore? cheers joystick
-
Does anyone know how to open the log files from the following address: - <HC_IP>/api/service/logsDump I am having some funky goings on and want to review the logs myself but when the file is downloaded from my HC2, it is a .tar.gz file and 7 zip will not open it. Can anyone help me out at all? Thanks, Hal
-
Hi, I have Alexa connected to HC2 (4.630). Everything was fine for a long time. But now I have problem with Danfoss thermostat. Alexa is funding thermostat as: "Connected Via: Danfoss Description: Thermostat connected by FIBARO Type: thermostat Enabled When I try to change temperature, I have information: "server unresponsive" Do you have similar problem? Some time ago everything was fine.
-
Hi all, I would like to share a 100% working solution for HC2 / HCL users that want to use new IP cameras working with RTSP, H.264. Problem: as you know Fibaro doesn't respect too much users demands. Fibaro only supports old IP cameras working with old streaming methods like MJPEG, using basic authentification... This is very bad, because it forces us to use old and unsecure technology. The best solution is that Fibaro supports newer protocols, RSTP, H.264, SSL authentication... But as you know, taking care of users is not the main Fibaro interest. Workaround solution: using an old Android phone (or tablet) as a webserver proxy using tinyCam Monitor PRO awesome app (3,5 EUR cost). The main idea is that tinyCam Monitor PRO connects to your cameras, serving at real-time MJPEG streams that Fibaro can watch perfectly fine Yes, it sounds too naif but for me, it toke me years in order to find this solution... In my example we will use Foscam C1 Tinycam Monitor Pro Configuration: Install tinyCam Monitor PRO on your old Android phone on the same network than your HC2 / HCL and make sure your phone is working 24/7 like your cameras do. Config your camera as usual Go to tinyCam Monitor PRO / menú / Settings / Web Server at set strong admin password and choose a port (I use, the default port 8083). Go to tinyCam Monitor PRO / menú / Enable Web server and check message: "webserver is running at http://192.168.1.10:8083" Test it on your computer browser, Google Chrome as example and login with your admin / password of step 3. You will be able to see a welcome screen with some information. I recommend that you Enable "Background mode" and "Power safe mode". In my case I have 2 x RSTP H.264 IP camera and is using about 30% CPU (2014 Android phone). Fibaro HC2 Configuration: Add new IP Camera, Choose as a model Axis Generic and go to Advanced tab You should take care of user, password, IP including port (the same that you setup at tinyCam Monitor PRO Webserver) JPG path: axis-cgi/jpg/image.cgi?camera=1 MJPG path: axis-cgi/jpg/image.cgi?camera=1 Check [ JPG ] 3 s. and Show it on main screen and [ v ] Send STOP If you have more than one camera, you need to add another IP Camera on Fibaro with exact configuration, but you should change in JPG and MJPG paths, camera=2, camera=3... and so on That's all! I hope you like it and it helps you -
Version 1.1.0
82 downloads
Hello Everyone, I 've tried Konnected alarm panel in parallel with my old alarm system, and it is working great. (Konnected) My task that was assigned to myself was to integrate Konnected directly to my HC2. So with a little LUA magic we have ready the Konnected Virtual Device for HC2. You can find the Virtual Device Repository here. Enjoy! -
This is a Quickapp script for HC3. I am trying to get this to work in a VD on HC2. Is it possible, or do I have to do it together with a scene to make it work? Can anyone help? function QuickApp:onInit() self:updateProperty("unit", "kr/kWh") self.refresh = 60 -- in seconds local function loop() self:webrequest(); setTimeout(loop,self.refresh * 1000) end if self.username ~= "changeme" then loop() end end function QuickApp:webrequest() local tid = os.date("%R") local minutt = os.date("%M") --OPPDATERER STRØMPRIS OG SNITT HVER TIME if (minutt == "00") then self:OppdaterPris(); self:OppdaterSnitt(); end end function QuickApp:OppdaterPris() --Opprette lokale variable local GammelStrompris = fibaro.get(126,"value") local NyStrompris --Definerer http local http = net.HTTPClient(); --Definerer strengen Payload til å være kommando til tibber local payload = '{"query": "{viewer {homes {currentSubscription{priceInfo{current{total}}}}}}", "variables": null, "operationName": null}'; --API.POST til Tibber-- http : request('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '.........', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = payload -- Query. }, success = function(response) --fibaro.debug (response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); --fjernet local under??? NyStrompris = json.encode(data.data.viewer.homes[1].currentSubscription.priceInfo.current.total); self:updateProperty("value", tonumber(NyStrompris)) --print("OK") end, error = function(err) fibaro.debug ("Error:" .. err) end }); end function QuickApp:OppdaterSnitt() --Definerer http local http = net.HTTPClient(); --Definerer strengen average til å være kommando til tibber local average = '{"query": "{viewer {homes {currentSubscription{priceRating{daily{entries{total}}}}}}}", "variables": null, "operationName": null}'; --API.POST Til Tibber http : request ('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '...............', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = average -- Query }, success = function(response) --fibaro.debug(response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); local Nypris = tostring(json.encode(data.data.viewer.homes[1].currentSubscription.priceRating.daily.entries[31].total)); self:updateProperty("log", tostring(Nypris)) end, } ) end
-
All, randomly I see some of my devices bahving strange. First TZ75 roller shutter occasionally, w/o any pattern would either open or close the blinds without any scene or other user interaction. Then recently my garden gate would open (Nice engine with IBT4ZWAVE module) though not requested through script or any other user action. Worst so far, my irrigation, managed with an FGS2x3 (Fibaro device) would just switch on, not even sending a proper signal back to the HC2, so it seemed switched off although it was actually switched on. Some additonal information - IBT4ZWAVE - I can see the action in the HC2 log, but it's certain that no scene or user request was triggering the action (remotes were at home, we were on vacation, no scene related to gate was active) - TZ75 - Most of the times there is a log entry with multiple values added e.g. open 70% or close 100%. Funny thing is that I don't have a scene requesting to open by only 70% - FGS2x3 - The most scary one as neither in the log file nor in the Yubii application would state that the switch is off, although it's running Happy for any advice. Let me know what else you need to know. Setup: HC2 ver 4.620
-
When I tried to include a new device (a Sensative Strip), the HC2 responded by displaying the message "Requesting neighbours, please wait" every 5 seconds. The device was not included. I have been through this twice now, once with "Network wide inclusion" checked, the other without. The only way to terminate the loop is to restart the HC2. What is going on? My software version is 4.600. I re-meshed the entire network between the first and second attempt, to make sure that the z-wave mesh is OK. What else can I do?
-
Witam wszystkich. Może temat już był, ale jestem nowy i nic nie udało mi się wyszukać. Mam 8 sztuk FGR 223 w wersji 5.1 i te działają normalnie. Podnoszą i opuszczają rolety. Mam jedną od znajomego używaną i moje HC2 widzi sterownik jako wersje 3.1 i że jest to sterownik od oświetlenia. Czy da się to uruchomić by na HC2 sterowało roletą czy to już śmieć. Reset poprzez przytrzymanie włącznika do żółtego i klik nic nie dają. Podczas ponownego parowania cały czas nie widzi jako sterowonika rolet. Proszę o pomoc! -
I am writing a scene which needs to set the setpoint temperature of my Z-TRM2 thermostats using a LUA command in HC2. I plan to address each thermostat individually, not through heating panels. The current value is succesfully retrieved by this command: fibaro:getValue(id, "value") where id is the id for the setpoint sub-device of the thermostat. This works as expected. However, when I try to change the setpoint through this command: fibaro:call(id, "setValue", "18") nothing happens, as shown by a subsequent getValue call. There is no error message, but the setpoint remains unchanged. I have tried to use the numeral 18 in stead of a string, and I have also tried with a variable name.What am I doing wrong in my fibaro:call command? The syntax is taken from the LUA API documentation, where this example is given: -- 'setValue' action call with one additional parameter fibaro:call(12, 'setValue', '23'); Is the required command for the Z-TRM2 module different?
-
I am currently using HC2 and will be migrating to HC3 which I have and is live with 2 devices. I need to rewrite my scenes and VDs etc. Question - will there be any interference between the devices owned by HC2 and the ones owned by HC3 ? The reason I am asking is that the whole stuff is so flaky. Devices used to go dead all the time. After literally 5 years of contacting suppliers, installers, support and engineers, I finally figured out the main problem in my network. My conclusion/assumption is. It turns out that 2 devices had removed themselves from the "control panel" as the support call it. I had not realized this as we never tried controlling them from the app or scenes. And devices around these were using them for hopping messages, which the HC rejected. Once I re-enrolled these two (after searching for them all over the house), everything has been running sweet, for the first time in 5 years. I would call this extremely flaky thinking, process and code !!!! And I am beginning to think that I might be up for more pain from similar stupidity happening between the two HCs.
-
I have a number of smoke sensors, one in particular that is about 6 feet from the HC2 beeps intermittently. The HC2 is not reporting a low battery so I can only assume its Z-Wave connectivity issue. The smoke sensor is not marked as dead nor are there any Z Wave issues in diagnostics. When will the HC2 log that this is an issue in the event log. If nobody is there to hear the beep, how are you ever meant to know there is an issue ?
-
HUNTER HYDRAWISE Irrigation System
gucio1234 posted a question in Other Devices / Third-party devices
Has anybody tried/managed to link Fibaro HC2 with the Hydrawise Irrigation system controller made by Hunter : https://www.hydrawise.com/ This controller connect to the network via WIFI. I appreciate any comment on this ... -
Hue white color lights issue with Fibaro
amatt posted a question in Other Devices / Third-party devices
I purchased some downlights that work with Hue. I added them to hue and ensured they work. then I added them to fibaro using the plugin with no issues. I set the color to what I want in the app (in this case I want bright white). I run a scene to figure out the value, brightness and saturation. I then put it in a VD as a saved color. once I press the saved color in fibaro the light changes to an off blue color instead of bright white. I can get the light back to a bright white by going to the hue app and adjusting the color so I know its not the light itself. Does anyone know if Hue changed a setting that does not allow the light to change to the correct color? in the app they have 2 different selections for colors and White not sure if this makes a difference on fibaro now. HC2 latest OS @T.Konopka
