Domoticz

Open source Home Automation System
https://forum.domoticz.com/

Reacticz dashboard: no install, no hassle

https://forum.domoticz.com/viewtopic.php?t=14941

Page 6 of 9

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:11
by Snowtiger
blackdog65 wrote:Hi,
I have managed to get node-red and mqtt installed and running as well as a mqtt client in domoticz... so far so good.
If I clone reactictz directly into the domoticz www folder it cannot install as it is looking for package.json in the home folder. So do I install build etc in my home folder and then move the entire package to domoticz? I was going round in circles last night until very late... but still want to attack it and win today ;)
I think you need to fill the correct root directory in the package.json file - see the post above yours about building your own build, especially the part about the note

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:12
by NietGiftig
blackdog65 wrote:Hi,
If I clone reactictz directly into the domoticz www folder it cannot install as it is looking for package.json in the home folder.
Maybe you missed this part about installing React on your PC.
Necessary to build your own version of Reacticz
https://github.com/t0mg/reacticz/blob/m ... ng-testing
If you really read the guidelines here it's must be working
But cloning the complete git to the www dir is not good
After npm run build (a node.js command) the contents of the build directory must be copied to your www directory, or a subdirectory of the ww dir from domoticz

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:16
by ptitneo
By default Reacticz builds assuming it is hosted at the server root. Before you build Reacticz, you need to change the homepage property in the package.json. See the note in the build instructions here.

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:30
by blackdog65
Thanks guys, I had the package json correct but the where to put it all... wrong :oops:
The instructions ( and I have read them all) are ambiguous about..
a) Root folder or home folder
b) Move build folder... but rename it reacticz? Or into a new folder called reacticz?
Sorry if I appear stupid... very little sleep last night :roll:
Sean :D

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:41
by NietGiftig
blackdog65 wrote: Sorry if I appear stupid... very little sleep last night :roll:
Maybe have some sleep, and come back tomorow.
And tell us what you want.
If you want to run Recticz on your own server, you have to buld reacticz first.
After that it must be placed in a subdir from the www dir of domoticz
But now am I repeating myself, so I stop.
And ambiguous?
I'm a complete www noob, but it worked for me.

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:42
by ptitneo
Don't worry, I'm getting that a lot. Which is a little depressing since I created Reacticz to be a no-install thing, so I made the public server to spare the burden of installing it. But it seems everyone still wants to do that anyway :)

Anyway, I'd be really grateful if a good soul could make a wiki page with detailed step-by-step instructions and command lines for building and installing in domoticz's www folder! It seems I'm failing at making it clear myself.

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 11:58
by blackdog65
ptitneo wrote:Don't worry, I'm getting that a lot. Which is a little depressing since I created Reacticz to be a no-install thing, so I made the public server to spare the burden of installing it. But it seems everyone still wants to do that anyway :)

Anyway, I'd be really grateful if a good soul could make a wiki page with detailed step-by-step instructions and command lines for building and installing in domoticz's www folder! It seems I'm failing at making it clear myself.
Thanks,
I'm rebuilding it now and will see how I get on.
Once I get it all sorted I'll have a look at writing something for the wiki, maybe the domoticz wiki too. I probably missed a simple step, as we sometimes "can't see the wood for the trees". I'm quite busy re-building a new look domoticz.com at the moment, but with the unhelpful and sarcastic attitude of some users... I wonder is it worth it :roll:

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 12:05
by NietGiftig
ptitneo wrote:since I created Reacticz to be a no-install thing, so I made the public server to spare the burden of installing it. But it seems everyone still wants to do that anyway :)
A separate branch ot github, with Reacticz build for local Domoticz /www/reacticz/ use, would be nice
But then, the user must know how to use the git to copy the correct branch. :shock:

The wish to have it build local comes with the burden of having installing node.js, react etc.
On Windows?, Linux?, Mac?
On your desktop?, or on the raspberry?

Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 12:07
by Snowtiger
I have Nginx running on my Pi with the gh-pages branch cloned into the root folder - no hassle, no install ;) but this requires an extra webserver running when you have Domoticz available, I know - but install and running Nginx is not a big deal

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 06 February 2017 12:52
by ptitneo
NietGiftig wrote: A separate branch ot github, with Reacticz build for local Domoticz /www/reacticz/ use, would be nice
I agree, a dedicated branch with just the pre-built releases as zip packages would probably make it easier for those who want a local install but don't have node.

Re: Reacticz dashboard: no install, no hassle

Posted: Tuesday 07 February 2017 0:05
by felix63
I can not get Reacticz to work. Spend a couple of hours (it way past bedtime). Googled everything I could think of.

I have the correct version of mosquitto running

Code: Select all

$ mosquitto -v
1486420919: mosquitto version 1.4.10 (build date Thu, 25 Aug 2016 10:12:09 +0100) starting
however

Code: Select all

sudo mosquitto start
(or restart) don't work. The service isn't started. I checked with

Code: Select all

--sudo service --status-all
My config-file (/etc/mosquitto/mosquitto.conf) is
Spoiler: show

Code: Select all

# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /var/run/mosquitto.pid

persistence true
persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d
which refers to /etc/mosquitto/conf.d/ which has /etc/mosquitto/conf.d/websocket.conf
Spoiler: show

Code: Select all

# Standard Listener
listener 1883
protocol mqtt
#allow_anonymous false
#password_file /etc/mosquitto/passwords.txt

# Websockets Listener
listener 1884
#http_dir
#Set the protocol to accept for this listener. Can be mqtt (the default), or websockets.
protocol websockets
If I run mosquitto from the console with

Code: Select all

sudo mosquitto -c /etc/mosquitto/mosquitto.conf
and I check my ports I see:

Code: Select all

portscan is gestart…

Port Scanning host: 192.168.178.50

	 Open TCP Port: 	22     		ssh
	 Open TCP Port: 	443    		https
	 Open TCP Port: 	1880   		vsat-control
	 Open TCP Port: 	1883   		ibm-mqisdp
	 Open TCP Port: 	1884   		idmaps
	 Open TCP Port: 	2812   		atmtcp
	 Open TCP Port: 	6144   		statsci1-lm
	 Open TCP Port: 	8080   		http-alt
portscan is voltooid…
So MQTT seems to be running. In Domoticz I've created the hardware:

Code: Select all

19	Mosquitto	Ja	MQTT Client Gateway with LAN interface	192.168.178.50	1884	Niet actief
.

The server settings in Reacticz are:

Code: Select all

MQTT Broker URL: connected!
ws://192.168.178.50:1884

Domoticz server URL:
http://192.168.178.50:8080
The mosquitto log-file doesn't help.
Spoiler: show

Code: Select all

1486422160: mosquitto version 1.4.10 (build date Thu, 25 Aug 2016 10:12:09 +0100) starting
1486422160: Config loaded from /etc/mosquitto/mosquitto.conf.
1486422160: Opening ipv4 listen socket on port 1883.
1486422160: Opening ipv6 listen socket on port 1883.
1486422160: Opening websockets listen socket on port 1884.
1486422161: New client connected from 192.168.178.29 as mqttjs_7610b5c1 (c1, k60).
1486422161: Sending CONNACK to mqttjs_7610b5c1 (0, 0)
1486422161: Received SUBSCRIBE from mqttjs_7610b5c1
1486422161: 	domoticz/out (QoS 0)
1486422161: mqttjs_7610b5c1 0 domoticz/out
1486422161: Sending SUBACK to mqttjs_7610b5c1
1486422161: Received SUBSCRIBE from mqttjs_7610b5c1
1486422161: 	domoticz/out (QoS 0)
1486422161: mqttjs_7610b5c1 0 domoticz/out
1486422161: Sending SUBACK to mqttjs_7610b5c1
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32473, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32473)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32474, 'domoticz/in', ... (36 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32474)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32475, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32475)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32476, 'domoticz/in', ... (36 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32476)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32477, 'domoticz/in', ... (36 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32477)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32478, 'domoticz/in', ... (36 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32478)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32479, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32479)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32480, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32480)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32481, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32481)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32482, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32482)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32483, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32483)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32484, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32484)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32485, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32485)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32486, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32486)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32487, 'domoticz/in', ... (37 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32487)
1486422161: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32488, 'domoticz/in', ... (36 bytes))
1486422161: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32488)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32473)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32473)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32474)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32474)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32475)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32475)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32476)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32476)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32477)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32477)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32478)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32478)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32479)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32479)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32480)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32480)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32481)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32481)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32482)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32482)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32483)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32483)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32484)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32484)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32485)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32485)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32486)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32486)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32487)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32487)
1486422161: Received PUBREL from mqttjs_7610b5c1 (Mid: 32488)
1486422161: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32488)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32489, 'domoticz/in', ... (36 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32489)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32490, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32490)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32491, 'domoticz/in', ... (36 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32491)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32492, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32492)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32493, 'domoticz/in', ... (36 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32493)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32494, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32494)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32495, 'domoticz/in', ... (36 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32495)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32496, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32496)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32497, 'domoticz/in', ... (36 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32497)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32498, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32498)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32499, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32499)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32500, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32500)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32501, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32501)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32502, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32502)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32503, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32503)
1486422179: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32504, 'domoticz/in', ... (37 bytes))
1486422179: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32504)
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32505, 'domoticz/in', ... (37 bytes))
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32505)
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32506, 'domoticz/in', ... (37 bytes))
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32506)
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32507, 'domoticz/in', ... (37 bytes))
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32507)
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32508, 'domoticz/in', ... (37 bytes))
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32508)
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32509, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32510, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32511, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32512, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32513, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32514, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32515, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBLISH from mqttjs_7610b5c1 (d0, q2, r0, m32516, 'domoticz/in', ... (37 bytes))
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32489)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32489)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32490)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32509)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32490)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32491)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32510)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32491)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32492)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32511)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32492)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32493)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32512)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32493)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32494)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32513)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32494)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32495)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32514)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32495)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32496)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32515)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32496)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32497)
1486422180: Sending PUBREC to mqttjs_7610b5c1 (Mid: 32516)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32497)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32498)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32498)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32499)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32499)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32500)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32500)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32501)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32501)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32502)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32502)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32503)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32503)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32504)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32504)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32505)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32505)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32506)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32506)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32507)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32507)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32508)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32508)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32509)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32509)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32510)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32510)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32511)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32511)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32512)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32512)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32513)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32513)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32514)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32514)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32515)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32515)
1486422180: Received PUBREL from mqttjs_7610b5c1 (Mid: 32516)
1486422180: Sending PUBCOMP to mqttjs_7610b5c1 (Mid: 32516)
1486422190: mosquitto version 1.4.10 terminating
I have the following problems:
1- mosquitto doesn't start as a service they way it should
2- in the domoticz.log 1-2 times per minute it shows:

Code: Select all

2017-02-06 23:52:52.469 MQTT: Connecting to 192.168.178.50:1884
2017-02-06 23:52:52.671 Error: MQTT: disconnected, restarting (rc=7)
3- in Reacticz all the devices are shown as 'Offline?'

Sorry for the lengthy post. But does someone have any idea what I could try next?

Re: Reacticz dashboard: no install, no hassle

Posted: Tuesday 07 February 2017 0:18
by G3rard
You should connect Domoticz to MQTT port 1883 and not 1884.
Reactiz should be connected to the websocket, which is 1884, so that part is correct.
Not sure if that is the only problem, but maybe it is :)

Re: Reacticz dashboard: no install, no hassle

Posted: Tuesday 07 February 2017 22:12
by felix63
That sure helped with part of my problems! thanks

Re: Reacticz dashboard: no install, no hassle

Posted: Friday 10 February 2017 21:58
by ptitneo
Hi everyone, due to popular demand I've created a first release tag on github, you can now download a pre-built package that will work from your domoticz/www folder right out of the box :)

https://github.com/t0mg/reacticz/releases/tag/v0.1.8

Reacticz now supports many new sensors as well as domoticz/mqtt authentication, thanks to the efforts of G3rard and davidlb.
Cheers!

PS felix63 I hope you were able to fix your problems! I think so since you've created tickets on github :)

Re: Reacticz dashboard: no install, no hassle

Posted: Saturday 11 February 2017 19:35
by simonrg
Great work, Reacticz is a very nice and clean interface.

The local implementation is even cleaner and I thought may give me new possiblities.

I would like to be able to create a number of different very simple pages of buttons - ones for different times of day and different parts of the house, with just a few buttons displayed. So TV Room - just with the TV and light controls for that room, Bedtime - just with set alarm and switch of lights in different parts of the house.

My knowledge of web page details is scanty, so this may be either very easy to do by another route or just plain stupid.

I thought if I just made symbolic links to the reacticz directory on my Raspberry Pi -

Code: Select all

ln -s reacticz/ reacticz-tv
So I thought I would now have two different pages - http://domoticz-ip:8080/reacticz/ and http://domoticz-ip:8080/reacticz-tv/, which will show different sets of buttons, but this doesn't work as obviously the caching is done by ip not by directory so both directories display the same buttons.

Is there any easy way to do this? I hoped to have a series of home page buttons which took me to the few controls I need for different situations.

Thanks, Simon

Re: Reacticz dashboard: no install, no hassle

Posted: Saturday 11 February 2017 22:30
by ptitneo
Interesting :) Your symlink idea is pretty clever. Unfortunately reacticz uses localStorage, which is unique for a given domain and protocol, regardless of the path.

I knew that eventually the need would come for several configurations on the same device. I have a simple idea that I need to try. In the mean time feel free to file an issue in github!

Cheers,

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 13 February 2017 14:12
by ptitneo
Following up on this: I've added an experimental way to have multiple dashboards on the same device/browser. It's documented on the wiki.
The feature is available on the public server.

Cheers!

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 13 February 2017 21:15
by rickwilleme
First of all: thanks ptitneo for this amazing piece of software.
For me (well, maybe more for my girlfriend :lol: ) this is really a game changer!!

During the config, I do however encounter a small issue.
We have 2 blinds (left and right). One is being recognized, but not responding. The other mentions "Offline ?"

Any way to troubleshoot this issue?

Help is very appreciated!

Regards,
Rick

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 13 February 2017 22:14
by rickwilleme
In addition to the statement above, I actually notice that more switches and groups are not responding.
My gut feeling says that something got messed up in the config, but 'starting all over' doesn't seem to fix it..

Re: Reacticz dashboard: no install, no hassle

Posted: Monday 13 February 2017 22:48
by ptitneo
Sounds like something is wrong with the config indeed. Are you using the public server or a local install? And in the server settings do you get the green "connected!" message on both Domoticz and MQTT?
All times are UTC+01:00
Page 6 of 9

Powered by phpBB® Forum Software © phpBB Limited