WebCore didn't fire yesterday

[toy4rick]

Hey all,

I have a simple WC Piston that is supposed to text me when the temp get too hot in my house so I can then decide to turn on the AC/House fan... or do nothing

Yesterday I never got the text even though I can see in the logs for the ecobee that the temp hit 78 starting at 1:01PM. I recognize that it will only text me once...

There were no other texts yesterday so I didn't hit the 10 limit

Anyone seeing issues similar to this lately?

Thanks, Rick

[ogiewon]

@toy4rick

I have a simple RM Piston

I think you mean you have a "webCoRE Piston"... may want to change the title as well.

[toy4rick]

TY - Done

[bertabcd1234]

You said you checked the logs for the ecobee, but do you know if all of your presence sensors actually went "away"? That would obviously prevent this from running the "then." You might also try using manual piston state and maybe rework the logic a bit (if ecobee rises above...then, if all presence sensors are away...then, SMS notify me...else) so you can go back to the dashboard later and check the status. The piston states could be something like "Thermostat rose above X at TIME but not changed because not away," "Thermostat rose above X at TIME; sending notification," etc., so you know code paths were executed and what it thinks it did. (Not really sure if that's how that feature was intended to be used, but it works for me on similar pistons and even for troubleshooting it can be easier than trying to turn on and read logging.)

[toy4rick]

Thanks bertabcd1234

Looks like my daughters phone is no longer indicating presence, since it was showing her home, the Piston never fired, as designed

Now to figure out why her phone is now acting up

Thanks, Rick

[csteele]

I added Homebridge again. (I keep adding it, then deleting it as I wonder if IT is the thing. As far as I can tell, so far, it has never been the cause of anything suspicious.) I did it this time specifically to use our iPhone's presence. It's remarkably good but was a really horror to get working on both my iPhone and my wife's.

What's easy (for me) to forget was that it's iCould in the mix too. I have 3 devices all using my iCloud ID and everytime I touched one, presence would fail, because I kept telling it to use the WRONG iDevice.

I'd open an iPad and see it was not sharing location, so I'd set it. Which I eventually realized was also altering my iPhone to let the iPad be the presence sensor. Well it never left the house, and so presence indicated exactly that. I hate it when machines do exactly what I tell them to, vs read my mind.

[toy4rick]

Hey all,

As it turned out, my hub wasn't connected to the cloud. While working with Bobby in support, he suggested shutting down the hub, pull the power for a minute then reboot. Sure enough it fixed the issue.

He also indicated there should have been a notification in the upper right corner about it not being connected to the cloud, something I never saw and he is submitting a ticket for.

It all seems to be related to improperly power cycling the hub during construction, and all it needed was a proper shutdown and reboot

Thanks, Rick