Open source Home Automation System
https://forum.domoticz.com/
Hello,DRuw wrote:Hi all,
I have some issues with getting my domoticz correctly in Imperihome..
for some reason, all items go to a folter called weather, also switches etc.
Any Idea how to fix this?
Well it says there is already a pid file meaning a process running, and second line says that the port 5001 is already in use, so you need to kill the "starman master" process manually before starting a new one.thorbj wrote:Hi, I'm trying to set up MyDomoAtHome on my Raspberry Pi running Domoticz.
After setup, when I try to access the devices list, I det a 502 Bad Gateway error. I notice that the MyDomoAtHome.sh service crashes immideately after I start it.
Code: Select all
sudo /usr/bin/plackup -E production -s Starman --workers=4 -p 5001 -a /home/pi/domoticz/MyDomoAtHome/bin/app.pl --pid /tmp/mydomoathome.pid Pid_file "/tmp/mydomoathome.pid" already exists. Overwriting! 2015/09/24-13:31:37 Can't connect to TCP port 5001 on 0.0.0.0 [Adressen er allerede i bruk]
the update-mdah script is here to manage auto-upgrade, it stops, update libs and update source code before restarting the service.ntougait wrote:Hi,
I had previous version of MyDomoAtHome working fine. Decided to update so i reinstalled following the wiki.
Great, now it seems I get te service to stay running at least. But I still get 502 Bad Gateway when trying to access http://ip:5001/devicesepierre wrote:Well it says there is already a pid file meaning a process running, and second line says that the port 5001 is already in use, so you need to kill the "starman master" process manually before starting a new one.
what does this gives to you:thorbj wrote:Great, now it seems I get te service to stay running at least. But I still get 502 Bad Gateway when trying to access http://ip:5001/devicesepierre wrote:Well it says there is already a pid file meaning a process running, and second line says that the port 5001 is already in use, so you need to kill the "starman master" process manually before starting a new one.
I've followed the wiki guide, and set up remote access. Where do I start to look for errors?
Code: Select all
lsof -i tcp:5001epierre wrote:what does this gives to you:
I guess something else is already on the listening port for this is more an apache/nginx answer than a gateway one...Code: Select all
lsof -i tcp:5001
Code: Select all
pi@DomoCore ~ $ sudo lsof -i tcp:5001
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nginx 2146 root 10u IPv4 7382 0t0 TCP *:5001 (LISTEN)
nginx 2147 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN)
nginx 2148 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN)
nginx 2149 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN)
nginx 2150 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN)
pi@DomoCore ~ $
ok so in the config.yml modify port 5001 to 3001, this is the port you will use for the gateway.thorbj wrote:epierre wrote:what does this gives to you:
I guess something else is already on the listening port for this is more an apache/nginx answer than a gateway one...Code: Select all
lsof -i tcp:5001Yeah, there seems to be more listening to port 5001. How can I find out what? I'm pretty fresh at this...Code: Select all
pi@DomoCore ~ $ sudo lsof -i tcp:5001 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME nginx 2146 root 10u IPv4 7382 0t0 TCP *:5001 (LISTEN) nginx 2147 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN) nginx 2148 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN) nginx 2149 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN) nginx 2150 www-data 10u IPv4 7382 0t0 TCP *:5001 (LISTEN) pi@DomoCore ~ $
Sorry I meant MyDomoAtHome.sh and start2.sh please replace "-p 5001" by "-p 3001", and also edit /etc/init.d/MyDomoAtHome.sh and do the same.thorbj wrote:Ok, so now I changed port to 3001 in MyDomoAtHome.sh, and in nginx config. I didn't find port in config.yml.
Still I get bad gateway.
Code: Select all
access_log off;
add_header Cache-Control public;
server_tokens off;
server {
include /etc/nginx/proxy_params;
listen 443 ssl;
keepalive_timeout 70;
server_name localhost ++;
ssl on;
ssl_certificate /etc/ssl/ca/server.crt;
ssl_certificate_key /etc/ssl/ca/server.key;
add_header X-Frame-Options SAMEORIGIN;
location / {
proxy_pass http://localhost:8080/; access_log /var/log/nginx/domoticz.access.log;
error_log /var/log/nginx/domoticz.error.log; }
}
server {
include /etc/nginx/proxy_params;
listen 80;
keepalive_timeout 70;
server_name localhost ++;
add_header X-Frame-Options SAMEORIGIN;
location / {
proxy_pass http://localhost:8080/;
access_log /var/log/nginx/domoticz.access.log;
error_log /var/log/nginx/domoticz.error.log;
}
}
server {
include /etc/nginx/proxy_params;
listen 3001;
keepalive_timeout 70;
server_name localhost ++;
add_header X-Frame-Options SAMEORIGIN;
location / {
proxy_pass http://10.10.10.127:3001/;
auth_basic "Access Restricted";
auth_basic_user_file "/etc/nginx/.htpasswd";
access_log /var/log/nginx/domoticz.access.log;
error_log /var/log/nginx/domoticz.error.log;
}
}
ok this is what I thought.thorbj wrote:Here is my nginx config:Code: Select all
access_log off; add_header Cache-Control public; server_tokens off; server { include /etc/nginx/proxy_params; listen 443 ssl; keepalive_timeout 70; server_name localhost ++; ssl on; ssl_certificate /etc/ssl/ca/server.crt; ssl_certificate_key /etc/ssl/ca/server.key; add_header X-Frame-Options SAMEORIGIN; location / { proxy_pass http://localhost:8080/; access_log /var/log/nginx/domoticz.access.log; error_log /var/log/nginx/domoticz.error.log; } location /iss { proxy_pass http://10.10.10.127:3001/; auth_basic "Access Restricted"; auth_basic_user_file "/etc/nginx/.htpasswd"; error_log /var/log/nginx/domoticz.error.log; } } }
Yeah and that looks like the thing thats not working.epierre wrote:Hello,DRuw wrote:Hi all,
I have some issues with getting my domoticz correctly in Imperihome..
for some reason, all items go to a folter called weather, also switches etc.
Any Idea how to fix this?
can you explain a little bit more your issue ? there is a mapping from Domoticz so that items go to the same forlder as domoticz.
@epiere Do you know the answer?Bikey wrote:Not all my switches appear in the ImperiHome App for iOS. I have 30 switches in the "Switches" tab, but I do have more then 50 (real switches, remote-buttons, and virtual) switches.
They are received by the App, because I can add them in a Dashboard page, so it seems to be because of the limitation on the number of switches in a single tab-page.
So the question is: why can't I see my rooms as pages in ImperiHome? Because if they are divided in rooms then I would not need to have 1 page "switches" with all my switches.
Also I have to empty tabs: "Utility" and "Volumio" which I would like to disappear.
@Bikey the answer is hard work and more hard work...Bikey wrote:@epierre Do you know the answer?Bikey wrote: Also I have to empty tabs: "Utility" and "Volumio" which I would like to disappear.
Thanks, I have tried, but I get the following error when trying this (what does it do?):epierre wrote: @Bikey the answer is hard work and more hard work...
There is a version for testing, please use start2-2.sh and report any problems encountered.
Code: Select all
pi@raspberrypi ~/domoticz/MyDomoAtHome $ sudo ./start2-2.sh
Error while loading bin/app2.pl: Can't locate Dancer2.pm in @INC (@INC contains: /home/pi/domoticz/MyDomoAtHome/bin/../lib /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at /home/pi/domoticz/MyDomoAtHome/bin/../lib/Domo2.pm line 6.
BEGIN failed--compilation aborted at /home/pi/domoticz/MyDomoAtHome/bin/../lib/Domo2.pm line 6.
Compilation failed in require at bin/app2.pl line 7.
BEGIN failed--compilation aborted at bin/app2.pl line 7.I added this, try manually (here I tested ok on a PI B:Bikey wrote:I did, and tried again but get the same results.
curl -L http://cpanmin.us | perl - --sudo Dancer2