I agree, and will do that if necessary, was just looking for confirmation. I try to make my pistons as simple as possible when I can.
I am getting the following error when using the ported version of WebCore - anybody have any ideas on how to fix? Executed [Kitchen Desk].setLevel (18ms)
+1365ms ║║An error occurred while executing the event: groovy.lang.MissingMethodException: No signature of method: com.hubitat.hub.domain.Location.hasCommand() is applicable for argument types: (java.lang.String) values: [setLevel]
setLevel shouldn’t be “string” right? It only takes a numeric value.
Yes - I am sending an Integer.
I read through the thread and was rather intimidated in being able to install WebCore on Hubitat. Thanks to everyone's work in porting it (and the developers), it turned out to be relatively easy and straightforward. Here are the steps to install:
-
Go to the GitHub repository
-
Click webcore.src
-
Click webcore.groovy
-
Copy the code. You can click the Raw button to display just the code, select it and use Ctrl + C.
-
Go to the Hubitat app.
-
Click Apps Code.
-
Click New App.
-
Paste the code (you can use Ctrl + V).
-
Click Save.
-
Click OAuth.
-
Click Update.
-
Repeat for the other webcore app components:
On GitHub (click Back in browser four times), click webcore-storage.src. Click webcore-storage.groovy. Copy the copy. Go to Hubitat app. Click Apps Code. Click New App. Paste the code. Click save. Click OAuth. Click Update. -
On GitHub (click Back in browser four times), click webcore-piston.src. Click webcore-piston.groovy. Copy the copy. Go to Hubitat app. Click Apps Code. Click New App. Paste the code. Click save. Click OAuth. Click Update.
-
On GitHub (click Back in browser four times), click webcore-dashboard.src. Click webcore-dashboard.groovy. Copy the copy. Go to Hubitat app. Click Apps Code. Click New App. Paste the code. Click save. Click OAuth. Click Update.
-
In Hubitat app, click Apps.
-
Click Load New App. Under User Apps (at the bottom).
-
Click webCoRe.
-
Click Next.
-
Enter a "Name" for the webCoRe instance. (I included "Hubitat" within the name to make sure it doesn't conflict with my ST install - don't know if needs to be unique.)
There's an option to (dis)allow collecting anonymized data (I don't know if the Hubitat port actually sends this data...?) Select whichever is your preference.
Enter a password. -
It will ask to select actuators and sensors, and devices by capability. Select all that you want WebCore to access for each the options. (You can change the selections later.)
-
Click Next.
-
Click Done.
That should be it, but let's make sure.
-
Click Hubitat WebCore.
-
Make sure the actuators and sensors saved properly (from the above step), by clicking Settings.
-
Click Available Devices.
-
Check if your selections show correctly, and if not, reselect them.
-
Click Done.
-
Open Dashboard in a new tab (eg right-click, Open link in new tab, or however).
Use as WebCore as normal and consider donating to the developers. (This is especially true for @Roguetech!)
If anything here is incomplete or incorrect, I will update - just tell me what I got wrong.
edit: I've had trouble getting WebCore working with these steps, and removed it and readded a couple times to get adding a piston to work. The "actuators and sensors" don't appear as available to WebCore. I'm not sure what the secret sauce was that finally worked for me. I think the trick was to follow the steps above, then open WebCore and login, then in Hubitat go into "Hubitat Storage" (which only appears after going into WebCore). When your devices are registered in Hubitat Storage, then they will appear in WebCore. I'll try to retest it and capture what's required (and what all I did that didn't actually help).
Credit for numbering to mpoole32.
6 Likes
Is there any technical barrier to creating a fork that would work on both ST and HE? Do the commands exist in both to get the system name to say If HT, then capability = button, else capability = pushableButton?
There isn't. I started off working on making the code flexible to run on both systems, however, owing to a new job and some other life changes, I am not able to find the time to work on this at the moment,
I hope to resume this project at some later point (unless someone else starts working toward this goal in the mean time.)
you have done some awesome work already ... thank you for that. i was thinking of taking this on but probably dont have the time i would need to get this done done. 
do you have a list of issues on github that community members could pick off one by one as they have time and submit a PR for each? that would help distribute the load and we could all help get this done.
thanks.
That's a great idea! 
I'll try to spend some time and break out the tasks coming weekend and then post it on the forum forum requesting for help.
Also, thank you for your kind words!
1 Like
I'm can't get Location Mode, weather or presence (using Life360) to work. Any suggestions on how to begin fixing any of these? Without any of these, my Hubitat system is pretty much a wasted Ethernet port.
I assume you mean using WebCoRE.
If so you might want to go to the webCoRE forum and ask for guidance or open a new thread on the Hubitat forum but include information of what you are actually doing.
Just saying you cannot get it work with no information makes it difficult for people to advise you.
2 Likes
So other people have been able to get Location Mode, weather and presence in WebCoRe on Hubitat to work?
Thanks. Knowing it's can work in the Hubitat port hopefully will help. I'll dig some more, and post on webcore.co if I can't figure it out.
Yes. I use webCoRE for all my automations.
1 Like
Brilliant!! Just when I thought I'd not get webCoRE again after moving over. Many thanks!!!
I am just moving over from ST to hubitat and I have installed Webcore. I created my first piston and when I saved it, this showed up in the log below the piston:
║Unable to update setting 'dev' from child app. Open child app 'Hall Light On' on the Hubitat apps page and click 'Done' for faster operation
What should I do about this?
do what it says, you go into the child device (click on the piston) and at the bottom on the page press done. think you have to do this each time the HUB is re booted @ajayjohnm will be able to tell you more and why its needed.
I was going to ask about it anyway @ajayjohnm is this something we will always need to do from now on?
At first I didn't see what you were talking about but then I figured it out. Thanks! Now if I could just get my zooz 4-in-1 sensor to react properly!
