Yes, I imported a whole number of Pistons via that method. Very easy.
1 Like
Thanks so much!!
So I posted this in another forum "WebCoRE vs Rule Machine" but thought I'd mention it here as well. A word of caution.....
I just encountered a major issue where my HE web interface was completely non-responsive after several clicks. Not sure what was going on I tried rebooting various times and nothing seemed to work. I even got a "Zigbee network offline" message at one point. Contacted support but while waiting decided to try and simplify my setup by removing WebCoRE. Manually powering off the HE, removing the usb stick and then booting up allowed me to regain normal access to the UI. I was then able to remove WebCoRE. I shutdown "gracefully" via the interface, added the stick back in and booted up. Everything started working and the interface was snappy again. Support got back in touch but had noticed that things seemed to be working from their end. Gave them the heads up on what I did.
My WebCoRE (v0.2-377-gb5cefd4) was running locally on a Raspberry PI3 - I had about 5 or so pistons with some basic logic, timers & triggers but nothing too weird as far as I know. It's possible I could have inadvertently created conflicting or "fatal embrace" pistons but not sure - I do have experience writing them under ST.
Have recreated most of them in RM now and things are working better. RM is quicker to respond but for me not as flexible - I really love the WebCoRE interface.
For now have disabled WebCoRE. 
Just an FYI - The only part of webCoRE that doesn’t run locally on your Hubitat hub, is the web configuration tool. All pistons run locally on your hub, You could turn off your RPi and your pistons would still run fine.
Yes that is my understanding as well.
The issue seems to be on the hub not the WC server - but I thought I'd mention my setup anyway just in case. I suspect the pistons I wrote caused a major slowdown when they ran on the hub. Most likely something I did but not sure. My HE WC Smart app version was "v0.3.108.20180906"
Also wanted to let everyone know how I managed to recover without resetting everything..
1 Like
Where did you come up with this URL? I'm trying to do the same but for some reason i can't find anywhere on how to find it.
EDIT:
I was able to find it. If anyone else happens on this thread and is looking for a clearer explanation on how to build the URL, here it is:
That same issue happened to me when I changed to using the new "Devices" selection instead of Sensors and Actuators. I've had WebCore running just fine on the current version for a few weeks, but as soon as I went in and messed with the "Devices" I started running into crashes with my hub whenever a WebCore rule ran.
I'm going to try and fix things the same way, just wondering if anyone else has tried changing to the "Devices" selection from the originally available options, and if that's caused issues.
That's interesting.. I was indeed using the devices section when the slowdown occurred but I don't think it was the primary reason not sure though.
In WC I was using a lot of triggers.. mixing triggers and normal comparisons and timers. I thought maybe that had something to do with it or I was created piston(s) that were in conflict with each other like a "fatal embrace" or some sort of race condition.
I only had like one or 2 global variables. I wonder if using virtual devices has anything to do with it? Seems like I started using virtual devices/groups a lot more just before the crash.
Is it possible that you deleted a device or removed a device from webCoRE that was included in a piston before deleting the piston? This is one situation where I could see big problems being created that the server implementation of webCoRE could react appropriately but our poor little server would just be completely unable to deal and recover.
1 Like
For me that is a possibility now that you mention it. Would not have done that at first though because I was ramping up and switching over devices from ST. Now that the migration is mostly complete and I'm in discover and play mode with HE - I certainly may have added/removed devices/groups etc without removing the piston...
Hmmmmm...
Having an issue parsing an HTTP get response. Anyone have any ideas? There's a thread on the webCoRE forum.
Anyone been able to parse HTTP responses in webCoRE yet?
I turned off all selections in the "Devices" section and upgraded to 1.16 and I don't have the 500 errors anymore with the Hub freezing. I'm almost certain using the "Devices" option is what caused the problem, but I can go figure it out for sure later when I can afford the downtime on the automations/ hub.
1 Like
If that's what it is - that's great to know! I wonder if it is also missing/removed devices still in pistons.
I made a little docker-compose project to download and build the hubitat patched webcore with SSL enabled. Just change the servername (2 places) in the docker-compose.yml, then docker-compose up -d.
https://github.com/bmcgair/webcore-docker/
Cheers
Is docker like a VM ?
1 Like
Can this be installed on an UnRaid server that has docker? If so, is there a direct installation link to install it?
Docker is the hypervisor like VMware or virtual box. Containers are the vms. It's a lot more modular than VMware.
Can this be used somehow on an Unraid server that has docker?
I'm not sure what unraid is, but I don't see why not. The idea of docker containerization is that containers will run anywhere that can run docker.
if you have both the docker and docker-compose commands on the box it should be good to go. Even just "docker" could be made to work.
UnRaid is a type of OS to create and run a Raid server. It has a GUI interface through a browser and part of the interface has a section that you can install docker containers through. It installs everything automatically. You don't need to use linux commands, etc. I think it is called a wrapper that is on the docker hub. I think you use linuxserver.io to build an isolated app container. I don't know enough about it to do it myself. Wondered if you would know?
