[OBSOLETE] Super Notifier - All your alerts in one place!

swdeason · February 17, 2019, 5:07am

Sorry but I do not see where to go to PM you. I tried to reply via email but it kicked back.

JMZ · March 12, 2019, 6:40pm

Has anyone tested the TTS functionality? I’d like to polish out any issues and release it so everyone can use it. I don’t have any text-to-speech (TTS) devices to test it on. @MLUCK?

I’ve helped everyone with their [Super Notifier] issues, if I missed you please let me know.

tekken007 · March 12, 2019, 10:09pm

Somehow I don’t get any “Delayed” notification . This is the log. 1st, I set upper threshold = 10. Nothing happens. I then changed to 50, same thing. I am monitoring the power of a switch.

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:56:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.43 W, want it between -3000000.0 W &amp; 50 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.49 W, want it between -3000000.0 W &amp; 50 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:43 PM: info updated with settings: [monitorType:Power, wantsPush:true, myPower:Aeotec Nano Switch 2, periodicNotifications:false, powerTooHigh:50, waitThreshold:1, useTimeStamp:true, messageText:Delay Power Alert Aeotec 2]

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.98, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.98 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.98 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.94, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.94 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.94 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.83, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.83 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.83 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.79, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.79 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.79, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.79 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.14, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.14 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.14 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:52:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.08, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:52:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.08 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.11, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.11 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 17.11, scheduling stillWrong() in 1 minutes

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 17.11 W, want it between -3000000.0 W &amp; 10 W

[dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 17.11 W, want it between -3000000.0 W &amp; 10 W    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:57:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.3 W, want it between -3000000.0 W &amp; 50 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:57:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.21 W, want it between -3000000.0 W &amp; 50 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:56:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.43 W, want it between -3000000.0 W &amp; 50 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.49 W, want it between -3000000.0 W &amp; 50 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:43 PM: info updated with settings: [monitorType:Power, wantsPush:true, myPower:Aeotec Nano Switch 2, periodicNotifications:false, powerTooHigh:50, waitThreshold:1, useTimeStamp:true, messageText:Delay Power Alert Aeotec 2]

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.98, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.98 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:55:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.98 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.94, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.94 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.94 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.83, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.83 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:54:20 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.83 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.79, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.79 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info eventHandler has Aeotec Nano Switch 2: power: 35.79, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:50 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 35.79 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.14, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.14 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:53:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.14 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:52:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.08, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:52:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.08 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:49 PM: info eventHandler has Aeotec Nano Switch 2: power: 37.11, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:49 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 37.11 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info eventHandler has Aeotec Nano Switch 2: power: 17.11, scheduling stillWrong() in 1 minutes

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 17.11 W, want it between -3000000.0 W &amp; 10 W

    [dc6124eb-3301-4680-9550-35a1723d3bc8](https://graph-na04-useast2.api.smartthings.com/ide/logs#dc6124eb-3301-4680-9550-35a1723d3bc8) 2:51:19 PM: info powerHandler found Aeotec Nano Switch 2 is outputting 17.11 W, want it between -3000000.0 W &amp; 10 W

Instant notification works normally. One thing I am not sure is why I’m getting constant notification (like 2 per minute). Is it because of how power meter report changes ?

JMZ · March 13, 2019, 1:10am

Sorry it’s not working. Can you turn on debug logging (under “Advanced”) and repost the logs? I’m not sure where the breakdown is occurring.

Edit- just saw the bottom of your post, power meters report pretty much every change in power level as far as I can tell, so getting a ton of instant messages makes sense. You can fix that by setting a custom limit to the time between notifications in Super Notifier. Under the “Messase Detail” section there is a “Minites” input that allows you to set a time delay between each notification, so you can set it to 10 minutes or something.

I just ran a test in my home and it worked, so we’ll see what we learn from your logs.

tekken007 · March 13, 2019, 6:22pm

So after some more testing, here is the result:

Instant notification works fine.
“Power” type Delayed notification doesn’t work with this specific Aeotec Nano Switch. Instant Notification does work normally though.
Custom message never works. Instant and delayed both reacts the same. Tested with multiple devices. I keep getting messages like: “Outlet B is still 36W” or “Light B is still On”. No matter what I put in the custom message.
I also got “Outlet is Ok now” when I turn the power off. This doesn’t make sense since I didn’t set any lower threshold for alert. In addition, for some reason this kind of message doesn’t popup all the time. It’s like randomly appear.
If you create an instance using one monitorType (ex: switch) but decide to change it to another (ex:power), the app can’t/doesn’t update itself to the new monitorType.

Take a look at the following log:
First, I created an instance that monitor “switch” type. Then, I changed it to “power” (@ 1:10:33 AM). @1:12:14 AM, you can see it sent both messages: the “is still on” (which is for “switch” type), and the “is still 36W” (which is for “power” type)

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug daysOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug modeOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug stillWrongMsger() started

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug Power is still out of limits (36.06 W)

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug sent first message, set atomicState.msgSent to true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: info sent 'Outlet-MH-R2-B is still 36.06 W! (2019-3-13 01:12:14)' via push

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: info sent 'Outlet-MH-R2-B is still on! (2019-3-13 01:12:14)' via push

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug Event within time/day/mode/switch constraints

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug switchOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug timeOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug daysOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug modeOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug stillWrongMsger() started

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug Switch is still on

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug myContactState is null, mySwitchState is on, tempState2 is null, myLockState is null, myPowerState is 36.06

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:12:14 AM: debug stillWrong() started

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:11:14 AM: info eventHandler has Outlet-MH-R2-B: switch: on, scheduling stillWrong() in 1 minutes

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:11:07 AM: debug it's okay now, and never sent left open/closed/on/off message, so no need to send an 'ok' message

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:10:33 AM: info updated with settings: [periodicNotifications:false, waitThreshold:1, monitorType:Power, wantsPush:true, myPower:Outlet-MH-R2-B, mySwitch:Outlet-MH-R2-B, powerTooHigh:26, onOff:On, useTimeStamp:true, sunChange:false, modeChange:false]

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug sent first message, set atomicState.msgSent to true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: info sent 'Outlet-MH-R2-B is still on! (2019-3-13 01:09:37)' via push

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug Event within time/day/mode/switch constraints

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug switchOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug timeOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug daysOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug modeOk = true

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug stillWrongMsger() started

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug Switch is still on

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug myContactState is null, mySwitchState is on, tempState2 is null, myLockState is null, myPowerState is null

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:09:37 AM: debug stillWrong() started

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:08:37 AM: info eventHandler has Outlet-MH-R2-B: switch: on, scheduling stillWrong() in 1 minutes

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:08:30 AM: debug it's okay now, and never sent left open/closed/on/off message, so no need to send an 'ok' message

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:08:08 AM: info updated with settings: [periodicNotifications:false, waitThreshold:1, monitorType:Switch, wantsPush:true, mySwitch:Outlet-MH-R2-B, onOff:On, useTimeStamp:true, sunChange:false, modeChange:false]

aceda55b-972f-4163-bfd7-6f45ef6c2548  1:08:07 AM: info installed with settings: [periodicNotifications:false, waitThreshold:1, monitorType:Switch, wantsPush:true, mySwitch:Outlet-MH-R2-B, onOff:On, useTimeStamp:true, sunChange:false, modeChange:false]

JMZ · March 14, 2019, 2:36am

How did you figure that out? I don’t know why the device model would matter as long as it was sending the same type of power notifications. Lemme know, I’m curious.

I think this might be the very source of all your issues. When you change monitor types the app changes the options on your interface, but anything you had set before creates a variable, and not all variable names are the same (myContact vs myPower, etc), so some are almost definitely left in that instance of the app, creating unpredictable and unexpected problems. Each instance can live and die on it’s own, that’s the point, and the type of sensor being monitored is the root of each instance’s existence. I can go through and figure out how to wipe any unused variables in a new version of the app, but in the meantime please remove any instances you’re having problems with and set them up fresh. That’ll isolate out weird variable interaction.

Half of that is right, the delayed alert has a bug preventing custom messages, so I’ll fix that. Thanks for finding it! I’ll wait to release a fix until I hear back on your other issues, so we can make sure any other bugs are fixed in the release.

But the instant alert should be working for you. I just tried a new one without issue, and my others still work. I’m betting it’s related to changing monitor types of the same child app instance. Test out a fresh one and let me know if it still fails. Also, I’d bet any special characters would crush it, so try it first without any punctuation (if you have any).

It makes sense, as soon as the power level goes below that set upper threshold it’s ok (0 is less than the upper threshold you set). If you had both upper and lower thresholds, like 10 upper and 5 lower, then if it was at 15 you’d get an alert that it was too high, and when you turned it off, if it reported an instantaneous level between the 5 and 10 thresholds, it’d send an ok message, and then once it fell to 0, it’d send another saying it’s too low. That intermediate ok message may or may not get sent, it’d just depend on how fast the update interval on the device is.

tekken007 · March 14, 2019, 8:00am

Yeah, scratch that. You are right. Further (and more careful) testing confirms that the only thing that’s not working now is Custom Message for Delayed Notification.
Custom Message does work for Instant Notification.

Is that possible to make a button(or something similar) to create a new child app using settings from another existing child app? That could speed up the process a lot if somebody needs to set notification for multiple sensors.

Thanks

JMZ · March 14, 2019, 12:16pm

Rog, I just released an updated Delayed Alert smartapp in Github that fixes that issue.

Not that I’m aware of. I think it could be possible, but I’d have to spend some time working on it. That should only be a bigger issue for the delayed alerts, since they can only support one device at a time. For the instant alert, you can select tons of different devices all together (for example, you can select all the sensors you’d want to alert you when the mode is away in one instance of an instant alert app). I’ll look into it.

JMZ · March 14, 2019, 12:26pm

Sorry for the immense delay! I just released new instant and delayed app versions that have BETA Pushover support. It’s using this Pushover Device:

Pushover Notifications - Device Type Projects & Stories

I wanted to move all of my notifications over into one area and so far I have been very focused on using Pushover. I know that there was a “notify me when with Pushover” but that didn’t fit my needs… I wanted something that I could easily integrate into all SmartApps that I wrote with just a simple line of code. I have created a simple Device Type where you put in your Pushover API keys and an option to send notifications to only one Device (Pushover Device). Once that is created you can just add in the following lines into any SmartApp to send notifications: preferences { section("Pushover Device") { input ("pushoverDevice", "capability.notification") } } And to send a notification: pushoverDevice.sendMessage("This is a message from SmartThings", "Normal") The code is available…

It’s a very old thread and code, but I’ve duplicated the DTH code in my own github repository if you want to install it from there. The idea is you install a “Pushover Device” into SmartThings so you only have to enter your Pushover credentials once, and then each smartapp can access that device to send Pushover notifications. Each Pushover device can send to a specific phone/computer/etc that you have in your Pushover account, or to all of them. So if you want to tailor your notifications, just create a Pushover device in SmartThings for each phone/computer you want to individually send notifications to. Then in each smartapp you just pick the devices you want them sent to.

Once you add the code to your IDE, install the device from the SmartThings app on your phone, then go into your Super Notifier settings and add the device to get notifications via Pushover.

I’m anticipating some bugs with this, so please let me know how it works (with logs please). Looking at the device code, I think every message will be delivered with ‘normal’ priority, despite what you select…

Looking forward to feedback!

xdreamwalker · March 14, 2019, 2:34pm

While I haven’t tried this Pushover device. I do use this Pushover Manager in a few places.

xraive · May 1, 2019, 5:30pm

Hi there,

Before I start I would like to thank you for this app. It’s exactly what I was looking for.

I setup a delayed alert for a door sensor to notify me when it’s left open. I was able to get push and sms notifications to work quite easily, but I’m having a hard time getting the audio notifications to work. I have a Samsung Radiant 360 R1 Multiroom speaker that I would like to use for the TTS.

I have the log results below.

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: error java.lang.NullPointerException: Cannot get property ‘uri’ on null object @line 598 (doCall)

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug Event within time/day/mode/switch constraints

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug switchOk = true

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug timeOk = true

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug daysOk = true

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug modeOk = true

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug stillWrongMsger() started

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug Contact is still open

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug myContactState is open, mySwitchState is null, tempState2 is null, myLockState is null, myPowerState is null

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:01:42 PM: debug stillWrong() started

a23987c6d01-b106-437e-acfe-86f87966f82349e 12:00:22 PM: info eventHandler has Test Sensor: contact: open, scheduling stillWrong() in 1 minutes

FYI I have a SmartThings ADT hub with sensors.

Any help would greatly be appreciated.

Sandra_Lucas_Lara_y · May 5, 2019, 7:26pm

great work, please, add the option of swhict on in the normal notifications, just as it is in the delayed ones, it would be very useful.

David_Schmidt · May 8, 2019, 12:25pm

When I try to add the Github repository I get:

You don’t have access to flyjmz/jmzSmartThings

I used the details from the original post of:

Owner: flyjmz
Name: jmzSmartThings
Branch: master

NOGRP1337 · May 17, 2019, 9:54am

Hi there,

Can someone tell me is there a way to get notification only when intrusion detected?
Just to be aware which sensor detected the intrusion.
Thanks.

JMZ · May 17, 2019, 6:16pm

@xraive thanks for posting the debug log, I’ll have to do some digging to figure out what is wrong. I don’t have any TTS devices to test, so I expected some errors. You’re the first to post, thanks!

@Sandra_Lucas_Lara_y I’m not sure what you mean. It has the option to be notified when a switch is turned on/off, and it has the option to turn a switch on/off when something else is triggered. Please explain so I can help out.

@David_Schmidt Hello! Sorry you’re having issues. Nothing has changed, so it should work. Have you tried again recently? Sometimes it really is just a restart/reopen/give it some time to solve the issue. The platform is growing rapidly and has little glitches on occasion. Also, have you tried adding other repositories and been successful? If not, try another one to narrow the scope of the problem. It may be something support will have to look into.

@NOGRP1337 Welcome! Just set an “execution restriction” for modes and choose Away. Assuming you have your system set to switch modes to away when you leave (or via some other method), then the triggers you set in this app to notify you will only occur when the mode is away (i.e. no one is home). That’s just a typical example, and I hope I’m understanding your question properly, but there are lots of ways to do anything. If that doesn’t make sense, please let me know the scenario you are trying to automate so I can help (e.g. you want to be notified if a door opens while no one is home).

NOGRP1337 · May 17, 2019, 6:37pm

@JMZ Thank you for your response. That’s definitely what I’ve been looking for.

Another problem was that the mode was not changed from home to away. Than I set a routine. Now it’s perfect. Thanks.

xraive · May 18, 2019, 6:59pm

Let me know if you need additional info. Great work by the way. This app is amazing. It’s already saved me once. I have it setup with a sensor on the fridge.

MLUCK · May 28, 2019, 2:51am

@JMZ sorry for going the dark side of the moon. Got busy at work blah blah blah.
But home automation can’t keep me away forever.

How can I best help test TTS with SuperNotifier for you?

jmhandel · May 29, 2019, 5:34pm

@JMZ Great app. Thanks for your efforts.
I have a water sensor that I would like a delayed alert. It seems like the sensor options for delay do not include those sensors like in the instant alert child app.
Am I missing something?

JMZ · June 10, 2019, 10:38pm

Updated both instant and delayed alerting apps! Added water sensor to the delayed app (it was already in the instant app), updated the UI some, and am continuing to troubleshoot TTS support.

@jmhandel Thanks! It didn’t, but I just added it, let me know if you have any issues.

@MLUCK & @xraive I changed the TTS stuff, see if it works and post logs so I can continue to track down the errors. Also, if anyone knows where the TTS documentation lives, it’d really help. I’m trying to follow along on some other apps and nothing is consistent.

Topic		Replies	Views
[OBSOLETE] Sharing some of my SmartApps (multiple lighting apps, garage check, not everyone leaves) Community Created SmartApps smartapp_alerts , smartapp_garage , smartapp_presence , smartapp_lights	2	2802	August 10, 2015
Z-Wave Garage Door Sensor - Delay notification? Devices & Integrations	2	1356	December 17, 2017
Newbie question to control door sensor Automation Ideas	6	1190	September 27, 2015
Temporary Door Notification - Toddler alarm? Automation Ideas	3	1524	July 5, 2017
How to enable notifications for multipurpose sensor only during certain modes (home, away, night, etc)? Also, how do you create new modes? SmartThings (Samsung Connect)	3	3147	April 23, 2019

[OBSOLETE] Super Notifier - All your alerts in one place!

Related topics