Can not access to homgear

English Forums Installation
#1

Hi, I am making new instalation on hassio.
When I try to access to homegear (http://ipaddr:2001) site redicted me to this:

Zajeta%20slika
Zajeta slika.PNG1413Ă—459 18.2 KB

Is this know problem?

#2

Hi @blazkom,

could you please change the environment in /var/lib/homegear/admin-ui/.env from APP_ENV=prod to APP_ENV=dev? After that, please reload the page and post the screenshot of the shown error.

– Micha

1 Like
#3

[quote=“Micha, post:2, topic:2978, full:true”]
Hi @blazkom,

could you please change the environment in /var/lib/homegear/admin-ui/.env from APP_ENV=prod to APP_ENV=dev ? After that, please reload the page and post the screenshot of the shown error.

– Micha
[/quote]Zajeta%20slika

Hi, I do not have this folder in my system.

#4

Hi @blazkom,

could you please look for adminUiPath in your /etc/homegear/main.conf? That’s the path you’ll find the .env-file.

– Micha

#5

Hi, sorry for late anserw.

I have only one Homegear folder and this is: config/homegear

In /config/homegear i have file main.conf

there i have change debugLevel = 5

This is reply that i get in hassio plugin site

07/07/19 12:33:36.226 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementCreateCa
(Array length=1)
[
  (Array length=1)
  [
    (Boolean) 0
  ]
]
07/07/19 12:33:36.226 IPC Server: Info: Client 1 successfully registered RPC method "managementCreateCa" (this method is registered by 2 client(s)).
07/07/19 12:33:36.226 IPC Server: Response: 
(void)
07/07/19 12:33:36.227 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementCreateCert
(Array length=1)
[
  (Array length=2)
  [
    (Struct length=0)
    {
    }
    (String) 
  ]
]
07/07/19 12:33:36.228 IPC Server: Info: Client 1 successfully registered RPC method "managementCreateCert" (this method is registered by 2 client(s)).
07/07/19 12:33:36.229 IPC Server: Response: 
(void)
07/07/19 12:33:36.229 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementDeleteCert
(Array length=1)
[
  (Array length=2)
  [
    (Struct length=0)
    {
    }
    (String) 
  ]
]
07/07/19 12:33:36.230 IPC Server: Info: Client 1 successfully registered RPC method "managementDeleteCert" (this method is registered by 2 client(s)).
07/07/19 12:33:36.230 IPC Server: Response: 
(void)
07/07/19 12:33:36.231 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementGetNetworkConfiguration
(Array length=1)
[
  (Array length=1)
  [
    (Struct length=0)
    {
    }
  ]
]
07/07/19 12:33:36.232 IPC Server: Info: Client 1 successfully registered RPC method "managementGetNetworkConfiguration" (this method is registered by 2 client(s)).
07/07/19 12:33:36.232 IPC Server: Response: 
(void)
07/07/19 12:33:36.233 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementSetNetworkConfiguration
(Array length=1)
[
  (Array length=2)
  [
    (void)
    (Struct length=0)
    {
    }
  ]
]
07/07/19 12:33:36.233 IPC Server: Info: Client 1 successfully registered RPC method "managementSetNetworkConfiguration" (this method is registered by 2 client(s)).
07/07/19 12:33:36.233 IPC Server: Response: 
(void)
07/07/19 12:33:36.235 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) managementCopyDeviceDescriptionFile
(Array length=1)
[
  (Array length=3)
  [
    (Boolean) 0
    (String) 
    (Integer64) 0
  ]
]
07/07/19 12:33:36.235 IPC Server: Info: Client 1 successfully registered RPC method "managementCopyDeviceDescriptionFile" (this method is registered by 2 client(s)).
07/07/19 12:33:36.235 IPC Server: Response: 
(void)
07/07/19 12:33:43.417 Info: Waiting for physical interfaces to connect (10 of 180s).
07/07/19 12:33:53.418 Info: Waiting for physical interfaces to connect (20 of 180s).
07/07/19 12:34:03.419 Info: Waiting for physical interfaces to connect (30 of 180s).
07/07/19 12:34:13.421 Info: Waiting for physical interfaces to connect (40 of 180s).
07/07/19 12:34:23.422 Info: Waiting for physical interfaces to connect (50 of 180s).
07/07/19 12:34:33.423 Info: Waiting for physical interfaces to connect (60 of 180s).
07/07/19 12:34:43.425 Info: Waiting for physical interfaces to connect (70 of 180s).
07/07/19 12:34:53.426 Info: Waiting for physical interfaces to connect (80 of 180s).
07/07/19 12:35:03.427 Info: Waiting for physical interfaces to connect (90 of 180s).
07/07/19 12:35:13.429 Info: Waiting for physical interfaces to connect (100 of 180s).
07/07/19 12:35:17.979 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.134:62094 accepted. Client number: 8
07/07/19 12:35:17.980 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 0
07/07/19 12:35:17.982 RPC Server (Port 2001): Listening for incoming packets from client number 8.
07/07/19 12:35:23.430 Info: Waiting for physical interfaces to connect (110 of 180s).
07/07/19 12:35:28.066 RPC Server (Port 2001): Debug: Connection to client number 8 closed (3).
07/07/19 12:35:33.431 Info: Waiting for physical interfaces to connect (120 of 180s).
07/07/19 12:35:33.510 RPC Server (Port 2001): Debug: Joining read thread of client 0
07/07/19 12:35:33.510 RPC Server (Port 2001): Debug: Client 0 removed.
07/07/19 12:35:43.432 Info: Waiting for physical interfaces to connect (130 of 180s).
07/07/19 12:35:53.434 Info: Waiting for physical interfaces to connect (140 of 180s).
07/07/19 12:36:03.435 Info: Waiting for physical interfaces to connect (150 of 180s).
07/07/19 12:36:13.436 Info: Waiting for physical interfaces to connect (160 of 180s).
07/07/19 12:36:23.438 Info: Waiting for physical interfaces to connect (170 of 180s).
07/07/19 12:36:33.439 Starting UPnP server...
07/07/19 12:36:33.442 Info: UPnP server: Binding to address: 192.168.1.3
07/07/19 12:36:33.442 UPnP Server: Info: Started listening.
07/07/19 12:37:14.614 Devlog: Calling onGet event handler.
07/07/19 12:37:14.615 RPC Server (Port 2002): Info: Connection from ::ffff:192.168.1.1:60929 accepted. Client number: 13
07/07/19 12:37:14.616 RPC Server (Port 2002): Info: RPC server client id for client number 13 is: 4
07/07/19 12:37:14.617 RPC Server (Port 2002): Listening for incoming packets from client number 13.
07/07/19 12:37:14.617 RPC Server (Port 2002): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030320D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:14.618 Devlog: Calling onGet event handler.
07/07/19 12:37:14.636 Devlog: onGet event handler handled event.
07/07/19 12:37:14.637 RPC Server (Port 2001): Debug: Connection to client number 12 closed.
07/07/19 12:37:14.637 RPC Server (Port 2001): Debug: Connection to client number 12 closed (1).
07/07/19 12:37:14.640 Devlog: onGet event handler handled event.
07/07/19 12:37:14.641 RPC Server (Port 2002): Debug: Connection to client number 13 closed.
07/07/19 12:37:14.641 RPC Server (Port 2002): Debug: Connection to client number 13 closed (1).
07/07/19 12:37:15.031 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
07/07/19 12:37:15.051 Debug: Sleeping 250ms before sending response.
07/07/19 12:37:15.302 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:15.302 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:15.403 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:15.403 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:15.404 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
07/07/19 12:37:15.424 Debug: Sleeping 1333ms before sending response.
07/07/19 12:37:15.476 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.1:60011 accepted. Client number: 14
07/07/19 12:37:15.476 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 5
07/07/19 12:37:15.478 RPC Server (Port 2001): Listening for incoming packets from client number 14.
07/07/19 12:37:15.543 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030310D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:15.544 Devlog: Calling onGet event handler.
07/07/19 12:37:15.546 RPC Server (Port 2002): Info: Connection from ::ffff:192.168.1.1:60724 accepted. Client number: 15
07/07/19 12:37:15.546 RPC Server (Port 2002): Info: RPC server client id for client number 15 is: 6
07/07/19 12:37:15.548 RPC Server (Port 2002): Listening for incoming packets from client number 15.
07/07/19 12:37:15.548 RPC Server (Port 2002): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030320D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:15.548 Devlog: Calling onGet event handler.
07/07/19 12:37:15.569 Devlog: onGet event handler handled event.
07/07/19 12:37:15.570 RPC Server (Port 2001): Debug: Connection to client number 14 closed.
07/07/19 12:37:15.570 RPC Server (Port 2001): Debug: Connection to client number 14 closed (1).
07/07/19 12:37:15.571 Devlog: onGet event handler handled event.
07/07/19 12:37:15.571 RPC Server (Port 2002): Debug: Connection to client number 15 closed.
07/07/19 12:37:15.572 RPC Server (Port 2002): Debug: Connection to client number 15 closed (1).
07/07/19 12:37:16.758 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:16.758 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:16.858 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:16.859 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:16.933 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.1:51014 accepted. Client number: 16
07/07/19 12:37:16.933 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 7
07/07/19 12:37:16.935 RPC Server (Port 2001): Listening for incoming packets from client number 16.
07/07/19 12:37:17.001 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030310D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:17.002 Devlog: Calling onGet event handler.
07/07/19 12:37:17.004 RPC Server (Port 2002): Info: Connection from ::ffff:192.168.1.1:56531 accepted. Client number: 17
07/07/19 12:37:17.004 RPC Server (Port 2002): Info: RPC server client id for client number 17 is: 8
07/07/19 12:37:17.006 RPC Server (Port 2002): Listening for incoming packets from client number 17.
07/07/19 12:37:17.007 RPC Server (Port 2002): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030320D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:17.007 Devlog: Calling onGet event handler.
07/07/19 12:37:17.024 Devlog: onGet event handler handled event.
07/07/19 12:37:17.024 RPC Server (Port 2001): Debug: Connection to client number 16 closed.
07/07/19 12:37:17.025 RPC Server (Port 2001): Debug: Connection to client number 16 closed (1).
07/07/19 12:37:17.030 Devlog: onGet event handler handled event.
07/07/19 12:37:17.030 RPC Server (Port 2002): Debug: Connection to client number 17 closed.
07/07/19 12:37:17.031 RPC Server (Port 2002): Debug: Connection to client number 17 closed (1).
07/07/19 12:37:17.037 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
07/07/19 12:37:17.058 Debug: Sleeping 1370ms before sending response.
07/07/19 12:37:18.428 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:18.429 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:18.533 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:18.533 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:18.534 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
07/07/19 12:37:18.554 Debug: Sleeping 1421ms before sending response.
07/07/19 12:37:18.608 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.1:41457 accepted. Client number: 18
07/07/19 12:37:18.609 RPC Server (Port 2001): Info: RPC server client id for client number 18 is: 9
07/07/19 12:37:18.610 RPC Server (Port 2001): Listening for incoming packets from client number 18.
07/07/19 12:37:18.678 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030310D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:18.679 Devlog: Calling onGet event handler.
07/07/19 12:37:18.681 RPC Server (Port 2002): Info: Connection from ::ffff:192.168.1.1:49380 accepted. Client number: 19
07/07/19 12:37:18.681 RPC Server (Port 2002): Info: RPC server client id for client number 19 is: 10
07/07/19 12:37:18.683 RPC Server (Port 2002): Listening for incoming packets from client number 19.
07/07/19 12:37:18.683 RPC Server (Port 2002): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030320D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:18.683 Devlog: Calling onGet event handler.
07/07/19 12:37:18.701 Devlog: onGet event handler handled event.
07/07/19 12:37:18.702 RPC Server (Port 2001): Debug: Connection to client number 18 closed.
07/07/19 12:37:18.702 RPC Server (Port 2001): Debug: Connection to client number 18 closed (1).
07/07/19 12:37:18.706 Devlog: onGet event handler handled event.
07/07/19 12:37:18.706 RPC Server (Port 2002): Debug: Connection to client number 19 closed.
07/07/19 12:37:18.707 RPC Server (Port 2002): Debug: Connection to client number 19 closed (1).
07/07/19 12:37:19.975 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:19.976 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
07/07/19 12:37:20.076 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:20.077 UPnP Server: Debug: Sending notify packets.
07/07/19 12:37:20.156 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.1:51694 accepted. Client number: 20
07/07/19 12:37:20.156 RPC Server (Port 2001): Info: RPC server client id for client number 20 is: 11
07/07/19 12:37:20.157 RPC Server (Port 2001): Listening for incoming packets from client number 20.
07/07/19 12:37:20.232 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030310D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:20.233 Devlog: Calling onGet event handler.
07/07/19 12:37:20.235 RPC Server (Port 2002): Info: Connection from ::ffff:192.168.1.1:53120 accepted. Client number: 21
07/07/19 12:37:20.236 RPC Server (Port 2002): Info: RPC server client id for client number 21 is: 12
07/07/19 12:37:20.237 RPC Server (Port 2002): Listening for incoming packets from client number 21.
07/07/19 12:37:20.237 RPC Server (Port 2002): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A486F73743A203139322E3136382E312E333A323030320D0A4163636570743A202A2F2A0D0A0D0A
07/07/19 12:37:20.237 Devlog: Calling onGet event handler.
07/07/19 12:37:20.255 Devlog: onGet event handler handled event.
07/07/19 12:37:20.256 RPC Server (Port 2001): Debug: Connection to client number 20 closed.
07/07/19 12:37:20.256 RPC Server (Port 2001): Debug: Connection to client number 20 closed (1).
07/07/19 12:37:20.260 Devlog: onGet event handler handled event.
07/07/19 12:37:20.260 RPC Server (Port 2002): Debug: Connection to client number 21 closed.
07/07/19 12:37:20.261 RPC Server (Port 2002): Debug: Connection to client number 21 closed (1).

Hope that you can help me because this is nightmare.

I hamax CUL that have worked. But when I install hassio from fresh i can not make it work anymore

#6

Hallo @blazkom,

the log is not complete. Please post the full log. It seems, your CUL is not working, so please post the max.conf here.

I have only one Homegear folder and this is: config/homegear

This is unusual. What kind of system are you running?

Cheers,

Sathya

#7

I have clean install on Hassio (version 0.95.4)
I used this CUL before, but when I reinstall Hassio, I can not make homegear working.
It’s seams like homegear does not have permision to install all files and directory onto system. If someone have option to test clean install and only homegear, just to make it work. I am trying to install homegear like plugin, from this repostry
https://github.com/stefangries/hassio-addons

Here is also my max.conf file

___________________________________________________________________________

---------------------------------- MAX!  ----------------------------------
___________________________________________________________________________

#######################################
########## General Settings  ##########
#######################################

[General]

moduleEnabled = true

## The MAX! address of Homegear. It is recommended to change this to a random 3 byte hexadecimal
## value starting with 0xFD (e. g. 0xFD43AB). Only change this, when no MAX! devices
## are paired to Homegear as existing pairings will not work anymore!
#centralAddress = 0xFD0001

#######################################
################# CUL #################
#######################################

## The device family this interface is for
[CUL]

## Specify an unique id here to identify this device in Homegear
id = My-MAX-CUL

## When default is set to "true" Homegear will assign this device
## to new peers.
default = true

## Options: cul, coc, cc1100
deviceType = cul

device = /dev/ttyACM0

## Should be "40" for MAX!
responseDelay = 40

#######################################
########## TI CC1101 Module  ##########
#######################################

## The device family this interface is for
#[TI CC1101 Module]

## Specify an unique id here to identify this device in Homegear
#id = My-MAX-CC1101

## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true

## Options: cul, coc, cc1100
#deviceType = cc1100

#device = /dev/spidev0.0

## Default: responseDelay = 95
## Should be "40" for CUL or COC and "45" for TI CC1101.
#responseDelay = 45

## The interrupt pin to use. "0" for GDO0 or "2" for GDO2.
## You only need to connect one of them. Specify the GPIO
## you connected the interrupt pin to below.
#interruptPin = 2

## The GPIO GDO0 or GDO2 is connected to. Specify which GDO to use above.
#gpio1 = 23

### Additional TI CC1190 Config ###

## The GPIO high gain mode of the CC1190 is connected to.
## Default: -1 (disabled)
#gpio2 = 5

## The hexadecimal value for the PATABLE of the TI CC1101.
## Default:
## - Without high gain mode: 0xC2
## - With high gain mode: 0x27 (maximum legally allowed setting)
#txPowerSetting = 0x27


#######################################
################ CUNX  ################
#######################################

## The device family this interface is for
#[CUNX]

## Specify an unique id here to identify this device in Homegear
#id = My-CUNX

## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true

## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw
#deviceType = cunx

## IP address of your CUNX
#host = 192.168.178.100

## Port number your CUNX listens on. Normally 2323.
#port = 2323

## Default: responseDelay = 95
## Should be "40" for CUNX
#responseDelay = 40


#######################################
######### COC, SCC, CSM, CCD  #########
#######################################

## The device family this interface is for
#[COC, SCC, CSM, CCD]

## Specify an unique id here to identify this device in Homegear
#id = My-COC

## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true

#deviceType = coc

#device = /dev/ttyAMA0

## Default: gpio1 = 0
## "17" for COC, SCC and CCD. Empty for CSM.
#gpio1 = 17

## Default: gpio2 = 0
## "18" for COC and SCC. "22" for CCD. Empty for CSM.
#gpio2 = 18

## Should be "40" for MAX!
#responseDelay = 40

## Default: stackPosition = 0 (= no stacking)
## Set stackPosition if you use the SCC and stacked multiple devices.
## Set stackPosition to "1" for the lowest device, to "2" for the device
## above that and so on.
# stackPosition = 0

#######################################
########## Homegear Gateway  ##########
#######################################

## The device family this interface is for
#[Homegear Gateway]

## Specify an unique id here to identify this device in Homegear
#id = My-HG-GW

## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true

#deviceType = homegeargateway

## The host name or IP address of the gateway
#host = 

## The port of the gateway
#port = 2017

## The CA certificate
#caFile = /etc/homegear/ca/cacert.pem

## The client certificate
#certFile = /etc/homegear/ca/certs/gateway-client.crt

## The client key file
#keyFile = /etc/homegear/ca/private/gateway-client.key

## Use the ID defined above to verify the common name of the certificate
## Default: false
#useIdForHostnameVerification = true

## Default: responseDelay = 95
#responseDelay = 42
#8

I don’t know the specifics of Hass.io, so you should ask your question in the Hass.io forum. Alternatively you can run Homeassistant in Docker under Raspbian and install Homegear there (or run both in Docker). But as Homegear is provided as an addon, I assume, it should work in Hass.io as well.

Cheers,

Sathya