Detailed functional documentation

[[email protected] 0]

I have been having great difficulty getting a double relay working with a TV hoist (0V contacts) although the controlled device is probably not relevant. I realise that there is no detailed documentation and what I observe is complex and changeable. For example I required both relays to be on for say 30 seconds then switch off (one for up one for down). I have discovered that this forces "Momentary" press and "toggle" to be set. OK seems reasonable. Next I find that relay 1 does switch off after a time lapse but the Homecentre 2 device display shows the switch as ON. Relay 2 works differently in that the HC2 device display goes off after relay time period - very strange.

Then I notice that if I send the relay 1 a turnoff command in LUA it doesn't turn the relay off it seems to turn the toggle switch off which because of the momentary setting, forces another relay on for 30 seconds cycle. So now I wonder if the fibaro:calls are working at different levels. Is the device value the relay position but the actions "turnOn" and "turnoff" apply not to the relay but to the button.

What I need is some documentation about the device states and a full exposition of the actions. I just can't find the right level of documentation. The supplied data sheet is very densely printed but there is just not enough explanation of the actual functioning of say Parameter 13 or perhaps the English has lost something in the translation. The developers online documentation is great as far as it goes but I am looking for better documentation of the device software object values and actions in LUA. I am aware of the help provided in pointing at a device while coding in LUA on the HC2 but it doesn't tell me in detail what the expected values are.

If someone could just point me, it would be great.

As an aside have just bought an echo and installed the fibaro support and it is really good. I can say "Computer switch on the television" and the TV hoist lowers the TV from the ceiling. Unfortunately I haven't got the reverse action working yet! (Echo support would benefit from some definitive documentation as to what statements and functions are available. Hopefully time will provide.)

[RH_Dreambox 189]

Hi, I use a double relay to open and close a damper that has three connections.
Cable 1 + 2 closes the damper.
Cable 1 + (2 and 3) opens the damper.
Is that your TV lift work?
If so, this solution works.

Parameter 13 = 0

Parameter 14 = 1

 

And here is more information:

Please login or register to see this link.

 

Please login or register to see this code.

 

[Jamie mccrostie 82]

@[email protected] have you set the 30 sec "delay off" as a auto off parameter in the relay settings or are you using LUA to do that delay for you?

If relay setting, are you better to use your local push buttons to trigger a "up" or "down" scene like the one   @RH_Dreambox

suggests.

 

Edited May 13, 2017 by Jamie mccrostie

[[email protected] 0]

Jamie, Thank you for being positive and trying to help. The thirty seconds Off is set as an auto parameter in the device settings. I basically have a working solution now. My aim was to try and get to a natural language solution so that I can literally say aloud "Computer turn on the Television" to cause the hoist to deploy and "Computer turn off the Television" to cause it to retract. This means I think that I have to have a device called television in HC2. It would be easy to use a scene but then I would have to say "Activate Television" as the "turn on" method is not accepted for Scenes. Saying Activate is not natural language for this particular activity. Basically my solution is a scene triggered by change in status of the toggle on the device television. The scene then tests for the switch being "on" or "off". My gripe was the unclear documentation around Parameter 13 and the general lack of accurate documentation about actions and object values. I have seen great strides in improving things of late. (I used to work in product development for communications controllers so I know the enormous effort it takes to get complete documentation out there.) Twenty years ago you could get definitive documentation for all the standard objects in visual Basic and I may be an old (72) fogey but I miss the same for LUA.

Geoff

--[[
%% properties
24 value
%% weather
%% events
%% globals
--]]

local startSource = fibaro:getSourceTrigger();
fibaro:debug(fibaro:getValue(24,"value")..fibaro:getGlobalValue("Hoist"))
--Test if the television (on) switch is set on and the
--TV is in the Up position
if (tonumber(fibaro:getValue(24, "value")) > 0)and
   (fibaro:getGlobalValue("Hoist")=="Up")
    then fibaro:setGlobal("Hoist","Moving") --tell everyone the hoist is moving.
   --Wait for 30 seconds
     fibaro:sleep(30000)
     --Show hoist now down
         fibaro:setGlobal("Hoist","Down")
     --Exit
  
 else --Switch has been set off or the Hoist is moving
     while fibaro:getGlobalValue("Hoist")=="Moving"
             do --Wait one second
              fibaro:sleep(1000)
        fibaro:debug("Scene clash hoist already moving")
      end
        --So now the hoist should have stopped moving.
     -- If its up we'll leave it.
     if fibaro:getGlobalValue("Hoist")=="Down"
          then --we'll put it up
               --Let things settle
        fibaro:sleep(1000)
          fibaro:call(25, "turnOn");
              fibaro:setGlobal("Hoist","Moving")
        fibaro:sleep(35000)
        fibaro:setGlobal("Hoist","Up")
      end
end

[Jamie mccrostie 82]

@[email protected] yes "work it out amongst yourselfs" seems to be the norm around here.