After trying the T3000, I’ve gone back to our ecobee4 as of yesterday. This morning ADC threw this message. I’ve since tried removing the bee and re-adding but no luck. The bee was ok overnight. I suspect it’s something to do with the 2FA that ecobee requires, although when re-adding, it seemed to add ok, just not showing full connectivity.
“Malfunction (Ecobee) indicates that this device is unable to send signals to your security panel. Automation rules and commands to control this device may not work.”
The ecobee web and app show full connectivity. Beestat is good too.
Very odd. I’m getting in contact with ADC’s automation team on this one. Seems to be a stuck status on the account, but just in case it is a mistranslation of status, have you tried new batteries?
The ecobee4 comes with a room sensor that uses battery power, correct? I am curious if something like that may be mistranslated through the API and causing this.
Yes, that was Alarm.com’s suggestion. However after that we are left with basically resetting the Ecobee and removing/readding thermostats on the account.
When activating it is odd that the status is immediately malfunction, which is why I expect this is actually something being passed by the ecobee API.
Over the weekend I’ll unlink/remove/reset everything related to the ecobee and report back.
Is there any chance that there’s something stuck in the account related to having installed/removed the T3000, something that ADC can reset on their side?
Removed all connected apps from ecobee account, reset ecobee4. Cleared browser cache for all ecobee.com, alarm.com, and beestat.io cookies. Changed name of ecobee. Beestat connects no problem. I connected Google home and it connected correctly and can control the ecobee without issue.
Something interesting that may be a clue for ADC. After connecting google home, I’ve changed the name of the stat a couple times. Google home is able to track the name change correctly. ADC however still thinks the stat is named “Ecobee” which is the original name I used before trying out the T3000 and then switching back to the ecobee. Currently the stat is named “Thermostat”. Beestat and Google home both track the name correctly, but not ADC, even after removal and relinking. (btw, tried renaming to “Ecobee” but that didn’t help ADC reconnect. GH and beestat got new name though.)
I’m also seeing the same errors and behavior with my Ecobee thermostat on my alarm.com account starting a few days ago… seems to work via the Ecobee app as well. Removing and readding resulted in an immediate error as well. New batteries in my remote sensors didn’t help.
Thanks for adding this, it does sound like there may be an issue with the ecobee integration currently. I’ll let ADC know we are seeing the same issue on multiple accounts and will follow up here with info.
Removed all connected apps from ecobee account, reset ecobee4. Cleared browser cache for all ecobee.com, alarm.com, and beestat.io cookies. Changed name of ecobee. Beestat connects no problem. I connected Google home and it connected correctly and can control the ecobee without issue.
Thank you, this helps force the ball into ADC’s court. I think it is safe to say this is likely an issue on the back end, but I will follow up with any additional troubleshooting they recommend.
I installed a new ecobee and am have the exact same problem. Eve ry few hours I get a notification that it’s off line and at random intervals it come back online. Averaging 2 times a day.
Did the reset thing, unpaired, repaired.
When I re paired, it immediately showed Device Malfunction on my ADC mobile app at the top
Unit is controllable from the Ecobee app
When it goes offline I watch the thermostate and its not rebooting. When it says its offline, I can control it from the ecobee app which would indicate its not a wifi issue
Unit is controllable by the ADC app, but it will turn on the heater, let you set a temp. and the furnace comes on. But then the ADC app shows the thermostat off pretty soon after the furnace is on… When the furnace is running, I cant turn it off from ADC as it shows “off” on ADC
Has there been any updates on resolution? It’s been quite a while.
If not, is it possible to not get notified of it being offline until a solution is found?
I also notified Ecobee and suggest others users do as well so they know this is not an isolated issue and this way save them time from trying to diagnose wifit, reset, repair procesdures with others.
I would still request Surety pursues this with ADC since we can’t contact directly and I would ask that there is frequent follow up until this is resolved. ADC is not known for its responsiveness on issues like this as indicated by the non response after this last post before mine 2 years ago. Surety needs to remember that I would probably have abandoned ADC if it were not for Surety as Surety is the one that has gotten answers for me when I have ADC issues. Counting on you here!
Ecobee said theissue may be due to the wifi signal jumping between access points on my Orbi Satellites. Suggesting moving one close to the thermostat so it locks onto that one.
Did it, but I hate having that satellite visible in place now.
It seemed to clear all the issues, and it keeps updated on ADC app and the malfunction error is no longer there.
.
I stil think ADC can fix the integration by putting a delay before notifying the unit is offline. Like 5 minutes. Plenty of time for a device to switch access points.
Can you please tell ADC to do thits. Between here and Reddit and others, it would cut down on some complaints and troubleshooting requests