Domoticz

gielie wrote: ↑Tuesday 16 July 2019 23:07 I tried v3 and iT looks nice. I have some trouble now with some scripts that won’t run anymore, how do I uninstall v3?

#First go to your dashticz_v3 folder
cd ~/dev/dashticz_v3

#Stop the Docker instance of Dashticz (assuming you used the automatic installation script)
make stop

#Remove the dashticz_v3 folder
cd ..
rm -rf dashticz_v3

#remove the docker images etc. To remove see  https://www.digitalocean.com/community/tutorials/how-to-remove-docker-images-containers-and-volumes:

docker system prune

Lokonli wrote: ↑Thursday 18 July 2019 17:29

gielie wrote: ↑Tuesday 16 July 2019 23:07 I tried v3 and iT looks nice. I have some trouble now with some scripts that won’t run anymore, how do I uninstall v3?

Which scripts won't run?

To uninstall:

Code: Select all

#First go to your dashticz_v3 folder
cd ~/dev/dashticz_v3

#Stop the Docker instance of Dashticz (assuming you used the automatic installation script)
make stop

#Remove the dashticz_v3 folder
cd ..
rm -rf dashticz_v3

#remove the docker images etc. To remove see  https://www.digitalocean.com/community/tutorials/how-to-remove-docker-images-containers-and-volumes:

docker system prune

After that you can deinstall Docker.

. <(wget -qO - https://raw.githubusercontent.com/dashticzv3/dashticz_v3/beta/scripts/dashticz_install.sh )
This is the installation script for Dashticz V3
The script will create a folder for Dashticz v3 in the following location:
/home/pi/dashticz3

Enter the folder name [dashticz_v3]: 

Dashticz will be installed in
dashticz_v3


Dashticz has a master branch (=stable) and a beta branch (=most up-to-date)
Which branch to install? [master]: beta

Now cloning the Dashticz repository https://github.com/dashticzv3/dashticz_v3

Cloning into 'dashticz_v3'...
remote: Enumerating objects: 7076, done.
remote: Counting objects: 100% (7076/7076), done.
remote: Compressing objects: 100% (2383/2383), done.
remote: Total 7076 (delta 4654), reused 7057 (delta 4636), pack-reused 0
Receiving objects: 100% (7076/7076), 29.20 MiB | 5.23 MiB/s, done.
Resolving deltas: 100% (4654/4654), done.

Configuring Dashticz.

What is the IP:port address of your Domoticz server? (example: 192.168.178.18:8080): 192.168.1.133:6060

Finding a free port for Dashticz
Port 8082 is NOT in use

Setting up Dashticz on port 8082


Let's install docker first
wget -qO- https://get.docker.com/ | sh	
# Executing docker install script, commit: 6bf300318ebaab958c4adc341a8c7bb9f3a54a1a
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ [ -n  ]
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "UTF-8",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
+ sudo -E sh -c docker version
Client: Docker Engine - Community
 Version:           19.03.0
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        aeac949
 Built:             Wed Jul 17 18:25:36 2019
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.0
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       aeac949
  Built:            Wed Jul 17 18:19:37 2019
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:

  sudo usermod -aG docker pi

Remember that you will have to log out and back in for this to take effect!

WARNING: Adding a user to the "docker" group will grant the ability to run
         containers which can be used to obtain root privileges on the
         docker host.
         Refer to https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
         for more information.
Check for git
Installed...
sudo docker build -t dtv3 .
Sending build context to Docker daemon  66.48MB
Step 1/3 : FROM php:apache
 ---> c6fa8e4bcb26
Step 2/3 : USER root
 ---> Using cache
 ---> 4c5ce91b0eaf
Step 3/3 : SHELL ["/bin/bash", "-c"]
 ---> Using cache
 ---> 8c66cd348691
Successfully built 8c66cd348691
Successfully tagged dtv3:latest
sudo docker run --name dtv3 -d -p 8082:80 --mount type=bind,source="/home/pi/dashticz3/dashticz_v3",target=/var/www/html dtv3
docker: Error response from daemon: Conflict. The container name "/dtv3" is already in use by container "f2f46cc0b2a11a65bea219ed56681df09a16a3ffb5ab272e58033491f4e2ebcd". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
Makefile:38: recipe for target 'start' failed
make: *** [start] Error 125

Trying Domoticz IP...OK!
All done

gielie wrote: ↑Thursday 25 July 2019 14:36

Lokonli wrote: ↑Thursday 18 July 2019 17:29

gielie wrote: ↑Tuesday 16 July 2019 23:07 I tried v3 and iT looks nice. I have some trouble now with some scripts that won’t run anymore, how do I uninstall v3?

Which scripts won't run?

To uninstall:

Code: Select all

#First go to your dashticz_v3 folder
cd ~/dev/dashticz_v3

#Stop the Docker instance of Dashticz (assuming you used the automatic installation script)
make stop

#Remove the dashticz_v3 folder
cd ..
rm -rf dashticz_v3

#remove the docker images etc. To remove see  https://www.digitalocean.com/community/tutorials/how-to-remove-docker-images-containers-and-volumes:

docker system prune

After that you can deinstall Docker.

I get a lot of errors during installation and afterworhs my normal dashticz isn't loading anymore.

Code: Select all

. <(wget -qO - https://raw.githubusercontent.com/dashticzv3/dashticz_v3/beta/scripts/dashticz_install.sh )
This is the installation script for Dashticz V3
The script will create a folder for Dashticz v3 in the following location:
/home/pi/dashticz3

Enter the folder name [dashticz_v3]: 

Dashticz will be installed in
dashticz_v3


Dashticz has a master branch (=stable) and a beta branch (=most up-to-date)
Which branch to install? [master]: beta

Now cloning the Dashticz repository https://github.com/dashticzv3/dashticz_v3

Cloning into 'dashticz_v3'...
remote: Enumerating objects: 7076, done.
remote: Counting objects: 100% (7076/7076), done.
remote: Compressing objects: 100% (2383/2383), done.
remote: Total 7076 (delta 4654), reused 7057 (delta 4636), pack-reused 0
Receiving objects: 100% (7076/7076), 29.20 MiB | 5.23 MiB/s, done.
Resolving deltas: 100% (4654/4654), done.

Configuring Dashticz.

What is the IP:port address of your Domoticz server? (example: 192.168.178.18:8080): 192.168.1.133:6060

Finding a free port for Dashticz
Port 8082 is NOT in use

Setting up Dashticz on port 8082


Let's install docker first
wget -qO- https://get.docker.com/ | sh	
# Executing docker install script, commit: 6bf300318ebaab958c4adc341a8c7bb9f3a54a1a
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ [ -n  ]
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "UTF-8",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
+ sudo -E sh -c docker version
Client: Docker Engine - Community
 Version:           19.03.0
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        aeac949
 Built:             Wed Jul 17 18:25:36 2019
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.0
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       aeac949
  Built:            Wed Jul 17 18:19:37 2019
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:

  sudo usermod -aG docker pi

Remember that you will have to log out and back in for this to take effect!

WARNING: Adding a user to the "docker" group will grant the ability to run
         containers which can be used to obtain root privileges on the
         docker host.
         Refer to https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
         for more information.
Check for git
Installed...
sudo docker build -t dtv3 .
Sending build context to Docker daemon  66.48MB
Step 1/3 : FROM php:apache
 ---> c6fa8e4bcb26
Step 2/3 : USER root
 ---> Using cache
 ---> 4c5ce91b0eaf
Step 3/3 : SHELL ["/bin/bash", "-c"]
 ---> Using cache
 ---> 8c66cd348691
Successfully built 8c66cd348691
Successfully tagged dtv3:latest
sudo docker run --name dtv3 -d -p 8082:80 --mount type=bind,source="/home/pi/dashticz3/dashticz_v3",target=/var/www/html dtv3
docker: Error response from daemon: Conflict. The container name "/dtv3" is already in use by container "f2f46cc0b2a11a65bea219ed56681df09a16a3ffb5ab272e58033491f4e2ebcd". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
Makefile:38: recipe for target 'start' failed
make: *** [start] Error 125

Trying Domoticz IP...OK!
All done

i tried several times on different systems with no luck, any idea?

cd /home/pi/dashticz3/dashticz_v3
make stop
make start

Lokonli wrote: ↑Thursday 27 June 2019 7:48

jake wrote: ↑Wednesday 26 June 2019 23:34 I did a 'make update' and now the garbage is loading alright. Thankf for fixing!

I noticed something else (very minor issue):
Because I had V3 setup 'manually' and via Docker, I can load them both in different tabs. I skipped between them and found something 'moving' in the calendar. Finally I saw that in the docker version of dashticz V3 the 'all day' events have a 02:00 time after the date, where the normal version doesn't have that.
Again, equal config file, so that doesn't explain.

Yesterday I indeed released beta 3.0.1. Thanks for confirming that your garbage issue is solved.

The 02:00 time issue sounds like an incorrect timezone setting, probably inside the Docker container. I'm afraid I don't have the time to look into this in the coming 3 weeks (holiday). I'll create an issue on Github. Maybe someone else is willing to pick this up.

kevinvantuyl wrote: ↑Friday 25 October 2019 11:38 Works fine for now on a rpi 3b+.

dstewart275 wrote: ↑Monday 23 December 2019 14:38 Hello - Can someone help me out?
I've a bit of experience with Domoticz and no problems with that. I've just tried to install Dashticz on the same PI and I simply can't make it work. The automatic installer runs fine and at the end I get the message to go to 192.168.1.96:8082 and another 172.x.x.x address but they don't land anywhere. If I go to 192.168.1.1:80 I get the apache holding page and at 192.168.1.1/dashticz/ i'll get an Dashticz error page. The CONFIG.js file is correct as you'd expect.
I'm running Raspbian Buster on a Pi1 Model B.
Any advice appreciated... Thanks Duncan

Lokonli wrote: ↑Monday 23 December 2019 16:06 What is the IP address of your pi? The installation script thinks it's running on 192.168.1.96...

Which error is reported if you go to 192.168.1.1/dashticz/ ?

Can you post your CONFIG.js here?

dstewart275 wrote: ↑Monday 23 December 2019 16:30

Lokonli wrote: ↑Monday 23 December 2019 16:06 What is the IP address of your pi? The installation script thinks it's running on 192.168.1.96...

Which error is reported if you go to 192.168.1.1/dashticz/ ?

Can you post your CONFIG.js here?

Thanks - my pi is 192.168.1.96 and I can get to Domoticz on 192.168.1.96:8080 just fine.
I've made a mistake in the previous post - The page I land on at 192.168.1.96/dashticz/ just says "ERROR - For more information visit Dashticz V3 Documentation"... The 192.168.1.1 reference should be ignored.

Thanks for helping!

Lokonli wrote: ↑Monday 23 December 2019 16:57 The 192.1168.1.96 indeed makes more sense ...

If you followed the automatic installation script you should have a Docker image running on port 8082.
Maybe better to test that first.

What do you see if you open 192.168.1.96:8082?

dstewart275 wrote: ↑Monday 23 December 2019 17:37

Lokonli wrote: ↑Monday 23 December 2019 16:57 The 192.1168.1.96 indeed makes more sense ...

If you followed the automatic installation script you should have a Docker image running on port 8082.
Maybe better to test that first.

What do you see if you open 192.168.1.96:8082?

That's what I was expecting too - Docker seems to be running (and I presume it is generating the error page mentioned on 192.168.1.96/dashticz
However if i navigate to 192.168.1.96:8082 on chrome I get
This site can’t be reached
192.168.1.96 refused to connect.
Search Google for 192 168 8082
ERR_CONNECTION_REFUSED

Does that help?

	make stop
	make start

Lokonli wrote: ↑Monday 23 December 2019 17:46 Then apparently the Docker image is not running correctly, at least not on port 8082.

Just to be sure, can you type the following in the Dashticz folder:

Code: Select all

	make stop
	make start

It stops the current Dashticz container, and restarts it again. It takes approx 1 minute. After start it reports the ip-adres:port.

The error page on 192.168.1.96/dashticz is not generated by the Docker container, but probably by some left overs from a previous manual install?

pi@raspberrypi:~ $ cd dashticz_v3
pi@raspberrypi:~/dashticz_v3 $ make stop
sudo docker stop dtv3
dtv3
sudo docker rm dtv3
dtv3
pi@raspberrypi:~/dashticz_v3 $ make start
Check for git
Installed...
sudo docker build -t dtv3 .
Sending build context to Docker daemon   66.8MB
Step 1/3 : FROM php:apache
 ---> c2dbfc2dd7fc
Step 2/3 : USER root
 ---> Using cache
 ---> f1f10f88a333
Step 3/3 : SHELL ["/bin/bash", "-c"]
 ---> Using cache
 ---> fd4d3dcf868d
Successfully built fd4d3dcf868d
Successfully tagged dtv3:latest
sudo docker run --name dtv3 -d -p 8082:80 --mount type=bind,source="/home/pi/dashticz_v3",target=/var/www/html dtv3
8505117725c350dc5a76a41b2c60445c110e6612c01d0e3903f8a88382e3b2bd
Dashticz is running at:
http://192.168.1.96:8082
http://172.17.0.1:8082