I tried a totally different piston and same thing.
Copy line 45 and past to 57.
The paste fails but I can add a condition and task maually which I couldn't on the other example.
Before
After
@nh.schottfam, Having some issues with graphs. I had not created a graph for a while but last week I modified an existing line graph to track humidity. After adding the additional sensor I went to the configure graph page. The sensor section was added but it shows the plot option, line options, etc. twice. Also I could not change the line color. If I select a color it just kind of blanks out.
I thought maybe it was just that graph, due to adding another sensor to an existing graph. Today I tried to modify the line color on another existing graph and I see the same thing.
Also if I change the line color and the selector greys out the graph will not display until I open it back up and then the colors are set to black. If I save it again without changing anything the graph will again display with black lines for the graph line I tried to change.
Here is the graph I tried to change line color on. One sensor tracking temp and humidity.
The 2nd screenshot shows the line color option when I start. In the next screenshot I tried to change the color to red, it is greyed out. Now the graph will not build, see screenshot 4, until I reopen and re-save without changing anything and the line color will be back at black.
Last screenshot is the log for the graph that will not build.
Hey guys. I been away for awhile, because everything has been working great. I am trying to make some adjustments, but cant get to my dashboard. It just never gets past loading.
I read thru, and dont see any changes, am i missing something here?
Try clearing your browser cache or using incognito mode.
I've noticed recently (within the past few weeks) that after saving a piston and "Finishing up..." is displayed, the editor doesn't drop me back into the main area that shows all of the pistons. I have to click on "cancel" or "save" multiple times get that to happen.
I suggest for both of these:
1 Like
Hi,
I'm trying to host my own local WebCoRE server on a Synology DS220+. I'm running into an infinite URL rewriting loop, where it keeps redirecting me when I try to access the site. Has anybody been able to get this running on a Synology?
Interesting. Could you tell me the benefits (assuming you get it sorted 
), and where I could find more info? A quick google didn't find much??
I had it working on a different brand's NAS, then I upgraded to a Synology and I can't get it working on that. It was really easy on the other one...
For all those who want to host a WebCoRE server on Synology, I finally got it working. Here's how to do it:
- Install Web Station and Apache 2.4.
- Clone the hubitat-patches branch of the WebCoRE github repository underneath the /web folder.
- Execute
sudo -R chgrp http webCoREandsudo -R chown http webCoRE. - Set up a virtual host using Apache 2.4 as the backend. Point its document root at /web/webCoRE/dashboard.
- Log out all browsers from the dashboard.
- Re-register the browser and log back in.
- Do a hard reload and dump cache.
- If the pistons don't display properly, log out and repeat steps 5 and 6 until it works. (This did it for me... I'm not sure when it started working)
4 Likes
Hello, I am having this exact same issue. Can you share what you changed line 4 in index.html to?
TIA!
Here you go. I think it was just a forward slash by default.
I normaly don't have the logs turned on in WC but I happened to be tracing the failing Speak command where the volume value doesn't work.
I found scores of these lines in the logs every night now.
I don't use most of the commands the Warns point to except the Blink drivers MotionDetection.
Maybe these are from the @snell driver?
Here is about 1/3 of the Warns:
app:122022-12-17 22:42:22.469warnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.467warnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.431warnStrange command toggleInputSource with commands [n:toggleInputSource, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.429warnStrange command showMessage with commands [n:showMessage, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.383warnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.381warnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.379warnStrange command toggleInputSource with commands [n:toggleInputSource, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.377warnStrange command showMessage with commands [n:showMessage, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.037warnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.035warnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.033warnStrange command MotionDetectionEnable with commands [n:MotionDetectionEnable, p:[null], cm:true] has nulls
app:122022-12-17 22:42:22.031warnStrange command MotionDetectionDisable with commands [n:MotionDetectionDisable, p:[null], cm:true] has nulls
The SystemArm/SystemDisarm and MotionDetectionEnable/MotionDetectionDisable are from my Blink drivers, as was brought up in another thread.
Apparently they are "benign" because I am using the parameter area with the commands to be able to put descriptions on the device's page, but no actual parameters are being used. I do not have commands for "showMessage" or those "toggle" ones though, so those must be from other drivers.
thanks. Certainly, sound, picture and input aren't yours.
Logs are off now so I guess what I don't know can't hurt me 
Well my logs are off but I'm getting hundreds of these daily. Ever since the last WC update a few days ago possibly? Never seen this action in the many years of running WC.
Can I downgrade WC to check and see if this is the issue? I'm using HPM so I would need the old source link.
@nh.schottfam
app:122022-12-20 08:56:16.583warnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.458warnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.456warnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.454warnStrange command toggleInputSource with commands [n:toggleInputSource, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.451warnStrange command showMessage with commands [n:showMessage, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.406warnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.404warnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.402warnStrange command toggleInputSource with commands [n:toggleInputSource, p:[null], cm:true] has nulls
app:122022-12-20 08:56:15.401warnStrange command showMessage with commands [n:showMessage, p:[null], cm:true] has nulls
ok, I push an update to allow quiet this down.
Update pushed out that should allow quieting of logs (controlled by debug level logging)
Also updates IDE modules for how custom device commands and parameters are handled
The IDE changes are on staging.webcore.co or in the repo
1 Like
I have just read the announcement webCoRE: A beautiful story continues beyond December 31st 2022 and have a few questions. #1: will development stop on the custom app we've been using all these years? #2: And will we loose access to the groovy source code like all the built in apps on the Hubitat hub? #3: Is Hubitat assuming control over dashboard.webcore.co? #4: Will we still have the ability to run the web interface locally?
IMHO Having webCoRE separate from the hub has given it more stability in that webCoRE is fully developed and changes infrequently. No disrespect to the Hubitat team, but it seems with every release things break, especially with Rule Machine. It would not be a good thing if that started to happen to webCoRE
3 Likes
No, the ongoing maintenance will continue to be in the hands of our community, especially @nh.schottfam and @ipaterson who have done a fantastic work to continue what Adrian has started in 2016. Any updates and bug fixes to the source code will come with the platform releases.
No, the source code will remain open.
We will be hosting the cloud infrastructure so that Adrian doesn't have to pay for the thousands of active users from his own pocket.
Nothing changes.
13 Likes
