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

[Rover 47]

This night it has worked (v9.6).

[SmartLifeSystems 20]

@cag014 I changed this line.

 

else fibaro.alert("push",uId,ctlChar(subject..""..body,"\n","\\n")) end end 

 

I deleted the \n characters between the subject and the ..body.

In this way in the push notification the \n characters is not there.

 

Working fine.

[cag014 731]

1 minute ago, SmartLifeSystems said:

@cag014 I changed this line.

 

else fibaro.alert("push",uId,ctlChar(subject..""..body,"\n","\\n")) end end 

 

I deleted the \n characters between the subject and the ..body.

In this way in the push notification the \n characters is not there.

 

Working fine.

What was the problem???

[SmartLifeSystems 20]

 

When the AOQ sent the notifications, between the subject and the message, puted \n characters.

 

 

Please login or register to see this attachment.

[cag014 731]

@Rover

Didn't find anything wrong, but might be AOQ with many lines is too busy and could miss the time.

In attached version have added extra trigger (every 15 seconds) to run through lines.

Let me know if it helps

@SmartLifeSystems

The \n is still exists in this version and the reason is that it works fine in old fibaro application. Will try to find out proper solution in next release.

 

Please login or register to see this attachment.

[SmartLifeSystems 20]

5 minutes ago, cag014 said:

@Rover

Didn't find anything wrong, but might be AOQ with many lines is too busy and could miss the time.

In attached version have added extra trigger (every 15 seconds) to run through lines.

Let me know if it helps

@SmartLifeSystems

The \n is still exists in this version and the reason is that it works fine in old fibaro application. Will try to find out proper solution in next release.

 

Please login or register to see this attachment.

 

If I deleted the \n from the next line, working fine.

 

else fibaro.alert("push",uId,ctlChar(subject..""..body,"\n","\\n")) end end 

 

This is the original line:

 

else fibaro.alert("push",uId,ctlChar(subject.."\n"..body,"\n","\\n")) end end 

 

The AOQ has need this \n?

Edited January 8, 2021 by SmartLifeSystems

[cag014 731]

5 minutes ago, SmartLifeSystems said:

 

If I deleted the \n from the next line, working fine.

 

else fibaro.alert("push",uId,ctlChar(subject..""..body,"\n","\\n")) end end 

 

This is the original line:

 

else fibaro.alert("push",uId,ctlChar(subject.."\n"..body,"\n","\\n")) end end 

 

The AOQ has need this \n?

Honestly it's just to distinguish between subject to body of the message.

Will try to find out different approach... maybe to include subject in parenthesis like

(Subject): body message

Do you have any suggestions?

Edited January 8, 2021 by cag014

[SmartLifeSystems 20]

5 minutes ago, cag014 said:

Honestly it's just to distinguish between subject to body of the message.

Will try to find out different approach... maybe to include subject in parenthesis like

(Subject): body message

Do you have any suggestions?

 

I think, dont't need the \n between the subject and the body in this line. Only the "" characters. I testing since some days, and working correctly.

Edited January 8, 2021 by SmartLifeSystems

[Rover 47]

12 hours ago, cag014 said:

@Rover

Didn't find anything wrong, but might be AOQ with many lines is too busy and could miss the time.

In attached version have added extra trigger (every 15 seconds) to run through lines.

Let me know if it helps

@SmartLifeSystems

The \n is still exists in this version and the reason is that it works fine in old fibaro application. Will try to find out proper solution in next release.

 

Please login or register to see this attachment.

All fine this night with v9.7 ?

[Rover 47]

12 hours ago, cag014 said:

Honestly it's just to distinguish between subject to body of the message.

Will try to find out different approach... maybe to include subject in parenthesis like

(Subject): body message

Do you have any suggestions?

Talking about subject and body:

Why is the subject in an email not showed up as subject, but get a title "Bericht van Fibaro" (Message from Fibaro)?

Please login or register to see this spoiler.

 

[cag014 731]

15 hours ago, Rover said:

Talking about subject and body:

Why is the subject in an email not showed up as subject, but get a title "Bericht van Fibaro" (Message from Fibaro)?

Please login or register to see this spoiler.

Yes, this problem exists since the beginning of HC3. Have reported about that. no answer....

[cag014 731]

On 1/8/2021 at 10:02 PM, SmartLifeSystems said:

 

I think, dont't need the \n between the subject and the body in this line. Only the "" characters. I testing since some days, and working correctly.

That's interesting on my phone (Samsung - android) I don't see "\n" character, but actually new line works!???

Is it iPhone?

 

[SmartLifeSystems 20]

8 hours ago, cag014 said:

That's interesting on my phone (Samsung - android) I don't see "\n" character, but actually new line works!???

Is it iPhone?

 

 

Yes, it is iPhone, and working without the \n.

 

Please login or register to see this attachment.

[Rover 47]

All fine this night with v9.7 ?

[SmartLifeSystems 20]

Hi @cag014,

 

Have you any idea, how can I set example the os.Date-20 min?

 

And I have another interesting question. I integrated the Football Euro20 calendar in the HC3. This events save a global variable.

 

Examples for the variable:

Hungary - Portugal [Euro2020]

France - Germany [Euro2020]

Croatia - Scotland [Euro2020]

Hungary - France [Euro2020]

 

Can I use for trigger from this variable example the Hungary word?

If the Hungarian team will play, turn on the TV. But from the calendar, every match will be in the variable before the match's time.

 

Do you understand?

Edited January 10, 2021 by SmartLifeSystems

[cag014 731]

Actually, yes there is an option to compare part of value. use "=="

{0,"&GV",{state="value==Hungary", trueAct={}......}},

it means when word Hungary will be found in &GV the trueAct{} executed.

 

Edited January 10, 2021 by cag014

[SmartLifeSystems 20]

9 hours ago, cag014 said:

Actually, yes there is an option to compare part of value. use "=="

{0,"&GV",{state="value==Hungary", trueAct={}......}},

it means when word Hungary will be found in &GV the trueAct{} executed.

 

 

Thanks, I will try.

 

And you have idea for the os.Date-20 minutes?

[SmartLifeSystems 20]

58 minutes ago, SmartLifeSystems said:

 

Thanks, I will try.

 

And you have idea for the os.Date-20 minutes?

 

I tried the command, but I think the os.Date don't working.

I tested a simple line, but the AOQ don't do anything.

 

Here is the line:

 

{0, "$osDate",{state="value=&CalendarDate",trueAct={{"`cinemaSystem`","turnOn",""},{"`sonyTV`","pressButton,26","6"},{"`sonyTV`","pressButton,11","10"},{"Foci EB","sendPush,3370","Hamarosan kezdődik a &Calendar , bekapcsoltam a TV-t!"}}}},

Edited January 11, 2021 by SmartLifeSystems

[SmartLifeSystems 20]

1 hour ago, SmartLifeSystems said:

 

I tried the command, but I think the os.Date don't working.

I tested a simple line, but the AOQ don't do anything.

 

Here is the line:

 

{0, "$osDate",{state="value=&CalendarDate",trueAct={{"`cinemaSystem`","turnOn",""},{"`sonyTV`","pressButton,26","6"},{"`sonyTV`","pressButton,11","10"},{"Foci EB","sendPush,3370","Hamarosan kezdődik a &Calendar , bekapcsoltam a TV-t!"}}}},

 

So I tried with an another mode.

I think, the "==" don't working too. Maybe I doing something wrong?

 

{0, "&Calendar",{state="value==Hungary",trueAct={{"`cinemaSystem`","turnOn","","={$24clock:value=&CalendarDate}"},{"`sonyTV`","pressButton,26","6","={$24clock:value=&CalendarDate}"},{"`sonyTV`","pressButton,11","10","={$24clock:value=&CalendarDate}"}}}},

[Rover 47]

All fine this night with v9.7 ?

After this third successful night with the timing function I declare the problem for solved ?