Hello - I've been using Webcore on SmartThings for about 1 yr. Recently I got a Hubitat so that I can get the advantages of local execution. But I cannot log into Webcore. I loaded the Webcore apps into Hubitat. The main Webcore app is OAuth. I named this instance different from my ST instances. But when I go to the instance, log out, go to the Dashboard, and enter in a new code that I just got, I always get a message that there was a problem loading the dashboard, try logging out. What do I need to do to get the Webcore dashboard working with Hubitat? Also is it normal that I
As an aside, when I go to the Hubitat logs, all the times are wrong. They are off by 7 hrs. But my location is correct (Mountain time). What's causing that discrepancy?
As another aside, I keep trying to load 1.1.7 into my hub, but when I do a Version Check, it says there is no update available. Will Hubitat push the new version to my hub when it decides on the best time?
I personally had a lot of issues with webcore on here. Originally I was very excited that I was going to be able to use webcore with Hubitat. But the reality was way more problems that help. I've migrated all that I could to Rule Machine here. And left some of my pistons on my ST account. I'm just going to be running hybrid. Which for me isn't a huge issue. I really wanted just local processing of all my lighting/etc rules. Some of the things i have going on in webcore aren't millisecond time sensitive. Eventually I may write something local to bring that processing in house. But for now. It works, it's free and I don't have to write more code.
Head over to the webcore forums. You will find some assistance there with getting webcore to work on hubitat.
Just curious, what are the constrains that are making you leave some pistons in webcore? I understand they have been improving rule machine continuously to close that gap but I have not migrated yet so I'm not sure, my plan is to try and do everything on rule machine too...
Same. I'd fuss with it for a couple days, and get it to work. Then it stop allowing me to access it again. And, after trying for a few days, uninstall and reinstall ... then rebuilding all my pistons.
I finally gave up. Personally, I've moved to building my own apps, but Rule Machine is pretty robust.
The largest piston I really used webcore to do some processing for my security cameras. I have a python script that submits images to sighthound. It takes the return information and sends it into webcore. Webcore keeps track (via global variables) what the make/model/year of cars that it sees in my driveway. There really is no clean way to do this with rule machine. Then webcore uses this information and information about where I am to do actions. (Speak in the house someone is approaching the front door or someone is in the driveway) to sending me messages on my phone about what's going on.
Another one for more processing about camera PTZ positions and actions around the house based on motion or doors. There just isn't any clean way without tons of rules and rule truths and basically massaging RM to be faked into keeping information like global variables. Or using devices to do it using levels. Webcore is just really clean.
Also webcore's presence sensor...I'm crossing my fingers HE's will be similar. With webcore I can find out when someone leaves a place. Kids leaving school, Wife leaving work. Since my wife's work schedule isn't consistent I have a rule that looks at outside temperature and house temperature. If she leaves work in between a set of times I turn up the heat. She's about 30 min away from home so it's perfect. It's little things like that I haven't figured out how to do in RM. I think Life360 has that data but I don't think RM gets it. Webcore's presence sensor is literally perfect. That should be replicated.
All that being said I've pretty much figured out how to move everything else I can move over to RM. Do note RM rules can pile up because you can't do multiple things in 1 rule. So I HIGHLY suggest really thinking out your naming strategy because all those rules bundled together can get confusing. AND when something's turning off and you can't figure out why it can get tedious to find it because the device itself does not tell you which rule turned it off....only that it was turned off.
Wow, you have really cool stuff in place, specially the sighthound part! this has given me great ideas of things I'll eventually like to try and do...
Thanks for the advice, as I'll be starting from scratch I can see the naming convention being important to do from the beginning... Seems like rule machine will be able to take care of all my stuff as I definitely do not currently have any behavior as fancy as what you describe...
I fell in love with WebCoRE over on ST but I had major issues running it over here as it wasn't made for HE. The interface for Rule Machine doesn't work in the way my brain does. WebCoRE really seemed to click.
That all being said, Rule Machine is much more lean. It runs very quick compared to WebCoRE which ran faster than on ST when it wasn't crashing my HE hub. If I were you I would go through all of your Pistons and re-create them with Rule Machine. It's bit intimidating at first but it gets the job done and makes sense as you use it more.
As far as your update availability I've heard rebooting the hub from the settings page will help make it aware of the updates.
Thanks for all the comments. I rebooted my hub. That seems to have solved the Webcore loading and version update issues. As for the issues with Webcore on HE, I'm just getting started, but so far, I have noticed a few quirks that I am working through.
