This is great news to know there is an investigation, and ecoBee is working.
Thank you
1 Like
Hey Derek,
I'm trying to copy your rule. How do I Set hubName? Can't figure that part of the actions out.
1 Like
Howdy, you don’t need to, that bit of the rule is grabbing your hub name from the hub and storing it in a local variable. First time you run the rule it’ll populate.
Ok, I was able to figure out everything else on the rule and get it plugged in, but couldn't figure that part out... I just ran the rule and my hub is rebooting... let me see what it looks like when it comes back up.
also i tried to download and import your rule, but that didn't seem to work.
1 Like
that didn't work... hub rebooted cause i ran the rule, but still don't have the first line Set hubName under actions.
Strange, I just exported the rule from RM, I wrote the rule that way because I have multiple hubs and this meant I could just write it once.
You can just modify the local variable manually if you like.
ok, I'll try that... 
1 Like
I just checked and downloading and importing my rule from GitHub does work. I’m wondering if your browser didn’t save it as a raw text file.
Not sure, I went to raw text and copied it into a file then tried the upload... either way, i see why you created it with the naming variables. I just replaced that part and wrote the rule specific to each hub. curious to see if this will help with my lockups. i'd rather they reboot when i don't need them... 
Sorry I didn’t see your rule in the earlier post, it doesn’t have the hub name because you haven’t duplicated that part of my rule.
I’m pulling it from hub info’s locationName and feeding it to a local variable called hubName at the start of the rule.
2 Likes
Just right click anywhere and select “save as” or “save page” depending on the browser.
2 Likes
I had taken out the ecobee integrations/devices on 3/26, and installed the memory monitor. I checked it manually every few days, and there may have been a slight downward trend, but the numbers seemed to fluxuate in a fairly narrow band. I left town for a few days, and when I returned the hub was locked up / unaccessable via the web page or programmatically through Alexa integration. The last backup date was 4/2 (I returned 4/6), so it appears that it worked from 3/26-4/2, or about 7 days. I had to do a soft reset and restore from latest backup, and it appears to be working again.
So my question at this point is how should I proceed? When it locks, I don’t seem to have access to the memory logs from the reporting tool, so I don’t know if the two things are related. Any advice on what to do next? I could implement the watchdog/reboot on low memory, I suppose, but prior to this starting, my hub would run for months in between reboots.
There is an update currently being beta tested that will hopefully resolve these unexplained lock ups people are having recently. I would sit tight for now.
The update that @jtp10181 referred to is is out - 2.3.8.138. Update your hub and see if it helps...
3 Likes
Any idea if the known issues got fixed? The release post has almost no information in it.
If it doesn't resolve the issue, please PM me your hub id.
No, this 2.3.8 update is focused on a single change that will hopefully mitigate hub lockups. Everything else is slated for 2.3.9.
2 Likes
@rrands1 - this message is for you. You are important!
1 Like
So not even the hub variables issue was fixed?
Correct...2.3.8.138 is a very targeted release.
1 Like
