Local HTTP for Receiver


#1

1) Give a description of the problem
I’m trying to send to commands to my Directv receivers at a specific time.

2) What is the expected behavior?
When command is sent, receiver turns on which turns tv on then the receiver changes channel to 12.

3) What is happening/not happening?
Nothing visible.

4) Post a Green Snapshot of the pistonimage

5) Attach any logs (From ST IDE and by turning logging level to Full)
3/19/2018, 8:43:33 PM +18ms
+2ms ╔Received event [Rene’s Motion Sensor].illuminance = 0 with a delay of 85ms
+117ms ║RunTime Analysis CS > 18ms > PS > 79ms > PE > 19ms > CE
+119ms ║Runtime (39129 bytes) successfully initialized in 79ms (v0.3.000.20180224) (116ms)
+120ms ║╔Execution stage started
+130ms ║║Comparison (integer) 0 is_greater_than (integer) 1 = false (1ms)
+131ms ║║Cancelling condition #7’s schedules…
+132ms ║║Condition #7 evaluated false (7ms)
+133ms ║║Cancelling condition #1’s schedules…
+134ms ║║Condition group #1 evaluated false (state changed) (8ms)
+136ms ║╚Execution stage complete. (16ms)
+137ms ╚Event processed successfully (137ms)
3/19/2018, 7:43:35 PM +596ms
+1ms ╔Received event [Rene’s Motion Sensor].illuminance = 9 with a delay of 73ms
+89ms ║RunTime Analysis CS > 16ms > PS > 57ms > PE > 16ms > CE
+91ms ║Runtime (39133 bytes) successfully initialized in 57ms (v0.3.000.20180224) (89ms)
+92ms ║╔Execution stage started
+101ms ║║Comparison (integer) 9 is_greater_than (integer) 1 = true (2ms)
+102ms ║║Cancelling condition #7’s schedules…
+103ms ║║Condition #7 evaluated true (6ms)
+104ms ║║Cancelling condition #1’s schedules…
+105ms ║║Condition group #1 evaluated true (state changed) (8ms)
+115ms ║║Comparison (time) 71015703 is_between (time) 27600000 … (time) 27900000 = false (6ms)
+117ms ║║Condition #6 evaluated false (10ms)
+118ms ║║Condition group #2 evaluated false (state did not change) (11ms)
+120ms ║╚Execution stage complete. (29ms)
+121ms ╚Event processed successfully (121ms)

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.


#2

From the logs, the lux has always been below 11, so the piston did not execute.

If you are indeed trying to send the commands at a specific time…then make TIME the trigger and not the lux reading. You can use “Time happens daily” or use a “Timer” to get that.


#3

In addition to what @Mike1616 said…
From the piston logs, you’re executing this in the evening(?), but you have a time restriction in place to only execute the remaining code between 7:40am - 7:45am.
For testing purposes, I wouldn’t put any time-based restrictions in just yet… Make the desired action work first, then look at adding restrictions.


#4

Ok Mike. Thank you. I’ll try that.


#5

Ok Allrak. I’ll take the time restriction off.