All-in-One Scene: How to do it Better

[Rover 47]

7 hours ago, Rover said:

No, both zones &Achterpoort en $Deuren (not the zone $Achter) have one different Fibaro D/W sensor. Breaching $Deuren works, but breaching $Achterpoort does not work. These two devices are not defined in zone $Achter.

My bad ?, in the testing of v13.7 I have forgotten to set back the &Achterpoort zone for triggering on state="value=breached". Sorry for bothering you with this, cag.

[Rover 47]

Hi cag,

When I  disconnect the power of two HC3 devices only defined in my AOQ1 and not in AOQ2, both AOQ1 and AOQ2 crashed with messages: 

[29.09.2022] [17:19:19] [ERROR] [QUICKAPP386]: main.lua:2103: Wrong parameter: 'simplePush'. Available parameters: email, push

[29.09.2022] [17:20:49] [ERROR] [QUICKAPP387]: main.lua:2103: Wrong parameter: 'simplePush'. Available parameters: email, push

Edited September 30, 2022 by Rover

[cag014 731]

18 hours ago, Rover said:

Hi cag,

When I  disconnect the power of two HC3 devices only defined in my AOQ1 and not in AOQ2, both AOQ1 and AOQ2 crashed with messages: 

[29.09.2022] [17:19:19] [ERROR] [QUICKAPP386]: main.lua:2103: Wrong parameter: 'simplePush'. Available parameters: email, push

[29.09.2022] [17:20:49] [ERROR] [QUICKAPP387]: main.lua:2103: Wrong parameter: 'simplePush'. Available parameters: email, push

What devices?

What SW version you run on HC3?

Edited September 30, 2022 by cag014

[Rover 47]

5 hours ago, cag014 said:

What devices?

What SW version you run on HC3?

I had disconnected a Fibaro Smart Implant and a Fibaro RGBW2 on HC3 v.50.070.42.

Edited September 30, 2022 by Rover

[cag014 731]

My HC3 currently at Fibaro Service and should arrive back to me on Sunday by end of day.  Is this version 50.070.42 is the latest ? 

 Using Yubii or HC3L I don't see any problem with the latest version 5.120.10

 

[cag014 731]

On 9/30/2022 at 6:27 PM, Rover said:

I had disconnected a Fibaro Smart Implant and a Fibaro RGBW2 on HC3 v.50.070.42.

Now I understand, when device disconnected the AOQ tries to report about dead device, since last upgrade the push notification doesn't support mobile devices, only user ID (email).

Please update HC3 version or change mobile ID to user ID in global parameters 

pushNote    = {true,"2"}  -- if true, auto alerts interactive/push notification will send

 

 

See 

 

 

[Rover 47]

22 minutes ago, cag014 said:

Now I understand, when device disconnected the AOQ tries to report about dead device, since last upgrade the push notification doesn't support mobile devices, only user ID (email).

Please update HC3 version or change mobile ID to user ID in global parameters 

pushNote    = {true,"2"}  -- if true, auto alerts interactive/push notification will send

 

 

See 

 

 

I will update HC3 version to v5.120.10. But I am missing an overall inside in the latest status of pushing, interactive or not. And what is the impact for AOQ and AOS?

Edited October 1, 2022 by Rover

[cag014 731]

14 minutes ago, Rover said:

I will update HC3 version to v5.120.10. But I am missing an overall inside in the latest status of pushing, interactive or not. And what is the impact for AOQ and AOS?

Currently I don't see any impact on AOQ or AOS and all push notifications are work properly (including interactive push).

But I am trying to fix the problem and send notification considering the version number. I believe in one hour I'll post a new AOQ for you.

[cag014 731]

@Rover

Please try attached version. Should support push notifications on all HC3 versions

 

 

 

Please login or register to see this attachment.

[Sjekke 87]

41 minutes ago, cag014 said:

@Rover

Please try attached version. Should support push notifications on all HC3 versions

 

 

 

Please login or register to see this attachment.

Hi @cag014, should everyone upgrade to the latest version? In the marketplace it’s an older version… 

[cag014 731]

36 minutes ago, Sjekke said:

Hi @cag014, should everyone upgrade to the latest version? In the marketplace it’s an older version… 

I post here the version for users to test to verify there are no some bugs and then upgrade the download center.

Meanwhile, yes you can download this version and try it.

I believe on Monday I'll release that (if no issues reported)

[Sjekke 87]

9 minutes ago, cag014 said:

I post here the version for users to test to verify there are no some bugs and then upgrade the download center.

Meanwhile, yes you can download this version and try it.

I believe on Monday I'll release that (if no issues reported)

 

Thx @cag014, I'm currently implementing AIO ?.

 

Q: Any idea how to use TTS with SONOS speakers? Any directions welcome.

[cag014 731]

3 hours ago, Sjekke said:

 

Thx @cag014, I'm currently implementing AIO ?.

 

Q: Any idea how to use TTS with SONOS speakers? Any directions welcome.

Unfortunately, I do not use SONOS for TTS. 

I'm using Android tablet and Android mobile TTS solution. 

 

 

May be that could help for SONOS

 

[Sjekke 87]

thx @cag014

 

Sorry for all my questions, but I'm new to this, learning everyday and the weather is bad here so I have some time ?

 

Q: I've implemented this in AIO.

 

{0,"`allLivingMotion`",{state="value=true",trueAct={"`allLivingLights`","turnOn"},falseAct={"`allLivingLights`","turnOff","400"}}}

 

• Is there a possibility to restart the 400sec every time when the MotionSensors are breached. 
• Can we add LUX condition to this scene

 

Before I was using a LUA script from @SmartHomeEddy which worked perfectly, before that I used Advanced Lighting Control (ALC) (UHAS) on my HC2 from @Sankotronic

 

Declarations

{

  conditions = { {

      id = 78,

      isTrigger = true,

      operator = "==",

      property = "value",

      type = "device",

      value = true

    }, {

      id = 263,

      isTrigger = true,

      operator = "==",

      property = "value",

      type = "device",

      value = true

    } },

  operator = "any"

}

 

Actions

-- This scene turns on one or more lights: 

--    when Lux level is below a certain level (see DECLARATIONS) and 

--    shows the Lux level of one ore more Lux sensors and 

--    turns off the lights after a certain time (maxTime), 

--    unless there is motion from one or more Motion sensors

 

-- Please enter the right ID's (if more than one, seperate by ",") and the prefered maxTime for the lights to stay on 

 

local light = {26, 62} -- ID's of the lights to turn on

local motion = {78, 263} -- ID's of the Motion sensors to check if they are breached

local lux = {80, 265} -- ID's of the Lux sensors to (only) show the lux level

local maxTime = 1*500 -- Maximum time the sensor should be safe before turning off (n*60 where n is minutes)

local sleepTime = 5 -- Time in seconds between each check of the Motion sensor (default = 5)

local debug_TAG = "Woonkamer licht" -- Tag for the debug messages

 

-- Below here no changes are necessary

 

for i in pairs(light) do -- Turn on the lights

  fibaro.debug(debug_TAG,"Turning on (ID " ..light[i] ..") " ..fibaro.getName(light[i]) .." for " ..maxTime .." seconds")

  fibaro.call(light[i],"turnOn")

end

 

for i in pairs(lux) do -- Show the lux level of the Lux sensors

  fibaro.debug(debug_TAG,"Current Lux level " ..lux[i] .." " ..fibaro.getName(lux[i]) ..": " ..fibaro.getValue(lux[i],"value"))

end

 

local safeTime = 0

while safeTime < maxTime do -- Loop until maxTime is reached

  fibaro.sleep(sleepTime*1000)                 

  safeTime=safeTime+sleepTime 

  fibaro.debug(debug_TAG,"Counting up safeTime " ..safeTime .." to maxTime " ..maxTime)

  for i in pairs(motion) do 

    if fibaro.getValue(motion[i],"value") then -- Check if Motion sensors are breached

       fibaro.debug(debug_TAG,"Reset by Motion sensor " ..motion[i] .." " ..fibaro.getName(motion[i]))

       safeTime = 0 -- Reset safeTime to zero

    end

  end

end 

  

for i in pairs(light) do -- Counted down to maxTime, turn off the lights

  fibaro.debug(debug_TAG, "Turning off " ..light[i] .." " ..fibaro.getName(light[i]))

  fibaro.call(light[i],"turnOff") 

end

Edited October 2, 2022 by Sjekke

[Sankotronic 2,370]

19 minutes ago, Sjekke said:

Before I was using a LUA script from @SmartHomeEddy which worked perfectly, before that I used Advanced Lighting Control (ALC) (UHAS) on my HC2 from @Sankotronic

 

Hi @Sjekke ,

 

Hmmm... latest and final version of UHAS with ALC is just about to be published. Previous beta versions was using Very Smart Lights (VSL) so I guess you meant you used VSL? Raising this comment just to be clear since access to UHAS with ALC is at this moment restricted just to few people that helping me mostly with writing manual since it is equally big job as writing all those 80+ VD's and 40+ scenes.

[Sjekke 87]

1 hour ago, Sankotronic said:

 

Hi @Sjekke ,

 

Hmmm... latest and final version of UHAS with ALC is just about to be published. Previous beta versions was using Very Smart Lights (VSL) so I guess you meant you used VSL? Raising this comment just to be clear since access to UHAS with ALC is at this moment restricted just to few people that helping me mostly with writing manual since it is equally big job as writing all those 80+ VD's and 40+ scenes.

Hi @Sankotronic, you are right ofcourse. I mean VSL.  I hope you port UHAS to HC3 very soon ?

[cag014 731]

2 hours ago, Sjekke said:

thx @cag014

 

Sorry for all my questions, but I'm new to this, learning everyday and the weather is bad here so I have some time ?

 

Q: I've implemented this in AIO.

 

{0,"`allLivingMotion`",{state="value=true",trueAct={"`allLivingLights`","turnOn"},falseAct={"`allLivingLights`","turnOff","400"}}}

 

• Is there a possibility to restart the 400sec every time when the MotionSensors are breached. 
• Can we add LUX condition to this scene

 

It restarted by default every time when the sensor is breached again, no issue there.

Please note that 400 seconds counting starts when the sensor goes back to safe mode and not from the moment when it's breached.

Yes, you can add any condition you need.

For example, assuming you have device called allLightsLux then

{0,"`allLivingMotion`",{state="value=true",trueAct={"`allLivingLights`","turnOn", "if {`allLightsLux`:value <80}"},falseAct={"`allLivingLights`","turnOff","400"}}}

[Sjekke 87]

Hi @cag014, I already moved some scenes to AIO and they are working perfectly. But since I like as minimum scenes as possible, do you think we can nest both scenes?

 

{0,"`allLivingMotion`",{state="value=true",trueAct={"`allLivingLampLights`","turnOn"},falseAct={"`allLivingLampLights`","turnOff","600"}}},

{0,"`allLivingMotion`",{state="value=true",trueAct={"`allLivingHueLights`","turnOn","if{$24clock:value=$sunsetHour~04:00}"},falseAct={"`allLivingHueLights`","turnOff","600"}}},

 

I explain : I have 4 lights in my living room > 2 are controlled via a Fibaro Wall Plug and 2 HUE lamps.

 

jS2n={

--== Living Room

livingRoomTVBox=478,livingRoomBlind=188,livingRoomMotionFront=263,livingRoomMotionBack=78,livingTVLight=62,livingDressorLight=26,livingRoomLeftHue=567,livingRoomRightHue=566,

 

--== Office

officeBlindBig=191,officeBlindSmall=195,

 

--== Combinations

allBlinds="`livingRoomBlind`|`officeBlindBig`|`officeBlindSmall`",

allLivingMotion="`livingRoomMotionFront`|`livingRoomMotionBack`",allLivingLampLights="`livingTVLight`|`livingDressorLight`",allLivingHueLights="`livingRoomLeftHue`|`livingRoomRightHue`",

}

 

What would be my ideal scenario.

• 1 light can always turnOn when motion is detected
• 1 light may always switch on when motion is detected, but only when LUX is lower than 50Lux
• The 2 HUE lamps can only be switched on when motion is detected, but only between sunset and 04:00 at night
• All lights should turnOff after 600sec unless there is motion detection.

 

Thanks for your help, this helps me learning!!

Edited October 2, 2022 by Sjekke

[Rover 47]

On 10/1/2022 at 8:28 PM, cag014 said:

@Rover

Please try attached version. Should support push notifications on all HC3 versions

 

 

 

Please login or register to see this attachment.

Hi cag,

I have tried v13.8 with HC3 still on v50.070.42.

{"&Test",{state="Start",initOnStartup=false,trueAct={"Push","sendPush,2","iPhone 6"},}}, delivered no push message at the iPhone when &Test become Start.

&Test:Global[Start] => sendPush,2(Rover) 'Push','iPhone 6')

But using a Block Scene producing a push message when &Test become Start works.

Edited October 3, 2022 by Rover

[cag014 731]

16 hours ago, Rover said:

Hi cag,

I have tried v13.8 with HC3 still on v50.070.42.

{"&Test",{state="Start",initOnStartup=false,trueAct={"Push","sendPush,2","iPhone 6"},}}, delivered no push message at the iPhone when &Test become Start.

&Test:Global[Start] => sendPush,2(Rover) 'Push','iPhone 6')

But using a Block Scene producing a push message when &Test become Start works.

Strange, works perfectly on my system...

Could you please post the block scene?

Edited October 3, 2022 by cag014