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

cag014 · September 28, 2020

2 hours ago, Rover said:

Please login or register to see this spoiler.

What do you mean by immediately? The alarm arm/disarm actions takes over one second in HC3. I think this is the most slowest action in HC3.

The idea to create verify solution in AOQ came because of that.

If you remember, before using verify option you've struggled with delays to verify alarm state...

Edited September 28, 2020 by cag014

cag014 · September 28, 2020

4 hours ago, gggizmo said:

Again a little help

{0,"$24clock",{state="value=05:00",lineState={"{&heating:value=true}"},timeSlot="~07:00",trueAct={"`caldaia`","turnOn",""},falseAct={"`caldaia`","turnOff",""}}},

{0,"$24clock",{state="value=07:30",lineState={"{&vmc:value=true}"},timeSlot="~14:00",trueAct={"`vmcs`","turnOn",""},falseAct={"`vmcs`","turnOff",""}}},

these lines are supposed to turnon at time and turnoff at the end of timeslot...but they don't work. What am i doing worng?

Not exactly... let's see the first line:

At 05:00 it will turn On the caldaia, but on minute later it will be turned OFF. The state of value=05:00 becomes false and falseAct{} executed.

Try that:

{0,"$24clock",{lineState={"{&heating:value=true}"},timeSlot="05:00~,~07:00",trueAct={"`caldaia`","turnOn",""},falseAct={"`caldaia`","turnOff",""}}},

Now there is no false/true state. trueAct{} executed at 05:00 and falseAct{} at 07:00.

Same for the second line

Rover · September 28, 2020

30 minutes ago, cag014 said:

2 hours ago, Rover said:

Please login or register to see this spoiler.

I mean: does this line with verification sign (!), but without okAct or errAct, also retry if disarming was not succeeded?

Yes arm/disarm actions takes many seconds. Therefor I like a construction that the arming/disarming is repeated until success.

Question was whether this repeat happens with "!" also without okAct or errAct.

Quote

cag014 · September 28, 2020

2 minutes ago, Rover said:

I mean: does this line with verification sign (!), but without okAct or errAct, also retry if disarming was not succeeded?

Yes arm/disarm actions takes many seconds. Therefor I like a construction that the arming/disarming is repeated until success.

Question was whether this repeat happens with "!" also without okAct or errAct.

Yes, it works w/o okAct{} or errAct{}.

You can see that on debug window.

In case verification failed, an error message printed on debug window and error popups on HC3 UI and hcWebEye as well. (The error sent to TTS also, so If you have updated TTS in AOQ you should hear warning message)

I considered to send notification to user, but it can be very annoying.

Rover · September 28, 2020

Now testing again an alarm zone with 1 device (your new emulated sensor, indeed to be included in alarm zone).

Please login or register to see this spoiler.

Yes indeed, and with errAct I can send f.i. an email.

Edited September 28, 2020 by Rover

cag014 · September 28, 2020

39 minutes ago, Rover said:

Now testing again an alarm zone with 1 device (your new emulated sensor, indeed to be included in alarm zone).

Please login or register to see this spoiler.

The verification runs in back ground and I don't see a problem that meanwhile another action executed.

Looks like verification shows fail even when the conditions are OK.

So it continues to run in loop and crashes?

Please post your jM table

Edited September 28, 2020 by cag014

Rover · September 28, 2020

Hi @cag014,

Another curious thing:

Test your rptAction:

Please login or register to see this spoiler.

Rover · September 28, 2020

1 hour ago, cag014 said:

The verification runs in back ground and I don't see a problem that meanwhile another action executed.

Looks like verification shows fail even when the conditions are OK.

So it continues to run in loop and crashes?

Please post your jM table

The verification runs in back ground and I don't see a problem that meanwhile another action executed.

- If arming the house at a certain moment when arming has succeeded (in HC2 by a while loop) then buzzer and push message let me know that arming was successful. I do not want a message later on that the arming was not successful. The same for disarming: I do not want to open the entrance door before knowing that the disarming is successfully ready.

Looks like verification shows fail even when the conditions are OK.

- No, first verification shows fail, because the disarming was not ready yet, the repeated verification after 3 seconds shows that disarming is ready. (How many repeats can be done if disarming takes longer? I think disarming for all sensors take minimal 15 seconds.)

So it continues to run in loop and crashes?

- Yes indeed, when okAct is part of the active code.

Please login or register to see this attachment.

Edited September 28, 2020 by Rover

gggizmo · September 28, 2020

4 hours ago, cag014 said:

Not exactly... let's see the first line:

At 05:00 it will turn On the caldaia, but on minute later it will be turned OFF. The state of value=05:00 becomes false and falseAct{} executed.

Try that:

{0,"$24clock",{lineState={"{&heating:value=true}"},timeSlot="05:00~,~07:00",trueAct={"`caldaia`","turnOn",""},falseAct={"`caldaia`","turnOff",""}}},

Now there is no false/true state. trueAct{} executed at 05:00 and falseAct{} at 07:00.

Same for the second line

$24clock or $Blank is the same for those lines?

and i suppose that in this line false act never be esecuted

{0,"`tlaura`|`tjacopo`",{state="value<18",lineState={"{&heating:value=true}"},timeSlot="16:30~21:55,~22:00",trueAct={"`caldaia`","turnOn",""},falseAct={"`caldaia`","turnOff",""}}},

Rover · September 28, 2020

Please login or register to see this spoiler.

171 and 169 are Schilderijspot and SpotsTrapOverloop.

Bad file descriptor?

gggizmo · September 28, 2020

It's normal in last beta?

Please login or register to see this image.

/monthly_2020_09/image.png.4c4bcfdb0049fc536ba0b91387b0f120.png" />

Please login or register to see this attachment.

cag014 · September 28, 2020

What beta version?

gggizmo · September 28, 2020

8 minutes ago, cag014 said:

What beta version?

5.041

another question:

{0,"$24clock",{lineState={"{&vmc:value=true}"},timeSlot="07:30~",timeSlot="~14:00",trueAct={"`vmcs`","turnOn",""},falseAct={"`vmcs`","turnOff",""}}},

{0,"$blank",{timeSlot="?$sunriseHour+1800?~,~?$sunsetHour-1800?",trueAct={"&luci_attive","setGlobal","false"},falseAct={"&luci_attive","setGlobal","true"}}},

about 15 mins ago i installed the new beta.

and devices vmcs was turned on after reboot

and global var set to false.

Why? what i missed? Do i need to set something in oninit?

cag014 · September 28, 2020

10 minutes ago, gggizmo said:

5.041

another question:

{0,"$24clock",{lineState={"{&vmc:value=true}"},timeSlot="07:30~",timeSlot="~14:00",trueAct={"`vmcs`","turnOn",""},falseAct={"`vmcs`","turnOff",""}}},

{0,"$blank",{timeSlot="?$sunriseHour+1800?~,~?$sunsetHour-1800?",trueAct={"&luci_attive","setGlobal","false"},falseAct={"&luci_attive","setGlobal","true"}}},

about 15 mins ago i installed the new beta.

and devices vmcs was turned on after reboot

and global var set to false.

Why? what i missed? Do i need to set something in oninit?

Yes, on Startup AOQ initialize every line.

Please insert initOnStartup=false

{0,"$24clock",{lineState={"{&vmc:value=true}"},initOnStartup=false, timeSlot="07:30~",timeSlot="~14:00",trueAct={"`vmcs`","turnOn",""},falseAct={"`vmcs`","turnOff",""}}},

gggizmo · September 28, 2020

{0,"$24clock",{initOnStartup=false,timeSlot="?$sunriseHour+1800?~,~?$sunsetHour-1800?",trueAct={"&luci_attive","setGlobal","false"},falseAct={"&luci_attive","setGlobal","true"}}},

why global var is set on false on every reboot or reinit of aoq?

cag014 · September 28, 2020

2 minutes ago, gggizmo said:

{0,"$24clock",{initOnStartup=false,timeSlot="?$sunriseHour+1800?~,~?$sunsetHour-1800?",trueAct={"&luci_attive","setGlobal","false"},falseAct={"&luci_attive","setGlobal","true"}}},

why global var is set on false on every reboot or reinit of aoq?

even if you reboot after sunsetHour?

gggizmo · September 28, 2020

30 minutes ago, cag014 said:

even if you reboot after sunsetHour?

yes.

Do you have same weird interface in last beta?

gggizmo · September 28, 2020

2 minutes ago, gggizmo said:

yes.

Do you have same weird interface in last beta?

Looks like scenes.sceneDashboard.sceneTile.log.never

is shown ultil scene is triggered

cag014 · September 28, 2020

22 minutes ago, gggizmo said:

yes.

Do you have same weird interface in last beta?

No... I'm on 5.041.50 (beta)

22 minutes ago, gggizmo said:

yes.

Do you have same weird interface in last beta?

Could you post your debug window of AOQ startup... I mean from "Gathering system... " and before the table shown

gggizmo · September 28, 2020

22 minutes ago, cag014 said:

No... I'm on 5.041.50 (beta)

Could you post your debug window of AOQ startup... I mean from "Gathering system... " and before the table shown

it's same version.5.041.50...notified to me today at 6pm.

[28.09.2020] [22:10:04] [DEBUG] [QUICKAPP1257]: Irrigazione Inattiva[28.09.2020] [22:10:04] [DEBUG] [QUICKAPP1256]: Vmc Attiva[28.09.2020] [22:10:04] [DEBUG] [QUICKAPP1259]: riscaldamento inattivo[28.09.2020] [22:10:04] [DEBUG] [QUICKAPP1258]: Condizionatore Inattivo[28.09.2020] [22:10:06] [DEBUG] [AOQ1354]: ^{^2.96}Gathering information...5264[28.09.2020] [22:10:07] [DEBUG] [AOQ1354]: hcl: Hcl_garden HCL-027231...[28.09.2020] [22:10:07] [DEBUG] [AOQ1354]: local: HC3-00003585 HC3-00004002...[28.09.2020] [22:10:09] [DEBUG] [AOQ1354]: ^{^2.96}Initializing jS2n{}, jP2n{}, global and userKeyWord{} tables...[28.09.2020] [22:10:10] [DEBUG] [AOQ1354]: Global not defined. Local variables ("onState" "my_Var") won't be saved for next run...[28.09.2020] [22:10:10] [DEBUG] [AOQ1354]: Global not defined. Reminders won't be saved for next run...[28.09.2020] [22:10:10] [DEBUG] [AOQ1354]: ^{^2.96}Parsing jM[31] hash table data... <6 sec.[28.09.2020] [22:10:13] [DEBUG] [AOQ1354]: ^{^2.96}Initializing devices state...[28.09.2020] [22:10:17] [TRACE] [AOQ1354]: ^{^2.96}jM{27} _Itbagno:444:porta bagno[true] => turnOff{stufabagno)[28.09.2020] [22:10:19] [DEBUG] [AOQ1354]: ^{^2.96}Data validation in progress...[28.09.2020] [22:10:19] [DEBUG] [AOQ1354]: ^{^2.96}Arranging data table... <10 sec.[28.09.2020] [22:10:25] [DEBUG] [AOQ1354]: 28-Sep 22:10 AOQ^{^2.96} All-in-One ^{? O O ? O ? ? ?} sunHours 07:12~19:03

Please login or register to see this code.

Type	Item Description	Value	Criteria	in State	TimeSpan	Time Slot	trueAct	falseAct	trigAct	initAct	Active Rules	jM{#}	jM { hash table line }
Z.Dev	Bedroom:931:remote camera	TBR	centralSceneSupport=dummy	00:00:08	Activity				turnOff^setValue			>5	{0, "`rcamera`"...}
	Giardino:59'hcl:linea destra	false	value=true	00:00:08	Activity		turnOn	turnOff		turnOff	lineState	>19	{0, "`lineadx`\|`lineasxt`\|`lineasxb`\|`lineacx`"...}
	Giardino:60'hcl:linea centrale	false	value=true	00:00:08	Activity		turnOn	turnOff		turnOff	lineState	>19	{0, "`lineadx`\|`lineasxt`\|`lineasxb`\|`lineacx`"...}
	Giardino:64'hcl:linea sx turbina	false	value=true	00:00:09	Activity		turnOn	turnOff		turnOff	lineState	>19	{0, "`lineadx`\|`lineasxt`\|`lineasxb`\|`lineacx`"...}
	Giardino:65'hcl:linea sx battente	false	value=true	00:00:09	Activity		turnOn	turnOff		turnOff	lineState	>19	{0, "`lineadx`\|`lineasxt`\|`lineasxb`\|`lineacx`"...}
	Jacopo:1302:Temp Jacopo	21.2	value<18	00:00:09	Activity	16:30~21:55, ~22:00	turnOn	turnOff			lineState	>23	{0, "`tlaura`\|`tjacopo`"...}
	Sala Pranzo:358:Interruttore cucina	TBR	centralSceneSupport=1.Pressed	00:00:10	Activity		turnOff^turnOn					>10	{0, "`icucina`"...}
		TBR	centralSceneSupport=3.Pressed	00:00:10	Activity		turnOff^turnOn					>11	{0, "`icucina`"...}
		TBR	centralSceneSupport=2.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>12	{0, "`icucina`"...}
		TBR	centralSceneSupport=4.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>13	{0, "`icucina`"...}
	Sala Pranzo:862:interruttore sala	TBR	centralSceneSupport=3.Pressed	00:00:10	Activity		turnOff^turnOn					>14	{0, "`isala`"...}
		TBR	centralSceneSupport=4.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>15	{0, "`isala`"...}
		TBR	centralSceneSupport=2.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>16	{0, "`isala`"...}
		TBR	centralSceneSupport=1.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>17	{0, "`isala`"...}
	bagnetto:1307:Remote Bagnetto	TBR	centralSceneSupport=1.Pressed	00:00:11	Activity		turnOff^turnOn					>1	{0, "`ibagnetto`"...}
		TBR	centralSceneSupport=3.Pressed	00:00:10	Activity		turnOff^turnOn					>2	{0, "`ibagnetto`"...}
		TBR	centralSceneSupport=2.Pressed	00:00:10	Activity		turnOff^turnOn					>3	{0, "`ibagnetto`"...}
		TBR	centralSceneSupport=4.Pressed	00:00:10	Activity		turnOff^turnOn					>4	{0, "`ibagnetto`"...}
	bagno:444:porta bagno	true	value=true	00:00:09	Activity		turnOff	turnOn		turnOff		>27	{0, "`pbagno`"...}
	lab:1063:Temp lab	20.0	value>25	00:00:09	Activity	08:00~20:00	setThermostatMode setThermostatFanMode setCoolingThermostatSetpoint				lineState	>20	{0, "`tlab`"...}
	lab:1063:Temp lab	20.0	value<16	00:00:09	Activity	08:00~20:00	setThermostatMode setThermostatFanMode setHeatingThermostatSetpoint				lineState	>21	{0, "`tlab`"...}
	lab:1134:Rack Temp	27.7	value>38	00:00:09	Activity		turnOn turnOff					>28	{0, "`track`"...}
	laura:1305:Temp Laura	21.4	value<18	00:00:09	Activity	16:30~21:55, ~22:00	turnOn	turnOff			lineState	>23	{0, "`tlaura`\|`tjacopo`"...}
	soggiorno:946:r soggiorno	TBR	centralSceneSupport=1.Pressed	00:00:10	Activity		turnOff^setValue					>6	{0, "`isoggiorno`"...}
		TBR	centralSceneSupport=2.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>7	{0, "`isoggiorno`"...}
		TBR	centralSceneSupport=3.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>8	{0, "`isoggiorno`"...}
		TBR	centralSceneSupport=4.Pressed	00:00:10	Activity		changeBrightness turnOff^turnOn					>9	{0, "`isoggiorno`"...}
K.Word	$24clock	22:10	value=04:00	00:00:10	Activity		turnOn turnOff turnOn turnOff turnOn turnOff turnOn turnOff				lineState	>18	{0, "$24clock"...}
	$24clock	22:10	value=20:05	00:00:09	Activity		setThermostatMode					>22	{0, "$24clock"...}
	$24clock	22:10	(value)	00:00:08	Activity	~07:00	turnOn	turnOff		turnOn	lineState	>24	{0, "$24clock"...}
	$24clock	22:10	(value)	00:00:08	Activity	~14:00	turnOn	turnOff			initOnStartup lineState	>25	{0, "$24clock"...}
	$24clock	22:10	(value)	00:00:08	Activity	07:42~, ~18:33	setGlobal	setGlobal			initOnStartup	>26	{0, "$24clock"...}
	$HC3onLine	false	value=true	00:00:09	Activity		tts	tts				>30	{0, "$HC3onLine"...}
	$RAM	41	value>85	00:00:10	Activity		sendNote setStateValue	setStateValue sendNote		setStateValue		>29	{0, "$RAM"...}
	$internet	online	value=online	00:00:09	Activity				tts			>31	{0, "$internet"...}
_It444>27^{turnOff{stufabagno)}

QuickApp/Global/Local variables

Type	Name	Value	Modified
Global	luci_attive	true	0d, 00:01:18
Global	sprinkler	false	0d, 00:01:18
Global	cooling	false	0d, 00:01:18
Global	heating	false	0d, 00:01:18
Global	vmc	true	0d, 00:01:18

now after reboot the global var has correct value. But on previous three reboots it always was false...

Welcome to Smart Home Forum by FIBARO

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

Recommended Posts

cag014 731

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Rover

cag014

cag014

Posted Images

cag014 731

Rover 47

cag014 731

Rover 47

cag014 731

Rover 47

Rover 47

gggizmo 6

Rover 47

gggizmo 6

cag014 731

gggizmo 6

cag014 731

gggizmo 6

cag014 731

gggizmo 6

gggizmo 6

cag014 731

gggizmo 6

Join the conversation

Rover

cag014

cag014

FORUM

KNOWLEDGE

DOWNLOADS

SUPPORT