Unable to parse ip

bauerpower · October 28, 2020, 11:19am

Dear Wolfgang,

it seems to me I have a similar problem…

I setup a brand new PI 4/8 with 128GB SD and the recommended “openHABian-OS”.
… I was wondering about changing HDMI settings after the first reboot

Anyhow I have the same “error” --> unable to parse ip. please debug!
Different to the topic of SamH1999 I’m able to access the server via SSH and HTTP…
But im to sure to proceed with installation because it seems to me bug (and you never know…)

I followed your instruction but I can’t identify any “issue”:

/sbin/ip route get 8.8.8.8 | head -1 | grep -Po ‘(?<=src )(\d{1,3}.){4}’
–> 192.168.1.199

/sbin/ip route get 8.8.8.8
–> 8.8.8.8 via 192.168.1.1 dev eth0 src 192.168.1.199 uid 1000

arp -a
->
pi.hole (192.168.1.16) at dc:a6:32:53:75:3c [ether] on eth0
SecurityGatewayUSG (192.168.1.1) at 80:2a:a8:cd:e1:69 [ether] on eth0

who | grep -c “$USER”
–> 2

sudo netstat -tulpe --numeric-ports |grep java
–>
tcp6 0 0 localhost:43993 [::]:* LISTEN openhab 17079 781/java
tcp6 0 0 [::]:8443 [::]:* LISTEN openhab 18177 781/java
tcp6 0 0 [::]:8101 [::]:* LISTEN openhab 18175 781/java
tcp6 0 0 [::]:5007 [::]:* LISTEN openhab 19092 781/java
tcp6 0 0 [::]:8080 [::]:* LISTEN openhab 17088 781/java
udp6 0 0 [::]:5353 [::]:* openhab 18211 781/java

ifconfig

[12:31:37] openhabian@openhab:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.199 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::54e9:3810:a552:e59 prefixlen 64 scopeid 0x20
ether dc:a6:32:d5:ef:e7 txqueuelen 1000 (Ethernet)
RX packets 26178 bytes 4501701 (4.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9963 bytes 1869219 (1.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 140 bytes 11328 (11.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 140 bytes 11328 (11.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Any idea how to fix?

Best regards

… brand new member

mstormi · October 28, 2020, 11:55am

First, provide proper information if you want help:

Second, your system is severely screwn up when it doesn’t even know the systemctl command.

Third, your DHCP/DNS setup is probably bad which is why your box didn’t obtain a proper IP or cannot use your DNS resolver.
@bauerpower same for you, but don’t invade others’ thread please.

Read the debug guide for things to try.

Your best bet is to fix your router first and then to install again from scratch using the openHABian image. You seem to be using a RPi4/8GB (not a good choice as the docs tell you) which does not work with ZRAM but the install routine should recognize that and not install ZRAM in the first place.

bauerpower · October 28, 2020, 2:59pm

Dear Markus,

thank you very much for your advice … very much appreciated.

Should I create a new topic?

Regarding your recommendation… I reinstalled from scratch already 5 times
I’m using a UNIFI Network and I never had any problems with my DHCP-Server
From my DHCP Server it seems the IP-request was handled correctly.

Do you think I should switch to P3 (I have one)?

Thank you for your help (appreciated)

Joerg

bauerpower · October 28, 2020, 3:00pm

mstormi · October 28, 2020, 3:09pm

Should I create a new topic?

normally yes but no

No point in that as now you have one but please don’t expect me or others to debug your setup.
Follow the debug guide, try disabling IPv6.
openHABian is standard Raspi OS w.r.t. networking so you can google that up in a Raspi or networking forum.
Don’t get mislead by the ‘Unable to parse ip’ output, it’s just the output of the FireMotD script.

SamH1999 · October 28, 2020, 3:20pm

Firstly I’ve provided information clearly showing the issue is that it says unable to parse IP and that I get nothing at http://openhab/ even though it says they’re are two active connections

Secondly you saying my systems screwed up is in no way helpful at all in terms of helping me solve the issue

Thirdly I haven’t changed any DNS/DHCP settings on my router

Also I have already tried reinstalling it from scratch twice now as it was working properly 3 days ago then stopped working and that hasn’t fixed anything and that hasn’t solved the issue.

If it was working 3 days ago clearly it isn’t a problem with the router.

mstormi · October 28, 2020, 5:41pm

Sorry for coming across as rude but I am just trying to help. As @rlkoshak mentioned I’m no native speaker so please attribute this to cultural differences and us (or me) being just another ‘harsh’ German.
For comprehensiveness, though: your posts are perceived by me as also somewhat rude: you ignored several of the items from the ‘how to post’ post I referenced, you didn’t provide any of the information it would take to help you, and still expect a no less than “helpful” answer (a solution as per your standard I presume) from volunteers like me spending their little spare time to help you for free.
And your response to them trying to is to complain with the moderators … not quite a move motivating me or others to help you in the future.
(and just for a fun comparison, see @bauerpower’s completely different reaction to the albeit very same post of mine).

Ok I suggest we stop the blaming here and try getting your box to work instead.

“unable to parse IP” is only the output of the FireMotD tool which does not necessarily represent the
state of the system. Obviously you can login so a fair amount of IP connectivity is there.

Well I thought it is but eventually I still wasn’t explicit enough then.
On the fact side of things, the little information you gave indicate your box is currently so broken that it does not make sense to try debugging, it would turn out to be a waste of time on everyone’s part. Yours, mine, everyone else’s.
When systemctl isn’t there as it shows it isn’t on your box, the openHAB service is also (very likely) down. Which explains why you cannot connect to it on port 8080.
This is why the probably fastest path to a solution is to reinstall right away … which is what I advised you to do next. If you asked me, I would call that ‘helpful’. I admit I should have explained better, but I was a bit in a hurry, sorry.

These sort of problems are very hard to figure out, even more so from remote.
There’s no IFTTT like template how to cope with the situation.
Have you read the debug guide I referenced ? It tells you how to enable extensive logging on automated image installs and what else you could try.

As already advised, reinstall from scratch. Read the docs how to re-parametrize your next install run before you start.
Use clonebranch=master, debugmode=maximum, ipv6=disable and zraminstall=disable
in openhabian.conf. Post the logfile /boot/first-boot.log here (spell it correctly, boot vs bot as you typed it) then we can have a look at what’s going wrong along the (installation) way.

Wolfgang_S · October 28, 2020, 6:16pm

with this output I would expect to see the IP address in the FireMotd output as this is the code that is being used in the FireMotd script.

mstormi · October 28, 2020, 7:43pm

Forget about the ‘unable to parse ip’. It’s probably just output of a broken script (FireMotD) and not necessarily a real issue with your system. That being said, do you have a route to 8.8.8.8 ?
Is there any other symptom or maybe you don’t have any problem at all ?

BTW you used wrong quotes when you quoted the /sbin/ip command

SamH1999 · October 28, 2020, 7:51pm

If your being rude of course I’m going to complain to an administrator as this forum has a if you see a problem flag it policy.

Frankly saying English is not my native language is no excuse for being rude. I regularly interact with lots of non native English speakers and they are no where near as rude as you.

And while I was more than willing to give you the benefit of the doubt after talking to the administrator it’s clear from your response that you don’t deserve the benefit of the doubt as your rudeness is a common issue

As is evident by the fact the administrator said Markus in particular comes across as blunt and sometimes blunt to the point of rudeness.

This makes me believe that many people have reported you for being rude in the past and that speaks volumes about you.

I have provided the thread with all the information I have which is screenshots showing it saying unable to parse IP, screenshots showing I can’t access my openhab even though it says I’m connected and screenshots showing the commands I was asked to enter didn’t work. I also mentioned how it was previously working 3 days ago.

You could have politely said I need more information and given me a list of the some of information that would be required to help me be able to solve my problem like the administrator did but you didn’t

Frankly your “apology” if you can even call it that clearly isn’t an apology it is just you complaining that I reported you as I had every right to do and effectively making a threat that you and others won’t help me in the future as I reported you.

This forums policy is if you see a problem flag it and your reaction is precisely the reason people stay silent.

After talking to the administrator I got some helpful advice on what I should try next which was that it might be a hardware issue and to try replacing the SD card and if the problem still persists to try a raspberry pi forum.

Helpful suggestions don’t always have to be the solution to a problem.

For example one person offered a helpful suggestion saying try looking at the logs which while it didn’t solve my problem, it was still a helpful response whereas your advice was your system is severely screwn up.

As you can see there is a clear difference between the advice I got from someone else and the advice you gave.

You also said I come across a rude for ignoring several items from the guide you linked when I haven’t as I will demonstrate below

Did you search

yes I did and there were no similar questions as you can see from the screenshot below

Did you search correctly

Yes I did as I searched only for the specific error which is unable to parse IP as you can see from the screenshot below

I found a similar topic but it’s already solved and I still have a problem. Should I post in it?

This was not relevant to my search as there were no similar topics as you can see from the screenshot below

Did you read and search the docs ?

Which I did

choose a category

I chose setup configuration and use and beginners which are the appropriate categories

Title

The title clearly states my issue so it is a good title

Tags

The tags I used were openhab2 ssh and debug which are appropriate tags for my question I would have used more but you are limited to 3

describe you goal

It’s very clear from the screenshots my goal is to access openhab on the internet and I clearly said that this is the issue that I’m facing so it’s obvious the goal is to not be facing this issue

show effort

There were no similar posts to mine so I couldn’t have posted similar links

I described what I have tried for example when I tried entering the commands given to me and when I tried installing and uninstalling zram as suggested and when I tried reinstalling openhabian from scratch

describe your environment

It clearly says in the screenshot what version of raspberry pi and openhabian I am using

describe what you changed and what’s happening now

I did this when I said I’ve tried uninstalling zram and when I said I’ve tried reinstalling openhabian from scratch and the problem is persisting

Use proper formatting

I have used proper formatting

Attach examples

This was not possible for my thread

reread it

Which I have done

Should I mention people in the post?

Which I haven’t done like it says. However you have 3 times through the thread even though it says not to.

You also accuse me of blaming which I’ve not done at all. All I have said to the moderator is you came across as rude and the moderator assured me that it was just because your not English and I gave you the benefit of the doubt then you reply to the thread accusing me of being rude for not following a guide I followed and say how that me reporting you validly will make you and others not help me in the future

It’s also clear that you haven’t read my response fully as otherwise you would be aware that I’ve already tried reinstalling openhabian from scratch which is what you suggested to do in your last reply.

rlkoshak · October 28, 2020, 8:18pm

There isn’t an administrator. There is a group of moderators, and Markus is among them. That’s what the little grey shield icon indicates next to the user name.

No, not frequently. I can’t remember any other reports frankly. But I’ve seen cases where his (and other) posts have devolved into accusations of rudeness and such. Having worked with him and other similar posters for years, I know that rudeness is not the intent.

I didn’t ask for information. I just confirmed that you didn’t provide enough information. I didn’t provide a list of what information would be needed.

We can continue wasting all our time being angry at each other and accusing each other of rudeness, or we can let it go and move on. It’s not productive.

mstormi · October 28, 2020, 8:46pm

Thanks Rich for setting the record straighter. As you can imagine I was tempted to answer all the accusations and correct a number of improper statements (just one for the record: the search function of the forum is broken at the moment, which is pretty unfortunate in this context).
I tried getting productive instead with my last post by giving detailed instructions on how to proceed.
But as that also wasn’t valued I decided to let go and cease wasting my efforts and time here.

denominator · October 29, 2020, 9:27am

I tried getting productive instead with my last post by giving detailed instructions on how to proceed.
But as that also wasn’t valued I decided to let go and cease wasting my efforts and time here.

Facts don’t care about feelings.

Mr Storm is one of the go to people when I have a problem with openhaian. Mainly I just read the manual. I work for a Mc massive company onsite every day at client’s facility’s fixing issues the client dosen’t know the terminology to ask me to fix the issue. I am use to the 100 questions to get 1 answer.

Now @SamH1999

Without being to blunt.
Where are we at?

Flip · October 29, 2020, 2:16pm

As the forum search option is having a problem - I tracked down the issue for the “Unable to parse ip”-message with another user some days ago. The problem was an outdated version of FireMotD. Please have a look here:

You can try to run:

/usr/local/bin/FireMotD --version

The version I am using is:
FireMotD v12.05.191019

Additionally you can run:

sudo /usr/local/bin/FireMotD -S
sudo /usr/local/bin/FireMotD --theme Gray

This should at least solve the display-problem of the IP.

ckw · October 29, 2020, 11:48pm

I have the same issue with “Unable to parse ip” in the SSH startup. I just installed openHABian 2 days ago from the latest stable version on github. I am running on a Raspberry Pi 3B, Raspbian GNU/Linux 10 (buster), OpenHAB 2.5.10-1 (Release Build). The FireMotD version comes back as:

FireMotD v12.05.191019

I tried using Flip’s last suggestions:

sudo /usr/local/bin/FireMotD -S
sudo /usr/local/bin/FireMotD --theme Gray

That did display the IP properly when it ran the last command but on rebooting the same “Unable to parse ip” came back up again. Everything else seems to be working properly. I am just a bit concerned since it says “Please debug.” Any suggestions? Just ignore the message?

Flip · October 30, 2020, 2:59am

Sometimes FireMotD is installed in 2 locations:

/usr/local/bin
/opt/FireMotD

Please check the .bash_profile and .profile in your openhab-users home-directory.

Additionally you can run:

which FireMotD

as openhab-User to see which path is used…

rlkoshak · October 30, 2020, 1:32pm

Also see [Solved] SSH Welcome screen IP display is "Unable to parse ip. Please debug."

There was apparently a change in how Firemotd works.

ckw · October 30, 2020, 1:56pm

Flip,
Thanks for the response. I had already check that and both location have the right version. I think the reply from mstormi in the
[Solved] SSH Welcome screen IP display is "Unable to parse ip. Please debug.
thread has the issue diagnosed and solved.
Thanks again.

Flip · October 30, 2020, 3:12pm

Yes, @mstormi is right… The newer versions of openhabian are using a systemctl service for FireMotD as were older versions are using a cronjob…

SamH1999 · November 5, 2020, 7:36pm

This is what happened when I ran sudo systemctl status openhab2.service

[17:36:41] openhabian@openHABianDevice:~$ sudo systemctl status openhab2.service
[sudo] password for openhabian:
Warning: The unit file, source configuration file or drop-ins of openhab2.service changed on
● openhab2.service - openHAB2 instance, reachable at http://openHABianDevice:8080
Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/openhab2.service.d
└─override.conf
Active: active (running) since Fri 2020-10-30 11:57:39 CET; 6 days ago
Docs: https://www.openhab.org/docs/
https://community.openhab.org
Process: 708 ExecStartPre=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name “.rules" -exec
Process: 726 ExecStartPost=/bin/sleep 120 (code=exited, status=0/SUCCESS)
Process: 1801 ExecStartPost=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name ".x” -exec /u
Main PID: 724 (java)
Tasks: 94 (limit: 4915)
CGroup: /system.slice/openhab2.service
└─724 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab

Oct 26 14:30:48 openHABianDevice systemd[1]: Starting openHAB2 instance, reachable at http://
Oct 30 11:57:39 openHABianDevice systemd[1]: Started openHAB2 instance, reachable at http://o
lines 1-18/18 (END)…skipping…
Warning: The unit file, source configuration file or drop-ins of openhab2.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
● openhab2.service - openHAB2 instance, reachable at http://openHABianDevice:8080
Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/openhab2.service.d
└─override.conf
Active: active (running) since Fri 2020-10-30 11:57:39 CET; 6 days ago
Docs: https://www.openhab.org/docs/
https://community.openhab.org
Process: 708 ExecStartPre=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name “.rules" -exec /usr/bin/rename.ul .rules .x {} ; (code=exited, status=0/SUCCESS)
Process: 726 ExecStartPost=/bin/sleep 120 (code=exited, status=0/SUCCESS)
Process: 1801 ExecStartPost=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name ".x” -exec /usr/bin/rename.ul .x .rules {} ; (code=exited, status=0/SUCCESS)
Main PID: 724 (java)
Tasks: 94 (limit: 4915)
CGroup: /system.slice/openhab2.service
└─724 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenhab.l

Oct 26 14:30:48 openHABianDevice systemd[1]: Starting openHAB2 instance, reachable at http://openHABianDevice:8080…
Oct 30 11:57:39 openHABianDevice systemd[1]: Started openHAB2 instance, reachable at http://openHABianDevice:8080.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-18/18 (END)

This is what came up when I ran SSH - cat /boot/first-boot.log

[17:39:42] openhabian@openHABianDevice:~$ cat /boot/first-boot.log

2020-08-20_10:48:02_UTC [openHABian] Starting the openHABian initial setup.
2020-08-20_10:48:02_UTC [openHABian] Storing configuration… OK
2020-08-20_10:48:02_UTC [openHABian] Starting webserver with installation log… OK
2020-08-20_10:48:07_UTC [openHABian] Changing default username and password… OK
2020-08-20_10:48:08_UTC [openHABian] Setting up Ethernet connection… OK
2020-08-20_10:48:08_UTC [openHABian] Ensuring network connectivity… OK
2020-08-20_10:48:08_UTC [openHABian] Waiting for dpkg/apt to get ready… OK
2020-10-26_09:55:00_UTC [openHABian] Updating repositories and upgrading installed packages… OK (rebooting)

2020-10-26_09:57:33_GMT [openHABian] Starting the openHABian initial setup.
2020-10-26_09:57:33_GMT [openHABian] Storing configuration… OK
2020-10-26_09:57:33_GMT [openHABian] Starting webserver with installation log… OK
2020-10-26_09:57:38_GMT [openHABian] Changing default username and password… SKIPPED
2020-10-26_09:57:38_GMT [openHABian] Setting up Ethernet connection… OK
2020-10-26_09:57:38_GMT [openHABian] Ensuring network connectivity… OK
2020-10-26_09:57:38_GMT [openHABian] Waiting for dpkg/apt to get ready… OK
2020-10-26_09:57:44_GMT [openHABian] Updating repositories and upgrading installed packages… OK
2020-10-26_09:57:47_GMT [openHABian] Installing git package… OK
2020-10-26_09:58:14_GMT [openHABian] Updating myself from https://github.com/openhab/openhabian, stable branch… OK
2020-10-26_09:58:18_GMT [openHABian] Starting execution of ‘openhabian-config unattended’… OK
2020-10-26_09:58:18_GMT [openHABian] Checking for root privileges… OK
2020-10-26_09:58:18_GMT [openHABian] Updating Linux package information… OK
2020-10-26_09:58:23_GMT [openHABian] Loading configuration file ‘/etc/openhabian.conf’… OK
2020-10-26_09:58:23_GMT [openHABian] Setting timezone based on openhabian.conf… OK (Europe/Berlin)
2020-10-26_10:58:23_CET [openHABian] Enabling time synchronization using NTP… OK
2020-10-26_10:58:24_CET [openHABian] Setting locale based on openhabian.conf… OK (reboot required)
2020-10-26_10:58:59_CET [openHABian] Setting hostname of the base system based on openhabian.conf… OK
2020-10-26_10:58:59_CET [openHABian] Setting the GPU memory split down to 16MB for headless system… OK
2020-10-26_10:58:59_CET [openHABian] Enabling Audio output… OK
2020-10-26_10:59:00_CET [openHABian] Installing basic can’t-be-wrong packages (screen, vim, …)… OK
2020-10-26_10:59:31_CET [openHABian] Installing additional needed packages… OK
2020-10-26_11:00:09_CET [openHABian] Installing additional bluetooth packages… OK
2020-10-26_11:00:16_CET [openHABian] Adding slightly tuned bash configuration files to system… OK
2020-10-26_11:00:16_CET [openHABian] Adding slightly tuned vim configuration file to system… OK
2020-10-26_11:00:16_CET [openHABian] Downloading FireMotD… OK
2020-10-26_11:00:19_CET [openHABian] Installing FireMotD… OK
2020-10-26_11:00:19_CET [openHABian] Generating FireMotD theme… OK
2020-10-26_11:00:30_CET [openHABian] Setting up FireMotD apt updates count service… OK
2020-10-26_11:00:39_CET [openHABian] Installing cached version of Java to ensure that some form of Java is installed!
2020-10-26_11:00:39_CET [openHABian] Installing Java Zulu prerequisites (libc, libstdc++, zlib1g)… OK
2020-10-26_11:00:39_CET [openHABian] Installing Java Zulu 8 32-Bit OpenJDK… OK
2020-10-26_11:00:39_CET [openHABian] Installing Java Zulu CEK to enable unlimited cipher strength… OK
2020-10-26_11:00:42_CET [openHABian] Beginning install of latest openHAB release (stable)… OK
2020-10-26_11:00:42_CET [openHABian] Adding required keys to apt… OK
2020-10-26_11:00:43_CET [openHABian] Installing selected openHAB version… OK
2020-10-26_11:01:27_CET [openHABian] Setting up openHAB service… OK
2020-10-26_11:01:28_CET [openHABian] Optimizing openHAB to run on low memory single board computers… OK
2020-10-26_11:01:28_CET [openHABian] Setting openHAB HTTP/HTTPS ports… OK
2020-10-26_11:01:28_CET [openHABian] Creating dependencies to jointly start services that depend on each other… OK
2020-10-26_11:01:28_CET [openHABian] Adding delay on loading openHAB rules… OK
2020-10-26_11:03:28_CET [openHABian] Adding an openHAB dashboard tile for ‘openhabiandocs’… OK
2020-10-26_11:03:28_CET [openHABian] Adding openHAB syntax to vim editor… OK
2020-10-26_11:03:30_CET [openHABian] Adding openHAB syntax to nano editor… OK
2020-10-26_11:03:31_CET [openHABian] Adding openHAB scheme to multitail… OK
2020-10-26_11:03:31_CET [openHABian] Preparing openHAB folder mounts under ‘/srv/openhab2-*’… OK
2020-10-26_11:03:36_CET [openHABian] Applying miscellaneous system settings… OK
2020-10-26_11:03:36_CET [openHABian] Installing Samba… OK
2020-10-26_11:04:10_CET [openHABian] Setting up Samba network shares… OK
2020-10-26_11:04:11_CET [openHABian] Setting up Samba service… OK
2020-10-26_11:04:13_CET [openHABian] Applying file permissions recommendations… OK
2020-10-26_11:04:14_CET [openHABian] Installing Frontail prerequsites (NodeJS)… OK
2020-10-26_11:04:38_CET [openHABian] Installing openHAB Log Viewer (frontail)… OK
2020-10-26_11:04:58_CET [openHABian] Configuring openHAB Log Viewer (frontail)… OK
2020-10-26_11:04:58_CET [openHABian] Setting up openHAB Log Viewer (frontail) service… OK
2020-10-26_11:04:59_CET [openHABian] Adding an openHAB dashboard tile for ‘frontail’… OK
2020-10-26_11:04:59_CET [openHABian] We’ve detected you’re using the 8GB model of the RPi4. It is known to not work with ZRAM.2020-10-26_11:04:59_CET [openHABian] Skipping ZRAM install as requested.2020-10-26_11:04:59_CET [openHABian] Beginning Mail Transfer Agent setup… CANCELED (no configuration provided)
2020-10-26_11:04:59_CET [openHABian] Setting up automated SD mirroring and backup… CANCELED (no configuration provided)
2020-10-26_11:04:59_CET [openHABian] Cleaning up… OK
2020-10-26_11:05:12_CET [openHABian] Execution of ‘openhabian-config unattended’ completed.
2020-10-26_11:05:12_CET [openHABian] Waiting for openHAB to become ready on openHABianDevice… OK
2020-10-26_11:05:12_CET [openHABian] First time setup successfully finished. Rebooting your system!
2020-10-26_11:05:12_CET [openHABian] After rebooting the openHAB dashboard will be available at: http://openHABianDevice:8080
2020-10-26_11:05:12_CET [openHABian] After rebooting to gain access to a console, simply reconnect using ssh.

This is what happened when I tried to uninstall ZRAM

[17:41:58] openhabian@openHABianDevice:~$ sudo openhabian-config
2020-11-05_17:44:26_CET [openHABian] Checking for root privileges… OK
2020-11-05_17:44:26_CET [openHABian] Loading configuration file ‘/etc/openhabian.conf’… OK
2020-11-05_17:44:26_CET [openHABian] openHABian configuration tool version: [stable]v1.6-880(769ea17)
2020-11-05_17:44:26_CET [openHABian] Checking for changes in origin branch stable… OK
2020-11-05_17:44:39_CET [openHABian] Switching to branch stable… OK
2020-11-05_17:44:49_CET [openHABian] Updating Linux package information… OK
2020-11-05_17:44:49_CET [openHABian] Removing ZRAM service… FAILED (disable service)
This is what happened when I ran sudo systemctl status openhab2.service after rebooting my raspberry pi
[17:51:56] openhabian@openHABianDevice:~$ sudo systemctl status openhab2.service
[sudo] password for openhabian:
Warning: The unit file, source configuration file or drop-ins of openhab2.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
● openhab2.service - openHAB2 instance, reachable at http://openHABianDevice:8080
Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/openhab2.service.d
└─override.conf
Active: activating (start-post) since Thu 2020-11-05 17:51:02 CET; 1min 16s ago
Docs: https://www.openhab.org/docs/
https://community.openhab.org
Process: 676 ExecStartPre=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name “*.rules” -exec /usr/bin/rename.ul .rules .x {} ; (code=exited, status=0/SUCCESS)
Main PID: 683 (java); Control PID: 684 (sleep)
Tasks: 97 (limit: 4915)
CGroup: /system.slice/openhab2.service
├─683 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenhab.l
└─684 /bin/sleep 120

Nov 05 17:51:02 openHABianDevice systemd[1]: Starting openHAB2 instance, reachable at http://openHABianDevice:8080…
lines 1-16/16 (END)

This is what happened when I ran /sbin/ip route get 8.8.8.8

[17:55:52] openhabian@openHABianDevice:~$ /sbin/ip route get 8.8.8.8
8.8.8.8 via 192.168.0.1 dev eth0 src 192.168.0.51 uid 1000
Cache

This is what happened when I ran sudo netstat -tulpe --numeric-ports |grep java

[17:59:26] openhabian@openHABianDevice:~$ sudo netstat -tulpe --numeric-ports |grep java
tcp6 0 0 localhost:36665 [::]:* LISTEN openhab 15984 683/java
tcp6 0 0 [::]:8443 [::]:* LISTEN openhab 16317 683/java
tcp6 0 0 localhost:8101 [::]:* LISTEN openhab 19928 683/java
tcp6 0 0 [::]:5007 [::]:* LISTEN openhab 16324 683/java
tcp6 0 0 [::]:8080 [::]:* LISTEN openhab 16320 683/java
udp6 0 0 [::]:5353 [::]:* openhab 18890 683/java

This is what happened when I reinstalled from scratch on a new SD Card & edited the openhabian.conf file so clonebranch=master, debugmode=maximum, ipv6=disable and zraminstall=disable and ran /boot/first-boot.log

[19:47:05] openhabian@openHABianDevice:~$ /boot/first-boot.log
/boot/first-boot.log: line 3: 2020-08-20_10:48:00_UTC: command not found
/boot/first-boot.log: line 4: 2020-08-20_10:48:00_UTC: command not found
/boot/first-boot.log: line 5: 2020-08-20_10:48:00_UTC: command not found
/boot/first-boot.log: line 6: ++: command not found
/boot/first-boot.log: line 7: ++: command not found
/boot/first-boot.log: line 8: +: command not found
/boot/first-boot.log: line 9: 2020-08-20_10:48:00_UTC: command not found
/boot/first-boot.log: line 10: +: command not found
/boot/first-boot.log: line 11: +: command not found
/boot/first-boot.log: line 12: +: command not found
/boot/first-boot.log: line 13: ++: command not found
/boot/first-boot.log: line 14: ++: command not found
/boot/first-boot.log: line 15: +: command not found
/boot/first-boot.log: line 16: +: command not found
/boot/first-boot.log: line 17: +: command not found
/boot/first-boot.log: line 18: OK: command not found
/boot/first-boot.log: line 19: +: command not found
/boot/first-boot.log: line 20: +: command not found
/boot/first-boot.log: line 21: +: command not found
/boot/first-boot.log: line 22: +: command not found
/boot/first-boot.log: line 23: +: command not found
/boot/first-boot.log: line 24: +: command not found
/boot/first-boot.log: line 25: +: command not found
/boot/first-boot.log: line 26: +: command not found
/boot/first-boot.log: line 27: +: command not found
/boot/first-boot.log: line 28: +: command not found
/boot/first-boot.log: line 29: +: command not found
/boot/first-boot.log: line 30: +: command not found
/boot/first-boot.log: line 31: +: command not found
/boot/first-boot.log: line 32: +: command not found
/boot/first-boot.log: line 33: +: command not found
/boot/first-boot.log: line 34: +: command not found
/boot/first-boot.log: line 35: +: command not found
/boot/first-boot.log: line 36: +: command not found
/boot/first-boot.log: line 37: +: command not found
/boot/first-boot.log: line 38: +: command not found
/boot/first-boot.log: line 39: +: command not found
/boot/first-boot.log: line 40: +: command not found
/boot/first-boot.log: line 41: +: command not found
/boot/first-boot.log: line 42: +: command not found
/boot/first-boot.log: line 43: +: command not found
/boot/first-boot.log: line 44: +: command not found
/boot/first-boot.log: line 45: +: command not found
/boot/first-boot.log: line 46: +: command not found
/boot/first-boot.log: line 47: +: command not found
/boot/first-boot.log: line 48: +: command not found
/boot/first-boot.log: line 49: +: command not found
/boot/first-boot.log: line 50: +: command not found
/boot/first-boot.log: line 51: +: command not found
/boot/first-boot.log: line 52: +: command not found
/boot/first-boot.log: line 53: +: command not found
/boot/first-boot.log: line 54: +: command not found
/boot/first-boot.log: line 55: +: command not found
/boot/first-boot.log: line 56: +: command not found
/boot/first-boot.log: line 57: +: command not found
/boot/first-boot.log: line 58: +: command not found
/boot/first-boot.log: line 59: +: command not found
/boot/first-boot.log: line 60: +: command not found
/boot/first-boot.log: line 61: +: command not found
/boot/first-boot.log: line 62: +: command not found
/boot/first-boot.log: line 63: +: command not found
/boot/first-boot.log: line 64: ++: command not found
/boot/first-boot.log: line 65: ++: command not found
/boot/first-boot.log: line 66: +: command not found
/boot/first-boot.log: line 67: 2020-08-20_10:48:05_UTC: command not found
/boot/first-boot.log: line 68: +: command not found
/boot/first-boot.log: line 69: +: command not found
/boot/first-boot.log: line 70: +: command not found
/boot/first-boot.log: line 71: +: command not found
/boot/first-boot.log: line 72: +: command not found
/boot/first-boot.log: line 73: +: command not found
/boot/first-boot.log: line 74: +: command not found
/boot/first-boot.log: line 75: +: command not found
/boot/first-boot.log: line 76: OK: command not found
/boot/first-boot.log: line 77: +: command not found
/boot/first-boot.log: line 78: +: command not found
/boot/first-boot.log: line 79: ++: command not found
/boot/first-boot.log: line 80: ++: command not found
/boot/first-boot.log: line 81: +: command not found
/boot/first-boot.log: line 82: 2020-08-20_10:48:06_UTC: command not found
/boot/first-boot.log: line 83: +: command not found
/boot/first-boot.log: line 84: OK: command not found
/boot/first-boot.log: line 85: ++: command not found
/boot/first-boot.log: line 86: ++: command not found
/boot/first-boot.log: line 87: +: command not found
/boot/first-boot.log: line 88: 2020-08-20_10:48:06_UTC: command not found
/boot/first-boot.log: line 89: +: command not found
/boot/first-boot.log: line 90: +: command not found
/boot/first-boot.log: line 91: +: command not found
/boot/first-boot.log: line 92: +: command not found
/boot/first-boot.log: line 93: +: command not found
/boot/first-boot.log: line 94: +: command not found
/boot/first-boot.log: line 95: +: command not found
/boot/first-boot.log: line 96: +: command not found
/boot/first-boot.log: line 97: +: command not found
/boot/first-boot.log: line 98: ++: command not found
/boot/first-boot.log: line 99: +++: command not found
/boot/first-boot.log: line 100: +: command not found
/boot/first-boot.log: line 101: +: command not found
/boot/first-boot.log: line 102: +: command not found
/boot/first-boot.log: line 103: +: command not found
/boot/first-boot.log: line 104: +: command not found
/boot/first-boot.log: line 105: OK: command not found
/boot/first-boot.log: line 106: ++: command not found
/boot/first-boot.log: line 107: ++: command not found
/boot/first-boot.log: line 108: +: command not found
/boot/first-boot.log: line 109: 2020-08-20_10:48:06_UTC: command not found
/boot/first-boot.log: line 110: +: command not found
/boot/first-boot.log: line 111: +: command not found
/boot/first-boot.log: line 112: +: command not found
/boot/first-boot.log: line 113: +: command not found
/boot/first-boot.log: line 114: +: command not found
/boot/first-boot.log: line 115: +: command not found
/boot/first-boot.log: line 116: +: command not found
/boot/first-boot.log: line 117: +: command not found
/boot/first-boot.log: line 118: +++: command not found
/boot/first-boot.log: line 119: ++: command not found
/boot/first-boot.log: line 120: +: command not found
/boot/first-boot.log: line 121: +: command not found
/boot/first-boot.log: line 122: +: command not found
/boot/first-boot.log: line 123: OK: command not found
/boot/first-boot.log: line 124: ++: command not found
/boot/first-boot.log: line 125: ++: command not found
/boot/first-boot.log: line 126: +: command not found
/boot/first-boot.log: line 127: ++: command not found
/boot/first-boot.log: line 128: ++: command not found
/boot/first-boot.log: line 129: +: command not found
/boot/first-boot.log: line 130: 2020-11-05_17:56:41_UTC: command not found
/boot/first-boot.log: line 131: +++: command not found
/boot/first-boot.log: line 132: ++: command not found
/boot/first-boot.log: line 133: +: command not found
/boot/first-boot.log: line 134: ++: command not found
/boot/first-boot.log: line 135: ++: command not found
/boot/first-boot.log: line 136: +: command not found
/boot/first-boot.log: line 137: +: command not found
/boot/first-boot.log: line 138: OK: command not found
/boot/first-boot.log: line 139: ++: command not found
/boot/first-boot.log: line 140: +: command not found
/boot/first-boot.log: line 141: +: command not found
/boot/first-boot.log: line 142: ++: command not found
/boot/first-boot.log: line 143: +: command not found
/boot/first-boot.log: line 144: ++: command not found
/boot/first-boot.log: line 145: ++: command not found
/boot/first-boot.log: line 146: +: command not found
/boot/first-boot.log: line 147: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 148: +: command not found
/boot/first-boot.log: line 149: FAILED: command not found
/boot/first-boot.log: line 150: ++: command not found
/boot/first-boot.log: line 151: ++: command not found
/boot/first-boot.log: line 152: +: command not found
/boot/first-boot.log: line 153: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 154: +: command not found
/boot/first-boot.log: line 155: +: command not found
/boot/first-boot.log: line 156: FAILED: command not found
/boot/first-boot.log: line 157: ++: command not found
/boot/first-boot.log: line 158: ++: command not found
/boot/first-boot.log: line 159: +: command not found
/boot/first-boot.log: line 160: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 161: ++: command not found
/boot/first-boot.log: line 162: ++: command not found
/boot/first-boot.log: line 163: +: command not found
/boot/first-boot.log: line 164: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 165: +: command not found
/boot/first-boot.log: line 166: +: command not found
/boot/first-boot.log: line 167: +: command not found
/boot/first-boot.log: line 168: ++: command not found
/boot/first-boot.log: line 169: ++: command not found
/boot/first-boot.log: line 170: +: command not found
/boot/first-boot.log: line 171: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 172: +: command not found
/boot/first-boot.log: line 173: 2020-11-05_17:56:42_UTC: command not found
/boot/first-boot.log: line 174: +: command not found
/boot/first-boot.log: line 175: +: command not found
/boot/first-boot.log: line 176: +: command not found
/boot/first-boot.log: line 177: +: command not found
/boot/first-boot.log: line 178: +: command not found
/boot/first-boot.log: line 179: +: command not found
/boot/first-boot.log: line 180: +: command not found
/boot/first-boot.log: line 181: +: command not found
/boot/first-boot.log: line 182: +: command not found
/boot/first-boot.log: line 183: +: command not found
/boot/first-boot.log: line 184: +: command not found
/boot/first-boot.log: line 185: ++: command not found
/boot/first-boot.log: line 186: ++: command not found
/boot/first-boot.log: line 187: ++: command not found
/boot/first-boot.log: line 188: ++: command not found
/boot/first-boot.log: line 189: ++: command not found
/boot/first-boot.log: line 190: ++: command not found
/boot/first-boot.log: line 191: ++: command not found
/boot/first-boot.log: line 192: ++: command not found
/boot/first-boot.log: line 193: ++: command not found
/boot/first-boot.log: line 194: ++: command not found
/boot/first-boot.log: line 195: ++: command not found
/boot/first-boot.log: line 196: +: command not found
/boot/first-boot.log: line 197: +: command not found
/boot/first-boot.log: line 198: +: command not found
/boot/first-boot.log: line 199: +: command not found
/boot/first-boot.log: line 200: +: command not found
/boot/first-boot.log: line 201: +: command not found
/boot/first-boot.log: line 202: +: command not found
/boot/first-boot.log: line 203: +: command not found
/boot/first-boot.log: line 204: +: command not found
/boot/first-boot.log: line 205: +: command not found
/boot/first-boot.log: line 206: +: command not found
/boot/first-boot.log: line 207: +: command not found
/boot/first-boot.log: line 208: +: command not found
/boot/first-boot.log: line 209: +: command not found
/boot/first-boot.log: line 210: +: command not found
/boot/first-boot.log: line 211: +: command not found
/boot/first-boot.log: line 212: +: command not found
/boot/first-boot.log: line 213: +: command not found
/boot/first-boot.log: line 214: +: command not found
/boot/first-boot.log: line 215: +: command not found
/boot/first-boot.log: line 216: +: command not found
/boot/first-boot.log: line 217: +: command not found
/boot/first-boot.log: line 218: +: command not found
/boot/first-boot.log: line 219: +: command not found
/boot/first-boot.log: line 220: ++: command not found
/boot/first-boot.log: line 221: +: command not found
/boot/first-boot.log: line 222: +: command not found
/boot/first-boot.log: line 223: +: command not found
/boot/first-boot.log: line 224: +: command not found
/boot/first-boot.log: line 225: +: command not found
/boot/first-boot.log: line 226: +: command not found
/boot/first-boot.log: line 227: ++: command not found
/boot/first-boot.log: line 228: ++: command not found
/boot/first-boot.log: line 229: +: command not found
/boot/first-boot.log: line 230: 2020-11-05_17:56:48_UTC: command not found
/boot/first-boot.log: line 231: +: command not found
/boot/first-boot.log: line 232: +: command not found
/boot/first-boot.log: line 233: cp:: command not found
/boot/first-boot.log: line 234: +: command not found
/boot/first-boot.log: line 235: +: command not found
/boot/first-boot.log: line 236: +: command not found
/boot/first-boot.log: line 238: $’\E[90’: command not found
/boot/first-boot.log: line 238: 01m$: command not found
/boot/first-boot.log: line 238: 49: command not found
/boot/first-boot.log: line 238: 00m: command not found
/boot/first-boot.log: line 239: +: command not found
/boot/first-boot.log: line 240: net.ipv6.conf.all.disable_ipv6: command not found
/boot/first-boot.log: line 241: net.ipv6.conf.default.disable_ipv6: command not found
/boot/first-boot.log: line 242: net.ipv6.conf.lo.disable_ipv6: command not found
/boot/first-boot.log: line 243: +: command not found
/boot/first-boot.log: line 244: +: command not found
/boot/first-boot.log: line 245: OK: command not found
/boot/first-boot.log: line 246: +: command not found
/boot/first-boot.log: line 247: +: command not found
/boot/first-boot.log: line 248: +: command not found
/boot/first-boot.log: line 249: +: command not found
/boot/first-boot.log: line 250: ++: command not found
/boot/first-boot.log: line 251: ++: command not found
/boot/first-boot.log: line 252: +: command not found
/boot/first-boot.log: line 253: 2020-11-05_17:56:48_UTC: command not found
/boot/first-boot.log: line 254: +: command not found
/boot/first-boot.log: line 255: +: command not found
/boot/first-boot.log: line 256: +: command not found
/boot/first-boot.log: line 257: +: command not found
/boot/first-boot.log: line 258: +: command not found
/boot/first-boot.log: line 259: OK: command not found
/boot/first-boot.log: line 260: +: command not found
/boot/first-boot.log: line 261: +: command not found
/boot/first-boot.log: line 262: +: command not found
/boot/first-boot.log: line 263: +: command not found
/boot/first-boot.log: line 264: ++: command not found
/boot/first-boot.log: line 265: ++: command not found
/boot/first-boot.log: line 266: +: command not found
/boot/first-boot.log: line 267: 2020-11-05_17:57:00_UTC: command not found
/boot/first-boot.log: line 268: ++: command not found
/boot/first-boot.log: line 269: ++: command not found
/boot/first-boot.log: line 270: ++: command not found
/boot/first-boot.log: line 271: ++: command not found
/boot/first-boot.log: line 272: ++: command not found
/boot/first-boot.log: line 273: ++: command not found
/boot/first-boot.log: line 274: ++: command not found
/boot/first-boot.log: line 275: ++: command not found
/boot/first-boot.log: line 276: ++: command not found
/boot/first-boot.log: line 277: ++: command not found
/boot/first-boot.log: line 278: ++: command not found
/boot/first-boot.log: line 279: ++: command not found
/boot/first-boot.log: line 280: ++: command not found
/boot/first-boot.log: line 281: ++: command not found
/boot/first-boot.log: line 282: ++: command not found
/boot/first-boot.log: line 283: +: command not found
/boot/first-boot.log: line 284: OK: command not found
/boot/first-boot.log: line 285: +: command not found
/boot/first-boot.log: line 286: +: command not found
/boot/first-boot.log: line 287: +: command not found
/boot/first-boot.log: line 288: +: command not found
/boot/first-boot.log: line 289: +: command not found
/boot/first-boot.log: line 290: +: command not found
/boot/first-boot.log: line 291: +: command not found
/boot/first-boot.log: line 292: +: command not found
/boot/first-boot.log: line 293: +: command not found
/boot/first-boot.log: line 294: +: command not found
/boot/first-boot.log: line 295: +: command not found
/boot/first-boot.log: line 296: +: command not found
/boot/first-boot.log: line 297: +: command not found
/boot/first-boot.log: line 298: +: command not found
/boot/first-boot.log: line 299: +: command not found
/boot/first-boot.log: line 300: +: command not found
/boot/first-boot.log: line 301: +: command not found
/boot/first-boot.log: line 302: +: command not found
/boot/first-boot.log: line 303: +: command not found
/boot/first-boot.log: line 304: +: command not found
/boot/first-boot.log: line 305: +: command not found
/boot/first-boot.log: line 306: +: command not found
/boot/first-boot.log: line 307: +: command not found
/boot/first-boot.log: line 308: +: command not found
/boot/first-boot.log: line 309: +: command not found
/boot/first-boot.log: line 310: +: command not found
/boot/first-boot.log: line 311: +: command not found
/boot/first-boot.log: line 312: +: command not found
/boot/first-boot.log: line 313: +: command not found
/boot/first-boot.log: line 314: +: command not found
/boot/first-boot.log: line 315: +: command not found
/boot/first-boot.log: line 316: +: command not found
/boot/first-boot.log: line 317: +: command not found
/boot/first-boot.log: line 318: +: command not found
/boot/first-boot.log: line 319: +: command not found
/boot/first-boot.log: line 320: +: command not found
/boot/first-boot.log: line 321: +: command not found
/boot/first-boot.log: line 322: +: command not found
/boot/first-boot.log: line 323: +: command not found
/boot/first-boot.log: line 324: +: command not found
/boot/first-boot.log: line 325: +: command not found
/boot/first-boot.log: line 326: +: command not found
/boot/first-boot.log: line 327: +: command not found
/boot/first-boot.log: line 328: +: command not found
/boot/first-boot.log: line 329: +: command not found
/boot/first-boot.log: line 330: +: command not found
/boot/first-boot.log: line 331: +: command not found
/boot/first-boot.log: line 332: +: command not found
/boot/first-boot.log: line 333: ++: command not found
/boot/first-boot.log: line 334: +: command not found
/boot/first-boot.log: line 335: +: command not found
/boot/first-boot.log: line 336: +: command not found
/boot/first-boot.log: line 337: +: command not found
/boot/first-boot.log: line 338: ++: command not found
/boot/first-boot.log: line 339: ++: command not found
/boot/first-boot.log: line 340: +: command not found
/boot/first-boot.log: line 341: +: command not found
/boot/first-boot.log: line 342: +: command not found
/boot/first-boot.log: line 343: +: command not found
/boot/first-boot.log: line 344: +: command not found
/boot/first-boot.log: line 345: +: command not found
/boot/first-boot.log: line 346: +: command not found
/boot/first-boot.log: line 347: ++: command not found
/boot/first-boot.log: line 348: ++: command not found
/boot/first-boot.log: line 349: +: command not found
/boot/first-boot.log: line 350: 2020-11-05_17:57:00_UTC: command not found
/boot/first-boot.log: line 351: +: command not found
/boot/first-boot.log: line 352: +: command not found
/boot/first-boot.log: line 353: +: command not found
/boot/first-boot.log: line 354: +: command not found
/boot/first-boot.log: line 355: +: command not found
/boot/first-boot.log: line 356: +: command not found
/boot/first-boot.log: line 357: +: command not found
/boot/first-boot.log: line 359: $’\E[90’: command not found
/boot/first-boot.log: line 359: 01m$: command not found
/boot/first-boot.log: line 359: 49: command not found
/boot/first-boot.log: line 359: 00m: command not found
/boot/first-boot.log: line 360: +: command not found
/boot/first-boot.log: line 361: +: command not found
/boot/first-boot.log: line 362: ++: command not found
/boot/first-boot.log: line 363: +: command not found
/boot/first-boot.log: line 364: syntax error near unexpected token Europe/Berlin' /boot/first-boot.log: line 364: OK (Europe/Berlin)’

When I ran /usr/local/bin/FireMotD –version I got
[19:49:59] openhabian@openHABianDevice:~$ /usr/local/bin/FireMotD --version
FireMotD v12.05.191019

I ran sudo /usr/local/bin/FireMotD -S & sudo /usr/local/bin/FireMotD --theme Gray

[19:54:21] openhabian@openHABianDevice:~$ sudo /usr/local/bin/FireMotD -S
[sudo] password for openhabian:
[19:55:25] openhabian@openHABianDevice:~$ sudo /usr/local/bin/FireMotD --theme Gray
###############################################################################
############### openHABianDevice ############################################
###############################################################################

Ip = 192.168.0.51

Release = Raspbian GNU/Linux 10 (buster)

Kernel = Linux 5.4.51-v7l+

Platform = Raspberry Pi 4 Model B Rev 1.4

Uptime = 0 day(s). 0:2:35

CPU Usage = 0% avg over 4 cpu(s) (4 core(s) x 1 socket(s))

CPU Load = 1m: 0.73, 5m: 0.57, 15m: 0.24

Memory = Free: 7.12GB (92%), Used: 0.61GB (8%), Total: 7.73GB

Swap = Free: 0.09GB (100%), Used: 0.00GB (0%), Total: 0.09GB

Root = Free: 11.36GB (82%), Used: 2.34GB (18%), Total: 14.32GB

Updates = 16 apt updates available.

Sessions = 0 session(s)

Processes = 134 running processes of 32768 maximum processes

###############################################################################

When I ran ip route get 8.8.8.8 | head -1 | grep -Po ‘(?<=src )(\d{1,3}.){4}’ | xargs I got this output
[19:56:22] openhabian@openHABianDevice:~$ ip route get 8.8.8.8 | head -1 | grep -Po ‘(?<=src )(\d{1,3}.){4}’ | xargs
192.168.0.51

So the IP address is now showing and I can access the online dashboard at the link http://192.168.0.51:8080/start/index but can’t be accessed at http://openhabiandevice:8080/