Jump to content

Search the Community

Showing results for tags 'hc2'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





Found 246 results

  1. Hi Everyone Smart Message Hub v1.2 (SMsgH v1.2) is now available. This release includes fixes tor three bugs that had various impacts and support for international characters. Thanks to @Sankotronic and @szmyk for locating the faults and extra feature for international characters "FIRST TIME USERS" - Please read below and follow the instructions laid out for first time users UPGRADING FROM 1.1b to 1.2 - Please use this Post - if you are a current user and may wish to consider avail of the fixes or extra feature This scene enables a user to send a message from either a scene or a virtual device to a number of notification and TTS services with a startScene call fibaro:startScene(682, {message, target}) -- Using ID of scene fibaro:startScene(SMsgH, {message, target}) -- Using HomeTable reference The scene also enables messages to be re-routed or queued depending on whether the house is set to Away mode, Sleep mode or if internet is not available. (See below for more details) A demo VD {v1.1} is also available to help demonstrate the scene features. SCENE FEATURES Smart Configuration options include the ability to re-route and/or queue all messages under certain conditions. (Internet unavailability , home occupancy mode presentState = Away) Messages with international characters are also supported Notification messages can be redirected to Home Center 2 Popup notification service if the internet is offline or unavailable Notification messages can be queued if the internet is offline or unavailable. All Messages in the queue will be released as one combined message once the internet come s back online. All TTS messages can be redirected to Home Center 2 Popup notification service if the internet is unavailable or offline or if the sonosAPI is offline if this solution is being leveraged All TTS messages can be queued if presentsState = Away. All TTS messages in the queue will be announced once presentsState = Home Simplified the message invocation method to startScene Invoked via startScene(SMsgHid, {message string} (SMsgHid is the id of the SMsgH scene when it is saved to your system ) See below for examples messageHub global no longer required (please delete when you have migrated all your scenes to using 1.1) Added support for sleepState (no TTS messages if set to Sleep) Additional support for HC2 popup notifications Types (Critical, Successs, Info, Warning) Images (use full url) Buttons (represented as a table) - See @Sankotronic [TUTORIAL] on popup notifications to see how to format Added ability to delay unloading of TTS messages by predefined time in seconds Added support for custom language in for TTS and Notify redirects default Popup title and subtitle Minor bug fixing and code cleaning Configuration options also include a default message notification target, title, subtitle and volume but all these can also be specified as part of the message invocation. There are three levels of debug verbosity. In normal mode there is a minimal amount of information displayed as the scene is triggered. The two other modes allow for much more expressive displaying of scene variables as well as configuration settings if enabled deBgVar is enabled in the scene so you can see the interactions- it can be disabled in normal running mode SCENE MESSAGING OPTIONS The supported services in this release include the following (supported in 1.0 & 1.1) Pushover Notifications -------------------------------------------------------> [TUTORIAL] on creating Pushover account and set up allinone ( jompa68 scene) Telegram messages hc2email (Home Center 2 email service) hc2push (Home Center 2 push notification service) hc2popup (Home Center 2 Popup Notification service) -------------------> [TUTORIAL} Popup Noification and Custom Inages Sonos-api based TTS --------------------------------------------------------> [TUTORIAL] Setting up and using Alternative Sonos VD using node-sonos-api Sonos VD Remote based TTS -----------------------------------------------> Discussion on Sonos Remote V1.0.0 beta I have also included a Companion Demo VD. The virtual device will allow the user to demonstrate the scenes queuing/unloading capabilities. CAUTION: The companion VD in demo mode can adjust the presentState and sleepState globals and will cause any other scene you may have with this as a trigger to execute A simplified version of the LAN Monitor VD called the WWWAPI Monitor will monitor just the sonos-api if desired and does not any in-built notification options like the LAN Monitor VD 2.5.Smart Message Hub users should use either the WWWAPI Monitor or LAN Monitor 2.6 Special thanks extended to @Sankotronic @petergebruers, @jompa68 and @szmyk for their contributions leading to 1.2 Once the scene configuration is complete I would recommend running the demonstration virtual device. This will give you a better understanding of the options and features as well providing some sample messages that you can run. Ideas for subsequent revisions are always welcome _f RELEASE CHANGELOG v1.0 - First release (march 4th 2017) v1.1 - Second release (march 17th 2017) v1.2 - Third Release (june 24th 2017) ================================================ FIRST TIME USERS - INSTALLATION & CONFIGURATION ================================================ The code is available in both lua and txt format below Paste code into scene and run - All global variables will be automatically created (Please do not adjust global triggers in scene header) Configure options as required at top of scene (line 100 onwards) Configure enable smart redirects Configure HC2 email settings, HC2 push settings and TTS services Configure default message titles, subtitles and volume Configuration notification settings, tokens, etc Enable/Disable increased debug and config verbosity for troubleshooting MESSAGE INVOCATION This message hub can be called from either a scene or a virtual device using a startScene call. The following is an example Sample invocations are included below Please see the section on Message Invocation lower down in this post of you wish to send messages with international characters local message = "Warning: Utility room freezer temperature is 10 degrees" local target = "hc2popup" local volume = "25" -- (can be left as "" if not TTS message) local title = "new alert title" local subtitle = "new subtitle" local popType = "Critcal" local popImg = "" local popButtons = "" fibaro:startScene(IDofSMsgHscene, {message, target, volume, title, subtitle, popType, popImg, popButtons}) Note: Replace IDofSMsgHscene with HomeTable reference of numerical ID of the SMsgH scene when it is installed on your system You need to include all parameters up to last one you populate. For example, if you want to specify a subtitle, you need to include message, target, volume and title as well. You CANNOT leave out a parameter in the call. Leave as "" if not used/required and default will be invoked. **USER CONFIGURATIONS & SETTINGS** OPTIONS FOR SMART RE-ROUTING OF MESSAGES The following four options can be set to true or false depending on what features you wish to enable. local tts2popup = "true" Set to true to enables re-routing of sonos TTS messages from either the Sonos VD or the sonos-api solution to HC2 notification Popup if the sonos-http-api or Internet is unavailable/offline to your local LAN local tts2queue = "true" Enable to Silence TTS announcement in sleepState, TTS announcements are NOT queued, they are simply discarded local tts2sleep = "true" Enable a Delay before TTS announcements are unloaded (seconds). Leave as "" for no delay local ttsUnloadDelay = "" -- seconds Set to true to enable Sonos TTS messages to queue when presentState = 'Away'. When presentState is set to Home it triggers the scene to automatically unload all the messages in the TTS queue to the default player that has been named in the configuration section local notify2popup = "true" Set to true to enable all notifications to re-route to HC2Popup notifications if the internet is unavailable/offline to your local LAN local notify2queue = "true" Set to true to enable all notifications to queue when presentState= 'Away'. When presentState is set to Home it triggers the scene automatically and unloads the message in the notifications queue to the default notification service that has been named in the configuration section below The scene as provided has all these 4 options set to true and this is the recommended setup if you wish to leverage full functionality and the demo OPTIONS TO MONITOR THE INTERNET STATUS To achieve the most benefit from this scene the internet and sonos-api should be dynamically monitored. Dynamically monitoring the internet will enable messages (TTS and notifications) to be queued while the internet if offline. Queued message can also be sent as hc2 pop notifications on the local LAN. The preferred monitoring option is named here. The example below is setup to use the LAN Monitor VD 2.5 local ipMonitor = "networkTable" There are 3 options available: Select 'manual' if you wish internet and sonos-api to be permanently set to online. Please note that this option does NOT enable queuing of notification messages. Select 'networkTable' to leverage the LAN Monitor VD 2.5, Select 'wwwapiTable' to leverage the new simplified WWWAPI Monitor 1.0 HC2 EMAIL CONFIGURATION hc2emailUsers = {["su"]="2", ["frank"]="1564", ["sylvia"]="1565"} List all users that you want to be able send messages to. The user id's are located from the HC2. Select Configuration, then Access Control to see the current users. HC2 PUSH CONFIGURATION hc2pushUsers = {["DadiPh"]="563", ["MumiPh"]="155", ["DogiPa"]="175"} List all users that you want to be able send push messages to. The mobile devices ID can be found by going to http://<HC_IP>/docs/ and looking under iosDevices section. local defhc2pushUser = "563" -- identify default hc2push user Select a default user from this list and this is used if there is no user specified as part of the message invocation. TTS PREFERENCES Select your TTS preference. If you use the sonos-http-api solution please enter API. If you use the Sonos VD Remote solution please enter REM. local ttsMethod = "API" Default volume for TTS announcements local defTTSvolume = "12" This allows you to select a default volume and this aplies to both the API and REM sonos solutions. This volume can be changed by including a different volume in the message invocation SONOS-API PREFERENCES Configure this section if you have selected API in the above section. APIplayers = {"hallway","kitchen","bed5_office","landing"} List all the sonos players you want to send TTS messages to. The zone/player names must match exactly what is on your sonos native application local defAPIzone = "bed5_office" The default player/zone selected is used to unload the TTS message when presentState = Home. The default player must be included in the overall players list above local APIipaddress = "" local APIport = "5005" The ip address and port are of the device that is hosting the sonos-api local defAPIlanguage = "Amy" The final item here is the language or voice code for the respective TTS service. Thisoculd be something like en-gb for google or Amy for AWS Polly SONOS REMOTE VD PREFERENCES Configure this section if you have selected REM in the above section. REMplayers = { ["kitchen"] = {vd="295", btn="28"}, ["hall"] = {vd="765", btn="27"}, } List all the sonos player virtual devices you want to send TTS messages to. The virtual device id's and process button id’s much match exactly what is on your HC2 for each virtual device. Please note the process button may differ if you have modified the standard virtual device. local defREMvd = "hall" -- Id of player vd for unloading queue The default player/zone is user to unload the TTS message when presentState = Home. This zone must be included in the overall REMplayers table and the name must match exactly. local defREMlanguage = "en-gb" The final item in this section is the language or voice code for the respective TTS service DEFAULT TITLES AND SUBTITLES This scene has default titles and subtitles and these are used if no title or subtitle is included in the message invocation. local defTitle = "Alert Title" local defSubtitle = "Alert Subtitle" Adjust the default titles and subtitles as you require. Note: Subtitles are only used for PopUp Notifications NOTIFICATION SERVICES There is a broad range of notification services available to use. Some are native to the home center and others are third party services provided by external vendors. local defmessageSvc = "pushover" Select the default notification service that you wish to use. This default service will be used if no service is invoked in the message and is also used as the service to unload the queued messages when presentState = Home PUSHOVER CONFIGURATION This service is provided by pushover.org. You will need to register with them and obtain a token and user key. local POtkn = "" local POusr = "" Once registered you will need to select the devices that you wish to send the pushover notifications to. Once they are added to your pushover account you will need to add their details below. Currently there is only one setting for device which means that all messages to pushover will be send to the devices named in this list. Priority can be set at ) like I have below local POdevice = "Dad_Ph, Kit_iPad, Landing iPad" local POpriority = "0" TELEGRAM CONFIGURATION This service is provided by telegram.org. You will need to register with them and obtain a token and a chat ID local TGtoken = "" local TGchatID = "" DEBUG VERBOSITY OPTIONS This allows a number of levels of debug verbosity. There is a minimal amount of debug window responses running in normal mode but these two capabilities allow the user to observe extra information in the debug window when the scene is running. local deBugVar = true -- deBugVar will display the scene variables local deBugCfg = false -- deBugCfg will display the scene configaution that you have set OCCUPANCY/PRESENCE STATE I am also supporting the presentState as it is defined by Sankotronic and others. -- "PresentState" is predefined global value that determines if you are at home -- or away. This variable value is set by other scene or VD. Enter name of your -- global variable between "" if called different or leave as it is local presentState = "PresentState"; -- Enter corresponding values that you use for presence in your language. Change -- the one in quotes or leave as it is local presentStateMapping = {Home="Home", Away="Away"}; HOMETABLE There is also support for the hometable solution. Hometable is a approach to storing all device ID in a global variable. Please Uncomment the following line if you wish to use Hometable data in scene -- local jT = json.decode(fibaro:getGlobalValue("HomeTable")); POPUP MESSAGE TYPES Default popup message type, possible values: Success, Info, Warning, Critical. Please define popup message default popup type, button caption and buttons if you wish These defaults can be left as is or modified/translated into your own language local defPopType = "Info" local defPopCaption = "OK" local defPopButton = { { caption = defPopCaption, sceneId = 0 }} Please refer to Sankotronic Tutorial "Popup Notifications and Custom Images" for format and examples POPUP REDIRECT TITLES AND SUBTITLES Please amend the text sent to PopUp Notification when Internet or TTS is offline to your own language if you wish. Both Title and subtitle can be modified local TTSofflineTitle = "Announcement" local TTSofflineSubtitle = "TTS is offline, TTS announcement sent as popup notification" local WWWofflineSubtitle = "Internet is offline, TTS announcement sent as popup notification" SAMPLE MESSAGE INVOCATIONS The message function can be invoked with as little as one parameter or as many as five parameters. The following examples will provide a good understanding. Send message to default notification service, with default titles/subtitles fibaro:startScene(682, {message}) -- Replace 682 with id of your SMsgH v1.1 scene or a hometable reference Send message to specific notification service (The notification service must match exactly what is contained in the notifySve table in the variables section) fibaro:startScene(682, {message, target}) (The hc2user in the message invocation must match exactly what is contained in the hc2emailUsers table in the user configuration section) fibaro:startScene(682, {message, "hc2email"}) - send to superuser fibaro:startScene(682, {message, "hc2email frank"}) - send to user frank fibaro:startScene(682, {message, "hc2email frank su"}) - send to user frank and superuser (The hc2push device in the message invocation must match exactly what is contained in the hc2emailUsers table in the user configuration section) fibaro:startScene(682, {message, "hc2push DadiPhone"}) - send to superuser fibaro:startScene(682, {message, "hc2push MumiPhone SarahiPhone"}) - send to mumphone and sarah phone (The sonos player name in the message invocation must match exactly what is contained in either the APIplayers or REMplayers table in the user configuration section) The target can also specify sonos player or VD id for TTS with options fibaro:startScene(682, {message, "kitchen"}) -send TTS to kitchen, default volume fibaro:startScene(682, {message, "hallway", "10"}) -send TTS to kicthen, volume=10 Custom titles and subtitles can also be specified. These will overwrite the default titles and subtitles. Subtitles are only available for HC2 Popup notifications. They can be used with or with a target notification. If the target is omitted it will send to the default notification service that has been named in the configuration section local message = "what ever the message is" fibaro:startScene(682, {message, "", "", "Alert !!", "The wine fridge temp is rising"}) Finally an example of a Message to popup with specified popup type local message = "kitchen window has been breached" fibaro:startScene(682, {message, "hc2popup", "", "Alarm", "House Breach", "Critical"}) MESSAGE WITH INTERNATIONAL CHARACTERS If you want to send message with special characters just use urlencode function: fibaro:startScene(682, {"message", "hc2email", "", "title"}) -- without special chars fibaro:startScene(682, {urlencode("message ąść"), "hc2email", "", "title"}) -- with special chars fibaro:startScene(682, {urlencode("message ąść"), "hc2email", "", urlencode("title ČčĆ抚ĐđŽžáäéè")}) -- with special chars COMPANION DEMONSTRATION VD INSTRUCTIONS (1.1) A number of sample notification and TTS messages can be activated giving the user an understanding of the message invocation format and options Demonstration mode enabled the toggling of 'Internet online/offline', presentState Home/Away, sleepState Sleep/Awake modes. This capability allows the used to observe the queuing and unloading of queued notification messages and TTS messages in action. Import the VD into your home center 2. Review the messages and adjust based on your own implementation of Smart Message Hub Send messages and TTS as required To demonstrate the queuing and unload of queue’s Set demo mode to ON. Send messages and TTS and observe in selected notification services and apps, Set internet to offline, sent messages and observe queuing, Set internet to online, observer unloading of queue. Set presetState to Away, send messages and observe queuing. Set presentState to Home and observe unloading of queue. Set sleepState to Sleep and observe TTS are silenced. For normal operation - set Demo mode to OFF FILES [Smart Message Hub SCENE] SMsgH 1.2.lua (lua file) WWWAPI Monitor Virtual Device [VIRTUAL DEVICE] WWWAPI_Monitor_1.0.vfib Companion Virtual Device [VIRTUAL DEVICE] SMsgH_Demo_1.1.vfib
  2. Stoję przed wyborem systemu do swojego mieszkania i proszę o pomoc w podjęciu decyzji. W chwili obecnej chce sprawdzić jak działa w ogóle Fibaro w moim mieszkaniu a następnie przenieść to do domu. W mieszkaniu nie będę stosował rozbudowach rozwiązań tylko zwykle włączniki, kamera ip, czujniki drzwi itp. Moje pytanie brzmi: 1. Czy wybrać HC2 czy Lite? Jakie są różnice? 2. Który system daje więcej możliwości, jest bardziej przyszłościowy i jak jest rozwijany HomeKit czy Z-Wave? Dziękuje za podpowiedź!
  3. So I have two houses with a hc2 in both. I also have a set of Google home minis in both houses. However I'm only able to use voice to control one of the houses and the devices from the other house is not visible in the Google home app. I can add the devices from the other house by talking to fibaro and after listing devices choose the hc2 from the other house, but of course then the devices from the other house disappear from the Google home app... I don't know if this is for Google to fix or if Fibaro can list all devices for both hc2's. Any suggestions on how to fix this problem is appreciated.
  4. Hi! I have setup google home and linked my Fibaro Home Center 2, when I asked Google Assistant to talk to Fibaro, a dude speaks out saying "I couldn’t find any devices." Is it because of software version? Do I need to update to the latest 4.153 beta version?
  5. 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...
  6. Hi all, I would like to share a 100% working solution for HC2 / HCL users that want to use new IP cameras working with RSTP, 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" 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
  7. freelife996

    Ezviz camera ?

    Hi, I have a EZVIZ Camera CS-CV310 and I wonder how I can add it to the HC2 as there is no plugin for that camera. Any thoughts?  Thanks
  8. asmith40444@gmail.com

    [SOLVED]Harmony Hub Plugin for HC2

    Hi - Brand new to this. I have an HC2 and Harmony Hub. Both were working well until recently where connection was lost. I factory reset the Harmony and attempted a reload of the Harmony Hub Plugin. The plugin loads and i am able to get the Harmony Pin. On copying and saving it to the HC2 i get the message "Undefined error" Further attempts also fail. Has anyone had this problem and is there a solutioin? Cheers Andrew
  9. 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
  10. When do I use the following code in lua:? tcpSocket:disconnect(); i some sample code it has been added to the sample in others not. example: -- Volume 40dB -- tcpSocket:write("MV40".."\r") fibaro:sleep(500); result, err = tcpSocket:read(); tcpSocket:disconnect(); if (err == 0) then fibaro:log("transfer OK"); fibaro:debug("transfer OK"); else fibaro:log("transfer failed"); fibaro:debug("transfer failed"); end ------------------------------------ -- HERE its not been used -- tcpSocket:write(string.char(0x53, 0x49, 0x49, 0x52, 0x41, 0x44, 0x49, 0x4f, 0x0d)); fibaro:sleep(1000); result, err = tcpSocket:read(); if (err == 0) then fibaro:log("Transfer OK: Internet Radio"); else fibaro:log("Transfer failed: extra check"); -- check source: needs 2 times... otherwise still failed... tcpSocket:write(string.char(0x53, 0x49, 0x3f, 0x0d)); fibaro:sleep(500); result, err = tcpSocket:read(); tcpSocket:write(string.char(0x53, 0x49, 0x3f, 0x0d)); fibaro:sleep(500); result, err = tcpSocket:read(); if (err == 0) then if ( trim(string.sub(result, 1, string.len(result)-9)) == 'SIIRADIO' ) then fibaro:log("Transfer OK: Internet Radio"); else fibaro:log("Transfer failed"); end else fibaro:log("Transfer failed"); end end
  11. Hi community, Perhaps you can help me understand how (if) to connect two houses that each has a HC2 and have them connected to my Google Home Mini for voice control. Setup I have two houses, in each house I have a HC2 that are linked to my Fibaro Cloud account. I can access them both remotely and everything is working fine through the app on my phone and as well as from computers. In each house I also have a Google Home Mini, that are configured to talk Swedish AND English. I live in Sweden should I say as well. Problem I've managed to link my Fibaro account to the Google Home app on my phone but only the devices in ONE of the houses are SEEN and can be controlled trough Google Home or Assistant. I've done multiple unlinking and re-linking as well. Both HC2's are on 4.510 I can switch to English and say "talk to Fibaro" and it lists both devices and I can control them from there. But through the Google Interface only the devices in one of the houses are seen - if you follow me here Any guidance or ideas to test would be highly appreciated! Have a good Saturday out there!
  12. hello i have 2 yale conexis L1 locks and the z-wave module to go with it. Back in June the modules included into my system with no issues whatsoever and i can now use fibaro to lock and unlock the doors and in scenes etc. However my sister decided to get this lock aswell and we tried to include the module but it is not including at all!!! the firmware version was 4.134 beta and i updated to 4.136 beta and still i get the same response, no inclusion at all. the timer on the fibaro just times out... i have tried to include using the 'LOCK' include and also tried to include in the usual 'ADD DEVICES' method and checking the box to add in secure mode and no response. does anyone else experience this issue? My system is currently on 4.134 and the modules are still working properly. thanks
  13. Can someone help me. I have been thinking about how the logic would work and cannot come up with the correct Lua code to make this work correctly. Goal: want the door to unlock when I arrive at home and lock when I leave and send a message (push, email etc..) every time. but if I am home/not home I don't want it to keep locking/unlocking and sending me a message *I already have fibaro looking for my phone to see if I'm present. a global variable keeps a number count present =1 not present = 0 so the logic I came up with is like this: Check Present=0 then lock door and send message check present =0 (still not at home) do nothing check present = 1 unlock door and send message check present = 1 (still at home) do nothing etc... let me know if you have questions or suggestions.
  14. Guest

    I lost my login ID for HC2

    Hi, Recently My HC2 went into recovery mode, but unfortunately when i tried to log in again into it, it happens that i forgot the login id, if there is anyway or someone who can help i can talk to please let me know. Thanks in advance.
  15. I get the following JSON string from my device in a browser by typing the IP of my device: {"data":{ "id":"8200007A","type":"8","detector":"SI29BG","voltage":382,"cpm":14,"temperature":9.45,"humidity":48.29,"pressure":100281,"voc":12800000,"co2":399,"noise":39,"ch2o":0.00,"pm25":3,"uptime": 107787}} is it possible to import these values into a virtual device in HC2? The closest I have found is: local urad = Net.FHttp("") local urad = Net.FHttp("{{}}",80) local urad = assert(io.popen('curl')) but these will not get the json string This is a part question for my thread:
  16. My HC2 was running fine for serveral weeks on ver. 5.10. Yesterday I noticed, that I I can'nt connect using my Phone. I checked from my PC - same behavior. Internal Error! I than switched off the HC2 using the button at the back. Wait for a minute and switched it back on. Now I getting "Starting Services". I left it now for couple of hours. No change! I did switch it off and on aggain, but the HC2 is not accessable anymore. I did not made any changes to the HC2, I also did not add any devicves. What can I do to gain access and control again. It's quite urgent thx & regards Rolf
  17. alandee

    Camera small ok large not ok.

    Has anyone experienced / overcome the following ? My overview pictures don't work, but if I click a camera button the camera works fine, ( click the camera number button ) in realtime, and all is well, then when I rotate the phone to get full screen, I get a "No Video" and black screen. Going back to the overview I generally have to refresh network to get the smaller view showing again. The cameras seem to work fine otherwise, I can even pinch in in the overview screen. HikVision Turret and Cube cameras all exhibit the same behaviour. Any thoughts on where to start ? Cheers, al.
  18. PieterB

    Incompatible backup notification

    Hi there, My hc2 keeps on reminding me that the backups that i have made so far are incompatible and that I have to make new ones. But in the backup screen is says that the backups that I made so far are compatible. Is it a bug, and/or do more people experience this? Let me know. hc2.pdf
  19. Hi, my google home fibaro dude ( weird having a different voice ) keeps finding my hc2 with the correct serial number then when I select the number one for the device he finds he tells me “I wasn’t able to select home centre” .. so I’m not sure how to disentangle him from my google to resend the setup link and I’m so close its more frustrating than when I was using IFTTT !! Pretty fast responses too! Anyone know where / how to view connections in both directions so I can clear them and try starting again ? I’m on 4.153b and wonder if that has anything to do with it ? Cheers, al
  20. Hi All, We recently purchased a Roomba 690 (with built in WiFi) and I went with the iRobot brand specifically as its listed on the home page of the Fibaro website as a one of the device thats compatible with the Fibaro system. https://www.shopirobot.com.au/roomba-robot-vacuum-cleaner/roomba690-robot-vacuum-cleaner.html I've been through the available Add-ons on my HC2 as well as searching both these forums and the internet with no answers. Is there something I'm missing? Thanks, Mist
  21. alandee

    Integrated Alarm Suggestion

    Hi, My alarm system has finally died , for good this time, the panel was always a little dodgey, but now it's burnt beyond what I can be bothered trying to fix .. Anyway, I'd like to replace the complete alarm system with something I can integrate to a greater or lesser extent with the HC2. I remember someone posting something about a plug in board called .. envision .. i think ? and it might have been a plug in for DAS alarms ? But I can't find anything on that when I search so I've probably got the name wrong. I don't mind running wires, Actually prefer it for an alarm system, and I don't really mind what sort of cost there is if it ticks the right boxes. Although it's not essential, Ideally I'd like to have some secured integration also with gate and door control and also cameras all in one... but that wish list may have just put me into a fixed wired C-Bus or Control-4 system I expect. Does anyone have anything remotely like this that I can start researching ? It's difficult to know where to start as the suppliers of most of the alarm systems around here seem to have little idea about integration. Or to put it another way, what home alarm system do you have and how have you integrated it with your Fibaro system ? Cheers in advance, al.
  22. Henn Sarv

    HC2 - Dashboard - HEating

    Hi people, who knows about things, I'm quite new in HC2 so might this is reason but I don't understand the logic of dashboard. I have home with 10+ rooms, regulated heating with temp-switch pairs (smoke detector + smart plug or single relay = connected device) and 2 bath-ruums with "real termostates". To monitor overview of climate system I find that Dashboard - Climate - Heating is good for overview but - only my batchrooms appear there. All rest isn't here visible. On mobiile app - all "heated" rooms (together 13 rooms) all are listed on climate view. My question - why heated rooms aren't listed on Dashboard? With bests Henn Sarv
  23. Henn Sarv

    HC2 sharing with other FibaroID

    Hi Fibaro staff and users, I've in problem with HC2-FibaroID and user authentication for remote acces I haven't find the place where share access to HC2 to second (and third, etc…) FibaroID to allow remote access to my family members. Current I find only following ways 1. share full access to my FibaroID (name and password) with instructuon how to connect through this - not best way, becouse I don't like to give full access to all mu houses 2. direct HTTP flow through my firewall and ask them to access directly - extremly unsecure way becouse lack of HTTPS Could You give some hint, how to behaive or could you point me the right option or (on case lack of this) plan in future developments add that kind of functionality With bests Henn
  24. Hello, everybody, I have a problem with Home Center 2: I forgot user and password! How can I reevive a hard reset? I'm desperate!
  25. Version 0.2.0


    Device inventory scene Hello everybody, this is a simple scene that shows you all the objects in the HC2 and their number, no matter if zwave devices, users, virtual devices and so on. See the attached screenshot. The script does not need an autostart or other triggers, rather it is meant to be executed ad hoc. In any case, it is no longer necessary to count the devices by hand in the future.