WARNING about webCoRE


#46

Life360. The default choice. I suppose you can call this non "native" but that just seems like semantics.

In any event, I may switch to doing presence via HA if Life360 continues to drop presence events.


#47

Thanks, just wanted to make sure I wasn’t missing something.


#49

I'm sorry you had trouble in your latest update. I offered to assist you in resolving this but you refused.


#51

Well. There's a statement.
I take it you are not happy with webCoRE.
You do not have to use it.


#52

I think it's phenomenal that you guys are still keeping up with this. I find it to be very dev friendly and easy to debug. Made the switch over to RM during the earlier WC woes but have always been following your progress. May consider putting it back on my "controller" hub now that I have a multi-hub setup.

Thanks again @nh.schottfam!!!!


#53

Some more information on all this:

In summary it is becoming clear that webCoRE is not the root of these issues (see the thread):


#54

WebCoRE is not the root of ALL lockups, no. But it definitely can cause a hub lockup. I've seen it happen. In my setup I had several pistons that subscribed to IFTTT events and used global variables. I watched my hub go from running to slow to total lockup right before my eyes. So, WebCoRE definitely can cause a lockup. Just because it isn't the only thing that does, doesn't mean it's 100% safe to use.


#55

I had the latest running on my hub for over a month and didn't witness any issues whatsoever. Where as before @nh.schottfam got involved there was definitely issues with it. I have just removed it as with the latest RM 3.0 I believe I can now do everything I could with WC so currently no need to use it. I just wish it had been fixed earlier before I learned RM :rofl:


#56

I agree. webCoRE does make my hub slow down and eventually lock up. I found this out months ago and haven't tried again with the updated code.
It also, for me anyway, does not run as quickly as RM.
Believe me no one is more disappointed than me that this happens as I love webCoRE.
I have got my head round RM3.0 and it is evolving with every new release but I just find webCoRE easier to use.


#57

I agree 100%. But hey, gotta do what works, right? I'm down to 1 webcore piston at this point and it only responds to unsolicited webcalls from IFTTT. So, I'm not too worried at this point. And as soon as my groovy skills get a little better maybe I can ditch it all together. :slight_smile: