Fading temperature and level at the same time

bug
#1

1) Give a description of the problem
Evething else tends to work but no mater how I write it eather it doesn’t change the temperature at all or it skips to the end. The other thing is there track variable I can’t get that to work correctly.

2) What is the expected behavior?
When the wife is there at a certain time the light comes on at Min and at 2710k, then over a hour gets brighter and changes temperature to 6500k. Then after the hour speak the random text on the Sonos then restore the Sonos level and track to what was in the que before (what I actually want it to do is speak a set of random text depending on if the weather is going to be nice or not using two sets of random text)

3) What is happening/not happening?
Can get it to brighten but not change temperature

**4) Post a Green Snapshot of the piston!

download (1)
download (1).png1178×885 174 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
No logs

#2

Select all your actions (with statements) and change the TCP to never cancel.

Edit: we can work on the weather part after getting the general functionality working.

#3

Yeah that was the plan need to get the main stuff working first.
Ok will try that

Edit: had to make a few more tweaks to how i had it before i put it on here, as i must have been slightly on the right lines but thanks @c1arkbar you got me over the line! Why does having never cancel set make such a difference, surely it shouldn’t have been canceling in the first place?

This is my tested piston but only for 5 mins so ill let you know after tomorrow morning if anything else didn’t work.

image
image.png1178×935 54.4 KB

Just the speaker and the weather to sort now :wink:

#4

Gonna copy paste an answer to this question from the Facebook group. Couldn’t get the Facebook app to open the actual comment or let me copy this so a screenshot will have to do

E492907A-EE3D-4F87-908D-EDA94D223B51
E492907A-EE3D-4F87-908D-EDA94D223B51.png750×1334 126 KB

#5

Still having issues but it seems to be to do with the fade time. It works for 5 mins 6 mins and 30 mins but not for 50 mins, 1 hour or 60 mins.

image
image.png1178×935 53.4 KB

@ady624 is there any known issues with the timer?

#6

Hi @ady624 have you had chance to look into the timer? If it helps, I will edit a piston again and put it back in for a hour and put trace and stuff on .

#7

not @ady624 :slight_smile: but set TSP to allow multiple for both with groups with fade tasks and it will work as expected.

#8

It works as expected as it is (is there something else i have missed though?), the issue is if i change the timer from 30 mins to 50 mins or 60 mins or 1 hour it doesn’t work?

#9

right, have you already tried setting TSP to allow multiple with 60 min timers and it doesnt work?

#10

I think I tried it at the beginning, but I will try it again to make sure and let you know the results tomorrow.

Is this what you mean?

image
image.png1178×935 59.1 KB

#11

yes please.

#12

Nope, same again it just keeps pending then looking like it worked then pending again, but no logs to say it working. But it was working before without the TSP and if it was set to 30 mins.

download (3)
download (3).png1178×956 203 KB

#13

anything in the ST logs?

#14

no how do i get them? as you only seem to be able to do it if the page is open when its running.

#15

if you log in to your ST account you can see the live logs and everything else over there. let me know if you need more details.

#16

46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: info ║ Setting up scheduled job for Tue, Oct 17 2017 @ 7:00:00 AM BST (in 45156.939s) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition #34 evaluated false (5ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Cancelling statement #34's schedules... 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Cancelling condition #2's schedules... 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Comparison (time) 66443034 happens_daily_at (time) 25200000 = false (2ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Cancelling condition #34's schedules... 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Comparison (enum) off is (string) off = true (1ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition group #2 evaluated true (state did not change) (8ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition #36 evaluated true (7ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition group #null evaluated true (state changed) (18ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Cancelling condition #null's schedules... 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Comparison (enum) on is (string) on = true (1ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition #12 evaluated true (7ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Comparison (enum) present is (string) present = true (2ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: trace ║╚ Execution stage started 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Condition #1 evaluated true (8ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: trace ║ Runtime (45399 bytes) successfully initialized in 47ms (v0.2.0fa.20171011) (140ms) 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:23: debug ║║ Cancelling condition #1's schedules... 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:22: debug ║ RunTime Analysis CS > 14ms > PS > 47ms > PE > 69ms > CE 46ae976c-457b-4db2-89c4-be6f598c03e6 18:27:22: info ╚ Received event [Home].test = 1508174842853 with a delay of 7ms

this is all i have at the moment is there a way of retrieving previous logs?

#17

this is the piston log. i was referring to the ST logs. once you are there, you will need to run the piston and watch the live logs to get any messages from the piston.

#18

That is the logs from ST that happened when I pressed test on the dashboard. I will clear that and get it to run again :slight_smile:

#19

see this:

#20

1611af3f-808d-4354-a07e-101c90c6418c 19:57:34: error physicalgraph.exception.StateCharacterLimitExceededException: State cannot be greater than 100000.0 characters 1611af3f-808d-4354-a07e-101c90c6418c 19:57:30: error physicalgraph.exception.StateCharacterLimitExceededException: State cannot be greater than 100000.0 characters 1611af3f-808d-4354-a07e-101c90c6418c 19:57:26: error physicalgraph.exception.StateCharacterLimitExceededException: State cannot be greater than 100000.0 characters