Domoticz

I want to update my Domoticz.

Till now I was using version:
===============================================================================
Version: 4.10717
Build Hash: b38b49e5
Compile Date: 2019-05-09 13:04:08
dzVents Version: 2.4.19
Python Version: 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516]
===============================================================================
Pretty old, I would say.

My Domoticz is running on a RaspberryPI 3

If I go to

Instellingen / Settings
Controleer op updates / Check Updates

The response is: There is now update.

So I try to do it by hand:

With Putty I make connection with my RasperryPI

===============================================================================
login as: pi
[email protected]'s password:
Linux raspberrypi 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 29 19:36:30 2023 from 192.168.178.100

pi@raspberrypi:~ $ cd domoticz
pi@raspberrypi:~/domoticz $ sudo ./updaterelease

Updating to latest release version...
Please Standby...
--2023-10-30 19:31:16-- https://www.domoticz.com/download.php?channel=stable&ty pe=release&system=linux&machine=armv7l
Herleiden van www.domoticz.com (www.domoticz.com)... mislukt: Tijdelijk probleem in naamsherleiding.
wget: kan host-adres '‘www.domoticz.com’' niet herleiden

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Restarting Domoticz... (please standby...)

pi@raspberrypi:~/domoticz $
===============================================================================

What do I have to do to update my system to the stable 2023 version?

Please in Jip en Janneke language.
I mean letterly all the steps I have to do.

Thank you in advance.

Rob
Halle
the Netherlands

DomoticaRob wrote: ↑Monday 30 October 2023 20:22 Herleiden van www.domoticz.com (www.domoticz.com)... mislukt: Tijdelijk probleem in naamsherleiding.
wget: kan host-adres '‘www.domoticz.com’' niet herleiden
-snip-
Please in Jip en Janneke language.

Rob,

Your raspberry doesn't have access to the internet or doesn't have DNS configured, which means that the DomainName ‘www.domoticz.com’ fails to be resolved to an IP Address, which is needed to be able to communicate on the internet. (not Jip&Janneke i know, but this is what it is! )
Test the following on the raspberry when you are on the command prompt: pi@raspberrypi:~ $

• Code: Select all

  ping www.domoticz.com

  This should show this when both DNS and Internet are available:

  Code: Select all

  PING www.domoticz.com (188.114.96.0) 56(84) bytes of data.

• to check DNS you do command:

  Code: Select all

  nslookup www.domoticz.com

  which should show something like:

  Code: Select all

  Server:         192.168.0.1
  Address:        192.168.0.1#53
  
  Non-authoritative answer:
  Name:   www.domoticz.com
  Address: 188.114.97.0
  Name:   www.domoticz.com
  Address: 188.114.96.0
  Name:   www.domoticz.com
  Address: 2a06:98c1:3121::
  Name:   www.domoticz.com
  Address: 2a06:98c1:3120::
  

Cheers, Jos


ps: I have split this off into its own topic in a support forum.

Thanks Jos, for you speedy response.

I have done what you wrote, see the following:

==============================================================================
login as: pi
[email protected]'s password:
Linux raspberrypi 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Oct 30 19:30:41 2023 from 192.168.178.100

pi@raspberrypi:~ $ ping www.domoticz.com
ping: www.domoticz.com: Tijdelijk probleem in naamsherleiding

pi@raspberrypi:~ $ nslookup www.domoticz.com
-bash: nslookup: opdracht niet gevonden

pi@raspberrypi:~ $
==============================================================================

I could and still can have acces to my Domotcz outside my network and WiFi.
So if I'am in another city I can control my Domoticz.

You write somthing about DNS.

Where can I find the info do make this properly for my RaspberryPI

Follow this explanation and try again.
The explanation is very Jip&Janneke because it even tells you how to use the text editor nano.

Regards, Jip from Twente

PS
I guess that if you edit /etc/resolve.conf (sudo nano /etc/resolv.conf) before you change settings you will see something like:
# Generated by resolvconf
nameserver 127.0.0.1

Hello Jip,

I have done what was written in the explanation.

At the end when I type sudo nano /etc/resolv.conf I get:

=====================================================
pi@raspberrypi:~ $ sudo nano /etc/resolv.conf

GNU nano 2.7.4 Bestand: /etc/resolv.conf

# Generated by resolvconf
domain fritz.box
nameserver 192.168.2.1
=====================================================

At the end of the dhcpcd.conf file is:

=====================================================
static domain_name_servers=192.168.178.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 eth 0fallback static_eth0
static domain_name_servers=8.8.4.4 8.8.8.8
=====================================================

Now my Domoticz system doesn't work anymore.

So no lightning and no heating.

Please help, the house is very cold and dark.

I hope/assume you kept the original content before changing, so did you change things back first?
What is the IP used in your Home network? (CHeck the IP of your phone/computer)

DomoticaRob wrote: ↑Tuesday 31 October 2023 1:31 domain fritz.box
nameserver 192.168.2.1

This looks strange when the IP range is 192.168.1.x! This is normally should be your Router , something like 192.168.1.1 when you have a 192.168.1.x network.
.....or .......

DomoticaRob wrote: ↑Tuesday 31 October 2023 1:31 At the end of the dhcpcd.conf file is:

=====================================================
static domain_name_servers=192.168.178.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 eth 0fallback static_eth0
static domain_name_servers=8.8.4.4 8.8.8.8
=====================================================

This is very strange when you have an 192.168.2.x in resolve AND 192.168.178.x & 192.168.1.x ip addresses in this file!

Now my Domoticz system doesn't work anymore.

So no lightning and no heating.

Please help, the house is very cold and dark.

I don't know how or why, but this morning my Domoticz system was working as always.

So my 'Please help, the house is very cold and dark.' is not vacant anymore.


Still there is that problem that, in my case, the update doesn't work.

I have tried to do the DNS stuff what Jip suggested.

Unfortunately that did not work.

Do I have to change something in my router or with my Internet provider?

My provider is Solcon and my router is a FRITZ!Box 7530.

So what about for starters:

jvdz wrote: ↑Tuesday 31 October 2023 9:11 What is the IP used in your Home network?

I think it is better to perform this when you are physically at your system so you can repair stuff when the remote connection fails by the changes you are trying to do.

Edit perhaps setup a test environment with a copy of your remote domoticz environment and test that.
Updating from a 4 years old domoticz environment is a little bit tricky. Also check the OS you are running on. Could be outdated for Domoticz 2023.2 too

I think I'll wait until the Raspberry PI 5 is available and then install a completely new installation of Domoticz.

Can Domoticz run on the RPi5?

Use a box TV x96. It costs much less than any Pi and run perfectly. I have 3 configuration running for years without troubles.
Good luck

polo9222 wrote: ↑Tuesday 31 October 2023 9:56 Use a box TV x96. It costs much less than any Pi and run perfectly. I have 3 configuration running for years without troubles.
Good luck

Do you have an instruction how to install Domoticz on such a system? It first needs to be a linux OS installed on it? It now seems to run Android....

You are right. First , you have to replace Android by a debian linux. Then you install domoticz. You have Many tutos on thé web corresponding to your box or processor. Take a 4/32 GB x96 mini Android 9 (max)box that cost around 15 to 25€ plus a wifi dongle 3€ if necessary.

M'y configurations have UP to 50 devices zigbee (around 150 domoticz devices) plus Many other wifi ones (sonoff, Espeasy, netatmo, ....)

Here is my dhcpcd.conf file.
Is it right or are the errors/mistakes?

==================================================================
pi@raspberrypi:~ $ sudo nano /etc/dhcpcd.conf
==================================================================
# 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.178.11/8080
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.178.1
static domain_name_servers=192.168.2.1
# 8.8.8.8 fd51:42f8:caae:d92e::1

interface wlan0
static ip_address=192.168.178.11
static routers=192.168.178.1
static domain_name_servers=192.168.178.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 eth 0fallback static_eth0
static domain_name_servers=8.8.4.4 8.8.8.8

When I ping in Windows CMD it works when I use the site name as well as when I use the site address:
==============================
C:\>ping google.com
Pinging google.com [142.251.36.14] with 32 bytes of data:
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Ping statistics for 142.251.36.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms
==============================
C:\>ping 142.251.36.14
Pinging 142.251.36.14 with 32 bytes of data:
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Reply from 142.251.36.14: bytes=32 time=5ms TTL=60
Ping statistics for 142.251.36.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms
C:\>
==============================
When I ping in the RasperryPI it only works when I use the site address:
==============================
pi@raspberrypi:~ $ ping -c3 google.com
ping: google.com: Tijdelijk probleem in naamsherleiding
==============================
pi@raspberrypi:~ $ ping -c3 142.251.36.14
PING 142.251.36.14 (142.251.36.14) 56(84) bytes of data.
64 bytes from 142.251.36.14: icmp_seq=1 ttl=60 time=5.77 ms
64 bytes from 142.251.36.14: icmp_seq=2 ttl=60 time=5.38 ms
64 bytes from 142.251.36.14: icmp_seq=3 ttl=60 time=5.12 ms
--- 142.251.36.14 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 5.125/5.427/5.772/0.272 ms
pi@raspberrypi:~ $
==============================

So I think the problem must be somewhere in the RasperryPI configuration.
In the post above you can see how my dhcpcd.conf looks like.
What is the solution?

Hello @DomoticaRob,

You see:

ping: google.com: Tijdelijk probleem in naamsherleiding

This indicates clearly that you have a DNS problem

Your Raspberry Pi is unable to resolve the IP address, based on the hostname.
Exactly the same as concluded by @jvdz.

Let's check your Raspberry Pi dhcpcd.conf file

The most of it are default and as such okay.
Two parts has been changed.

1.

# Example static IP configuration:
interface eth0
static ip_address=192.168.178.11/8080
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.178.1
static domain_name_servers=192.168.2.1
# 8.8.8.8 fd51:42f8:caae:d92e::1

A recommendation for the future is not to change this part, but create a new one.

Your IP address is very strange, as it shows 192.168.178.11/8080
This should be 192.168.178.11/24, as it should indicate the subnet mask in use.
Why it is 8080. which is the default port of Domoticz, I do not know, but it is wrong.
Your "static router" (192.168.178.1) looks okay.
The "static domain_name_server" indicate 192.168.2.1.
This is also strange as it is in the private IP address range (192.168.x.y).
Unless it is somewhere configured as a "caching DNS" and you have a bridge between 192.168.178.0 and 192.168.2.0 networks this will not be reachable.
Replace it by 8.8.8.8 8.8.4.4 This will point to the primary and secundary Google DNS servers, which are pretty fast.

2.

interface wlan0
static ip_address=192.168.178.11
static routers=192.168.178.1
static domain_name_servers=192.168.178.1

Your static IP address for the wlan0 interface is the same as the IP address of the eth0 interface.
Both show 192.168.178.11. You might see issues, if they are both online at the same time. This might cause an IP address conflict.
I recommend to select another IP address, e.g. 192.168.178.12, if that is free.
And add "/24", Example 192.168.178.12/24
"Static routers" = okay
Again your domain server is the same as the router and this will only work if this device is also configured as a "caching DNS server".
If not sure, again take 8.8.8.8 8.8.4.4

See also the last line in this section:

# 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 eth 0fallback static_eth0
static domain_name_servers=8.8.4.4 8.8.8.8

Comment out the (now) uncommented lines¨

static routers=192.168.1.1
static domain_name_servers=192.168.1.1

Modify this section as well.
This section should be:

# 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 eth 0
#fallback static_eth0

I hope this will solve your issue.

Regards

Rob,

Also confirm the ip address of your router/modem as requested by Jos. It’s probably printed on the back side of the router.
(Which provider do you have and which router/modem)

It’s probably 192.168.178.1 or 192.168.1.1

As mentioned by previous posters it’s weird you have 3 different networks. Usually this is not the case and a reason for network problems. All your problems are probably related to that.

All your ip addresses should have the same first 3 sections so all should start with:
192.168.178.xxx
Or all should start with:
192.168.1.xxx

Or a different set depending on the settings in your router/modem.

Please check which the correct network address is (backside of your modem) or ask the client support of your provider.

Without this information it’s difficult to give you good instructions

Thanks for all the replies.

At one moment Domoticz was totally dead, so I wiped a lot of tears.

I made a complete new installation on my RaspberryPI 3B+ with the new 2023.2 version.

Unfortunately I had no proper backup.

Luckely I had a text copy of all my dzVents scripts and also a text copy of the devices parameters, so most of the necessary information I still have.

Now I am configuring my Domoticz system step by step.

The most important parts, two heating systems are up and running again, so I can take off my coat.

Again, many thanks for all you replies.

Congratulations !
Now it is warm, you Can take some Time to think to change and forget your Pi !
Good luck