Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


FunkFib

Member
  • Posts

    66
  • Joined

  • Last visited

About FunkFib

Profile information

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

Recent Profile Visitors

329 profile views

FunkFib's Achievements

Learner

Learner (2/8)

14

Reputation

  1. Hello I'm not a network specialist but the zero(0) in your Network-Adress could be a problem. Only a idea. 192.168.0.200
  2. Hello Sankotronic, Hello Geoff I'm just in the install process from UHAS Beta to the release version. The package is hugh. Till now I have only installed the neccessary modules of UHAS. I had only one small problem with "-- System Translations Scene - Version 1.3" scene code: In the german translation the ", is missing after Südhalbkugel (Row 56). The manual is very helpful and it is in the length of a novel ? Very well structured and you can quickly jump to the respective area from the table of contents. Need more time for install and config. A big thank you to you ? I will report back if there are corrections needed.
  3. Hello, maybe this side helps: http://manuals.z-wave.info/#/
  4. I've also thought of switching to stand alone. Please do not get this wrong, but I stuck in Beta Version from 2018: --[[ Weather State VD - Version 2.2 beta 7 (UHAS compatible) Copyright (c) 2018 Zoran Sankovic - Sankotronic (Author). All Rights Reserved. --]] It feels like the other users can install newer upgraded modules. But there are many reasons to leave it that way. All modules work without any errors since 2018. This is great and I use it every day. I will continue to wait patiently. UHAS will definitely be a stable, functional HC2 extension when its done. ? Thank you Sankotronic ?
  5. Good news ? I'm looking forward to the final version of UHAS. I am very excited. Especially on the SECURITY MODULE with the Netatmo Cameras suite (VD+scene), because I don't have my own programming here yet. The Presence VD will help us a lot because we often forget to start the alarm system with the Zipato key pad. Home schooling and home office has changed the daily routine. Stay safe and find a balance between work(coding) and family ? Greetings Manuel
  6. Hello, you have to look at this: --[[%% properties%% weer <--- %%weather747 CentralSceneEvent%% events%% globals--]] Hope this helps
  7. Hello, if someone pulled the head from the thermostat it had demaged. Are the snaps of the Fibaro thermostat demaged? Sind die Rastnasen beschädigt oder abgeschabt? Ist der Pin des Thermostates wirklich leichtgängig? Eventuell mit einer anderen Heizung vergleichen ob der Monteur richtig liegt.
  8. Hello @Sankotronic, welcome back at home. It's definitely not easy to be away from home for such a long time. Note: I am still interested in UHAS for the HC2. Maybe next year HC3? Especially the part for presence automation. The Netatmo doorbell and an outside camera are waiting for the (hardware)installation on my table. I am patient and wait until you are satisfied with the result of the code. Greetings Manuel
  9. Hello, I use the UHAS Version HUE AIO VD: Hello Sankotronic -- Hope the upload is ok. Stay safe on your long trip HUE_AIO_v3.0b9.vfib.json
  10. Hello, the complete text is only for HC3 transfer. Version 4.590 The possibility of transferring the cloud backup to Home Center 3! - Use the Transfer Configuration feature available from the Remote Access (home.fibaro.com). - Both gateways must be assigned to the same Fibaro ID account and available on the Home Center list. - The backup must be created on version 4.581 or higher. - Home Center 3 must be on version 5.021 or higher. - All Z-Wave devices, their configuration, room assignment, associations and parameters will be transferred. - If you have thermostats, they will await reconfiguration. - Scenes will not be moved and need to be created again. - Virtual devices will not be moved. Use a new tool - Quick Apps - to implement them. - The gateway from which you are moving the backup will still be available, but the devices will no longer communicate at all. - The migration process cannot be undone - it is irreversible. I can confirm this just updated the HC2 to 4.590 Scenes are working / some Fibaro thermostats needs a reconfiguration (not a new inclusion).
  11. Hello Sankotronic, I have added the possibility to switch off the scene with a global Variable local applianceStatus = "Trockner"; local applianceStatusMapping = {On="An", Off="Aus"}; but I found this in the code: if ((tonumber(fibaro:getValue(deviceID, 'power')) > deviceMinPower) and (StartSource['type'] == "property")) then logbug ("green", "Appliance monitoring scene started version "..version.." - © 2016 Sankotronic"); --> fibaro:setGlobal(applianceStatus, applianceStatusMapping.On); <--- This part set allways the Status to On and the below if statement is true so its not possible to switch the scene to off. Perhaps I'm wrong. and I don't understand what I can do with this status variable. Edit 22.03.2020 21:50 : Ok I'm wrong the variable will be changed by scene to actual status. I search for a way to complete switch the scene off because sometimes in the whool prg the scene starts several times and my wive is not amused. Manuel
  12. Hello, you can use Sankotronics "UNIVERSAL ALARM SCENE -- FIRE/FLOOD/OTHER DETECTION" then add in this section: -- use this function to add code that will be executed after all other -- code when sensor is breached function extraUserCodeBreachLast() -- your code goes here fibaro:call(your AOI VD ID, "setSlider", "3", "100") <--- this is brightness 100% fibaro:sleep(1*200) fibaro:call(your AOI VD ID, "setSlider", "4", "0") <--- this is RED fibaro:sleep(1*100) fibaro:call(your AOI VD ID, "setSlider", "5", "100") <--- this is saturation 100% fibaro:sleep(1*100) to switch them off you can also add this to the safe state section: -- use this function to add code that will be executed when sensor is -- back to safe state function extraUserCodeSafe() -- your code goes here fibaro:callyour AOI VD ID, "pressButton", "1") <--- this switch off(or On) the light But if you wan't to use the the global variable table HueMain you have to read the manual and use the described commands. fibaro:call(hueID, “setSlider”, hM[hueID].hueSli, value) for red you have to use value 0 or 100 ? Manuel
  13. FunkFib

    All-in-One Scene

    Hello, I switch Fiona from V1,1 to 2,0 ? Everthing looks fine LED's match to HC2, thats a nice add on. And if you compare the time you can see at the sunHours where you can find me at the globe ☺️ cag014 many thanks for this improvements. Now I have to look at the new possibilities of your AOS 2.0...
  14. Hello, I'm not a LUA pro but this code will be execute to late. That means you defined the local variables at the end of the script when the device reach for 5 min 0 Watt, but you use them at the start. If I'm right you have to move this code to the beginning of the script. move this code to -- EXTRA GLOBAL VARIABLES ----------------------------------------------------- here you can add your extra global variables to enhance features of this-- scene: local Jacob = "JacobPresentstate";local JacobMapping = {Yes="Away", No="Home"};local Andy = "AndyPresentstate";local AndyMapping = {Yes="Away", No="Home"}; Sankotronic explain this above. Then is local deviceMinPower = 0; I don't know if this works are you sure that the device reach this value?
  15. Hello, fine that your problem is solved. I have some Information for you: Blue means that the dimmer starts Auto-calibration. Can you check your parameter 175? If this parameter is not 0 the device starts Auto-calibration by itself(see Screenshot). If you have problems again you can change the parameter 150+151 reducing the parameter 151 to a lower level ca. 50% so a load error will be not present and no Auto-calibration started. Then you can increase the parameter 151 step by step and find the maximum brightness level without an error. I have checked the blue LED flash with my device and can confirm that it blinks in your shown blue color(Video) when the device make the Auto-calibration. The Auto-calibration process will set the dimm levels on 6%-63% with two GU10 5W LED dimmable light spots, but I will change them back to my previous settings. Range test you can start with Magenta LED signal see Screenshot. I hope this helps if the error occurs again. Manuel
×
×
  • Create New...