Challenges with Flasher SmartApp

smartapp

(Michael) #1

Hey folks - Wondering if anybody who has experience troubleshooting the Flasher app could take a look at this log and tell me what they think the issue is. I’m relatively new to the ST platform (and admittedly from another generation of programmers) so not sure what I’m looking for yet. The Flasher is set to flash three times when a door contact sensor opens. The door contact sensor is the NYCE hinge sensor and the light is the Iris Smart Switch in a wall socket with a lamp attached. Both device handlers from this community. I spaced the flashing frequency out to 2000ms in order to see if the flashing was happening too fast for the switch. Still wondering if that is the problem. Outcome is light is turned on once but that’s the end of it.

The Flasher appears to trigger correctly.

a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: trace Switch off after 10000 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: trace Switch on after 8000 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: trace Switch off after 6000 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: trace Switch on after 4000 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: trace Switch off after 2000 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: trace Switch on after 0 msec
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: debug LAST ACTIVATED SET TO: 1460295862754
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: debug FLASHING 3 times
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: debug DO FLASH: true, ELAPSED: 1026536, LAST ACTIVATED: 1460294836217
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: debug LAST ACTIVATED IS: 1460294836217
a3ae252a-c3c9-4cd8-8567-ef4fa8e598ff β€Ž6β€Ž:β€Ž44β€Ž:β€Ž22β€Ž β€ŽAM: debug contact open

Then the log for the Iris Smart Switch is below.

dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž25β€Ž β€ŽAM: error java.lang.NullPointerException: Cannot execute null+null @ line 150
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž25β€Ž β€ŽAM: info [name:power, value:62, type:power]
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž25β€Ž β€ŽAM: debug description is read attr - raw: 3211010B040A0B05293E00, dni: 3211, endpoint: 01, cluster: 0B04, size: 0A, attrId: 050b, encoding: 29, value: 003e
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž24β€Ž β€ŽAM: error java.lang.NullPointerException: Cannot execute null+null @ line 150
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž24β€Ž β€ŽAM: info [name:power, value:24, type:power]
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž24β€Ž β€ŽAM: debug description is read attr - raw: 3211010B040A0B05291800, dni: 3211, endpoint: 01, cluster: 0B04, size: 0A, attrId: 050b, encoding: 29, value: 0018
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: info [type:switch, name:switch, value:on]
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: debug description is on/off: 1
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: info [name:switch, value:on, type:switch]
dbcf4c08-bb3c-46a2-b23f-eb17189aa267 β€Ž6β€Ž:β€Ž44β€Ž:β€Ž23β€Ž β€ŽAM: debug description is catchall: 0104 0006 01 01 0140 00 3211 00 00 0000 0B 01 0100

On a related note, why does the Iris Smart Switch report a power level as follows? I notice it in the dashboard and in the notifications log in the ST app. Not a dimmer.

switch: on
power: 6.1
heartbeat: alive

Thanks. Learning a ton from this community in only a couple weeks of playing with the ST hub.


Home Monitor > Alert with Lights > Blinking
(Bob) #2

When the new scheduler was rolled out a couple weeks ago, it was subsequently discovered that ms were being treated as seconds. Thus why the switch came on but then appeared to be stuck on. If you hung around long enough, you would probably see it toggle 2000 seconds later.

Maybe someone else can chime in with when the ETA is for a fix. With all the ongoing platform issues, I’ve lost track.


(Stuart Buchanan) #3

there isn’t an ETA yet, it was due to be rolled out last Wednesday, but it has been held back, most likely because the β€œfix” introduced other issues… there is no ETA yet


(Michael) #4

That explains a whole hell of a lot. I came home after running a couple errands to have my wife say that the light came on and went off while I was gone. I was perplexed in looking at the event logs.

So 1ms actually equals 1s. Got it. Thanks a ton.


(Jason "The Enabler" as deemed so by @Smart) #5

I heard there was going to be a fix on Monday?


(Mistman ) #6

did this never get fixed?