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 'documentation'.
-
I'm asking the forum for support regarding the creation of software documentation in HC3. (please answer yes/no) I propose to create a button in the /app/settings/general/main location, which would make a documentation in the text format as similar as possible (included a graphical side) to the HC3 programming area in LUA scenes. The file name should be DocFIBYYYYMMDDTime.LUA. It would be used for comparison with older versions of the software in Visual Studio Code (Microsoft). I really appreciate the HC3 system. However, my customers and I lack a documentation of all scenes in the text format in one file. This collection would allow me and my customers to rewiev the previous data to remind ourselves the original state of the software and settings. When our system doesn't work, I would like to find what I have changed before or what have gone wrong. By comparing the original documentation with the new one, I would have an immediate overview. Furthermore, this documentation could be useful to search for the ID numbers in the scenes. As you probably know, sometimes we are forced to remove and add the ID again. This causes the ID to be renumbered. As a result of it, it is necessary to replace the old ID numerical codes with the new ones in all scenes. When renumbering the ID of, for example a three-phase electricity meter, it has to make 32 times. The structure of the documentation is described in the "BLOCK Scheme" below. An example of the documentation is given in the "Example of documentation" below. Experts may program in other languages and make extensive use of APIs, but the system is not intended for them, but for the general public. The public needs outputs perhaps more than experts. I would be grateful if FIBARO looked into this as soon as possible. With thanks for your cooperation ing. Petr Boltík "BLOCK Scheme the documentation" procedure CreateTXT(DocFIBYYYYMMDDTime.LUA); var i,sceneMAX: Integer; BlockScene: boolean; begin for i := 1 to SceneMAX do --the main passage if exists(scene[i]) then begin if BlockScene then TraslateBlockToLUA; SaveNumber and NameScene; Save DECLARATIONS (Conditions/Triggers) scene; Save "---------------------------------"; Save ACTIONS scene; end; for i := 1 to QuickUPMAX do --passage QuickUp if exists(QuickUP[i]) then begin SaveNumber and NameQuickUP; SaveDevice??? SaveMain; end; for i := 1 to rowDocumentTXTMAX do --passage control on exist ID and SC begin if search ID (not exists in systém HC3) then begin changetxt "IDXXX" on IDXXXNotexists or IDXXXERROR end; if search Scene( not exists in systém HC3) then begin changetxt "SCXXX" on SCXXXNotexists or SCXXXERROR end; end; for i := 1 to IDMAX do --passage ADD params ID begin SaveNumber and NameID; Save name Params and value; end; end; "Example of documentation": --SC46 on device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> table = { isTrigger = true, operator = "match", property = "cron", type = "date", value = { "0", "*", "*", "*", "*", "*" } } -------------------------------------------------- local currentHod = os.date("*t").hour hub.call(467NOTEXIST, "turnOff") hub.call(468, "turnOff") hub.call(469, "turnOff") hub.call(470, "turnOff") if (currentHod == 0) then --hub.call(470, "turnOn") --zahrada vzadu elseif (currentHod == 1) then hub.call(467NOTEXIST, "turnOn") elseif (currentHod == 2) then hub.call(469, "turnOn") elseif (currentHod == 12) then hub.call(470, "turnOn") end --SC47 off device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> table = { isTrigger = true, operator = "match", property = "cron", type = "date", value = { "0", "*", "*", "*", "*", "*" } } -------------------------------------------------- --local currentHod = os.date("*t").hour hub.call(467NOTEXIST, "turnOff") hub.call(468, "turnOff") hub.call(469, "turnOff") hub.call(470, "turnOff") --SC48 on device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ...
- 2 replies
-
- 1
-
- hc3
- documentation
-
(and 2 more)
Tagged with:
-
Has anyone had issues with getting the alarm input to set? I have two set up identically, one sets the input, the other doesn’t. it almost like you have to seed the setting of the input in some way. My first one didn’t set the input initially, but some wherein the process of removing/adding, connecting/disconnecting the switch on the input it set. At first it would not reset, but then it did. Magic! any help . . . . .Please!
-
Does anyone have experience with connecting and configuring the external relays - the available documentation and the manuals are very poor and minimalistic. Thank you
- 6 replies
-
- 1
-
- documentation
- manual
-
(and 1 more)
Tagged with:
-
Hi, I must confess that I use only "value", "lastBreached", "turnOn" and "turnOff" properties and commands for z-wave devices in my scenes. I don't actually know what "log" and "logTemp" and the others are. They may be very useful, but I cannot find any documentation for them. Are there any? Has anyone tried to figure out what they are, and maybe made a list?? Fredrik
- 3 replies
-
- lua
- documentation
-
(and 1 more)
Tagged with:
-
Hi, Fibaro has implemented swagger for REST API documentation and testing, which is great. However, the documentation part is almost completely absent. I tried using the developer.fibaro.com portal but also there I can't really find proper documentation. Does anybody know where to find it? Thanks! KR, Kristof
- 2 replies
-
- rest
- documentation
-
(and 1 more)
Tagged with:
-
Hi, I just registered for a developer.fibaro.com account to see if the Lua library description was better there than what is posted on the public web (http://www.fibarouk.co.uk/support/lua/library/). It is not. As I understand it, these functions you still need to hunt around in the forum release notes to get a description of: setTimeout fibaro:setSceneRunConfig fibaro:getSceneRunConfig fibaro:setSceneEnabled fibaro:isSceneEnabled fibaro:getDevicesId And this function is more of a rumor. A mystical being that someone discovered and that may be present (have not checked yet, but just the fact that new functions are mentioned first in the forum tells you something about the state of things): clearTimeout So, for how long will this be the way developers are treated? Would there not be less problems reported on the forum if documentation was actually updated (not just copied in to a more pretty frame) AT LEAST when a non-beta version is released. Fredrik