Domoticz no longer accesible via wired, but only via wlan

[Jheronymus]

Hi,

I have some trouble with my Domoticz and Raspberry after a series of updates. I used to have the Raspberry on a wired ethernet connection with fixed IP. That no longer worked for some reason and now I can start the raspberry and I can access the dashboard on the dhcp linked to the wlan0, but not via the IP linked to eth0. I can SSH via putty to either... not sure what is going on.

That IP set in eth0 is outside the range of DHCP addresses on my router. (192.168.1.34). There are a few devices that assume domoticz is listeing to this (for example the P1 smartmeter trying to connect to 192.168.1.34:8080)

I'm a bit puzzled on what to check next or how to debug this.

I have Domoticz Version: 2024.7
I have a raspberry pi 3 model B plus Rev 1.3
I'm running Raspbian 10 (buster)

in /etc/dhcpcd.conf I have

Code: Select all

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

# Example static IP configuration:
interface eth0
static ip_address=192.168.1.34/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.1.1
static domain_name_servers=192.168.1.1 8.8.8.8
# ipv6 DNS?? fd51:42f8:caae:d92e::1

# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0

In ~/domoticz/domoticz.sh I have

Code: Select all

#! /bin/sh
### BEGIN INIT INFO
# Provides:          domoticz
# Required-Start:    $network $remote_fs $syslog $time
# Required-Stop:     $network $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Home Automation System
# Description:       This daemon will start the Domoticz Home Automation System
### END INIT INFO

# Do NOT "set -e"

PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
DESC="Domoticz Home Automation System"
NAME=domoticz
USERNAME=pi
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME

DAEMON=/home/$USERNAME/domoticz/$NAME
DAEMON_ARGS="-daemon"
#DAEMON_ARGS="$DAEMON_ARGS -daemonname $NAME -pidfile $PIDFILE"
DAEMON_ARGS="$DAEMON_ARGS -www 8080"
DAEMON_ARGS="$DAEMON_ARGS -sslwww 443"
#DAEMON_ARGS="$DAEMON_ARGS -log /tmp/domoticz.txt"
#DAEMON_ARGS="$DAEMON_ARGS -syslog"

# Exit if the package is not installed

(and then the rest of that file)

I've used raspi-config to make sure it waits for network on boot. (didnt help)

Any suggestions are welcome.

[jvdz]

I have done this after I did an Debian version upgrade:
To set a fixed IP in the newer Debian version I installed:

Code: Select all

sudo apt-get install network-manager

and then run the command where you can set the static IP for the Ethernet interface:

Code: Select all

nmtui

[Jheronymus]

Thanks @jvdz.

I'm not too concerned with the network setup itself.
What I dont understand is that it looks like domoticz is running, but only accesible via the wlan IP.
It somehow looks like is bound to that, but I dont understand how/why that is. Even if I wanted to do that deliberatly (which I dont)
If I have to choose, I want it to run on the wired eth0 connection. But preferably on both (just like for SSH it doesnt matter which IP I use.)

[jvdz]

Well, I think it's because your Ethernet Fixed ip isn't assigned anymore after the OS upgrade, hence you can't access the RPI via the Ethernet port.
Have you checked the ip addresses assigned to all network interfaces? To check run command : ip address

[Jheronymus]

Well, it was working friday...
I swapped the ethernet cable, and I swapped the power supply PSU. The Rasbperry was like 40cm from its final place...
I did not find any low voltage warnings in dmesg

Now had some additional time and tidied up, put it on the old power supply and moved it to final spot... no ethernet...argh..
I just ordered a new PSU and will try again when it arrives.

Something else was really weird. I had everyting working, including P1 gateway, OpenTherm gataway via USB (OTGW) last friday... but today two things:
- Even though I could SSH into device on both the eth0 and wlan IP, I could not access Domoticz. The service was running, but I had to restart it to make it work again. I couldnt find any crashlog or something.
- now also the OTGW was giving uncoded messages and did not really work (in status log showing like: OTGW: BC0090000.)

Since I'm not a linux expert, I have some challenges troubleshooting all this. But first I want to make sure there are no hardware issues.

I found some old experiements on the rapsberry, like VPN and 1-wire things that I disabled. Also did cleanup of apt-get to get to 50% diskspace use.

[jvdz]

Did you do the command i gave and check the output?