Sorry, my fault.
sudo service apache2 stop
looks like it did something that time 
Edit: @Royski still says no permission
if i do
cd /var/www/
is there a delete command i can do to delete the file webcore
1 Like
think this is one of my issues as mine says pwd
rm not remove maybe.
2 Likes
May be worth logging in a root, and removing that way?
the ` on the PWD is top left of the keyboard (UK that is) tilled character and originally I thought this was how I received SQL from colleagues in the US, so changed mine (stupidly) to '
This is what broke mine, and I did the above after reading some others having just a webcore "file" rather than directory in /var/www once I corrected this, all went well.
yes getting somewhere @bobbles rm worked
1 Like
yes this took me a while to work out and find too 
1 Like
Now try the URL and I'm 
for you 
1 Like
Yay. I'm not sure I did much apart from help you to 'poke and hope'.
Glad you got it working though.
Have fun.
1 Like
Great!! Only took me three times 
1 Like
Best way too learn in my opinion! But you do need at least a small stick to to start poking
1 Like
So it's one of the other in reference to the dashboard, if you have you pi set up as the server you can't use dashboard.co ? Have you guys set up a VPN to be able to remote in and edit if you have too?
Not as yet, but you can. But then I have VNC on my VM image to connect if needed.
I've pushed an update to github for the following changes:
- Update code to latest from ady624 (removal of contact support)
- Hubitat Saftey Monitor support for dashboard and pistons
- Added $currentEventDescription and $previousEventDescription variables
- Added firmware version display support to dashboard if >= 1.1.2.112
The $hsmStatus variable has also changed from showing a display status to the raw value, so if any previous pistons used that be sure to update them.
Note there is also support for another event: "Hubitat Safety Monitor Event" that is disabled by default. It will listen to apps sending events (using hsmSetArm) to Hubitat Saftety Monitor but not done through HSM or buttons/switches configured to do so.
For instance if you cancel an alert by using sendEvent(name: "hsmSetArm", value: "cancelAlerts") it will pick it up in a piston, but not if you hit the Cancel Alerts button using a device configured in HSM or through the app page.
If that's something your interested in you can uncomment line 3120 in webCore.groovy and it will show up as a new virtual device just note the limitations above.
@bravenel maybe in the future HSM can send these events to let other apps know when things like cancelled alerts happen within HSM
//alarmSystemEvent: [ n: 'Hubitat Safety Monitor event',t: 'enum', o: getAlarmSystemStatusActions(), m: true],
If you are running a local instance don't forget to run these commands:
cd
cd webCoRE/
git pull
Also, if you haven't switched from @ajayjohnm's repo to mine, run these before doing the above:
Here is an example piston for the HSM:
2 Likes
That was my believe as well. As i have over 20 pistons, really don't want to chance it and would like to be pretty certain it won't break my pistons. @jp0550 - some guidance on this matter?
Just wanted to find out - I have a second Rpi and have installed webCore there. Will there be any problems if i just change on the HE portal the custom webcore instance url to the new Rpi IP address? Will it disrupt anything?
No disruptions at all. The webcore UI is just a front end for editing pistons.
1 Like
This will be in the next release (1.1.3).
1 Like
Idpaterson pushed another update today for some UI changes. I've merged the changes into my repo. Feel free to update if you want to get rid of the UI out of date message or want the latest.
4 Likes
Changed the IP and all is working smoothly. Thanks for verifying that!
1 Like
