"Invalid Alert Name" message on tstat screen for a DR event (showIdt = false)

Hello !

We already noticed and reported the fact that even if you specify "showIdt" to false, ecobee still sends a notification / alert to the thermostat (same happens for email and web access)
We reported it in http://developer.ecobee.com/api/topic...

Now, while doing tests with a different tstat device we've seen a different behaviour.

Let me compare.

Tstat1) This is the one we were using before

Thermostat Model: Smart Si
Firmware Version: 3.3.0.566

The screens:



Then:



Tstat2) a new one that shows the weird message:

Firmware version: 3.5.0.3890



Check out the message there that says "Invalid alert name"

The questions are

1) what is the reason for that message ?
2) is it related to the bug we reported ? (meaning that it shouldn't be shown at all because of the showIdt = false ?

Thanks !

Regards
2 people have
this question
+1
Reply
  • I am also running into this issue with the Smart Si displaying a screen with date, time, and "You have an Alert" followed by an empty screen.

    These alerts show up on the thermostat anywhere from 1 day to a week or more after the date shown on the alert. The alert showing on the thermostat seems to correlate with when the thermostat receives new demand response events, and they do seem to correspond to times where events were sent with showIdt = false. E.g. I send a demand response on the 13th at 14:31, and an alert shows up from the 8th at 15:24.

    I don't have an ecobee3, so I haven't seen if there is an "Invalid alert name" message involved or not. However, this makes me wonder if the issue is possibly due to some encoding oversight, as in this topic: http://developer.ecobee.com/api/topic... . (Before seeing the aforementioned topic, I did not realize that the body of a POST needed to be url-encoded as well; my code now does that).

    These phantom alerts also seem to be interfering with the display of messages where showIdt = true.

    Any insights on how to prevent such alerts from showing up and/or any way to clear the backlog of these alerts would be greatly welcome.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • MarkK (API Architect) July 20, 2015 17:29
    We are investigating the issue. Thanks for reporting.

    Mark.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Hi Mark, I appreciate you guys taking the time to look into it. Here's a little update with some more observations:

    I'm getting blank alerts from dates after I added url-encoding to the POST body, so it looks like that wasn't the issue.

    I've been continuing to monitor when the alerts show up, and they are consistently linked to when new demand response events are received -- aside from one that will show up a few seconds after the thermostat boots up after being powered down. The dates/times on the incoming alerts don't seem to align with anything (i.e. no correlation between time on alert and time it shows up), but they do show up in roughly chronological order.

    I have not received any error/unexpected responses at all from sending events.

    Interested to hear what you find out; please do keep us posted!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Another update with some new happenings:

    On 7/24, my test thermostat was still having the alerts pop up as had been the case, but after about 5 of them, they stopped showing up. I would still get one alert popping up shortly after the thermostat booted up, but none during periods of events.

    Then on 7/28, the alerts came back with a vengeance. Previously, I had tried letting an alert sit for a while before clearing it, and when I finally did clear it, it was the only one -- no others immediately popped up. On the 28th, I wasn't seeing alerts at first, so I didn't pay too close attention to the thermostat. When I did check it at various intervals later on (during periods where events were being sent), I would see groups of 4-8 alerts in succession (i.e. clear the first alert and a second immediately pops up, clear the second and a third immediately pops up, etc...).

    One other thing that may or may not be related: I also got some thermostat crashes/resets earlier today when testing events. I have experienced crashes previously while testing on an older touchscreen model, but I believe this is the first time that I have seen the Smart Si suffer a crash, and it did appear to be correlated with the events. After crashing, the thermostat came right back on though, and resumed and carried out the event that was already in progress.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • MarkK (API Architect) July 29, 2015 19:26
    We have identified this as a bug and it has been fixed. It will be in the next production release we do. I don't have a timeframe for that though. Thanks for reporting.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Is there any news/updates (or workarounds) with this issue? I've still been experiencing it, and some of our customers have been reporting it as well.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Any updates or ways to clear the backlog of these alerts for a thermostat? It may also be worth mention that this occurs with Demand Management events as well as Demand Response events.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned