Domoticz

At the end of an earlier message I already indicated that probably the more pragmatic solution would be to redistribute the functions of this 'problematic' Raspberry-setup over other Raspberries, combined with a serious clean-up.
Shifting the SD-card to a Raspberry3A+ is a pragmatically simple, functional way out.
Has wlan0 only, no eth0, and is fast. Adressing-structure remains same, both for IP and for devices.
Eth0-function lost, but further looks like really minimal effort, without loss of data.
Just checking that applications refer to correct accessible, active IP-adresses and URLs.
After that redistribution then this 'problematic' Raspberry3B+ is 'clean & empty' for new applications, incl. use of eth0.

Conclusion:
a pity that no simple solution could be found to activate eth0, but enough time has been spent to search.
Better now start that redistribution & clean-up .......

Thanks for the support during the search for a solution!

Side-effect (rather obvious) from 'Lessons-Learned' as indicated in the previous messages.

If you have an RPI-B or later with both LAN /eth0 and Wifi/wlan0 (= dual-channel communication), then
you are able to communicate with both LAN and Wifi.

If you have a processor with either LAN, or Wifi, you have no path to make direct connection between LAN and Wifi, but
you can 'misuse' the processors with dual-channel communication to assist you:
such processor can read a device in 1 processor LAN and copy/upload to another processor at WiFi, or reverse.

Sometimes have to admit that an idea is not working .....

Had a setup in mind with cabled LAN in IP-range 192.168.1.x and WLAN in IP-range 192.168.0.y, aiming a a 'simple & good' separation of groups of clients.
As described in previous messages, initially it worked, but after some time ran into problems with the RPI-3Bs loosing the connection to cabled eth0;
in past year not once but with several RPI-3Bs.
Considering the found practical solution, not a hardware problem, but perhaps some aspect in the software coming up during use of such setup?

Have 'surrendered' to a configuration in which cabled LAN-clents and WLAN-clients are in the same IP-range:
then both eth0 and wlan0 come into action and crosscommunication is very easy!
Except shifting of the LAN-cabling to another router as part of clean-up, most effort to tune all (W)LAN-related software to suite the common IP-range.

Is sshd configured on port 22? And is sshd listening on all interfaces/listenaddress?
Check: /etc/ssh/sshd_config

@AllesVanZelf

According to experiences, the 'eth0-problem' as described in the thread has no relation to ssh.

But eager to learn:
what line to check in the indicated config-file /etc/ssh/sshd_config?

In /etc/ssh.sshd_config
set
ListenAddress 192.168.1.6
ListenAddress 192.168.0.185

Do you get a ping result if you ping 192.168.1.6 from another computer?
Could you make this rpi get an address via dhcp for testing? Or could you change the ipaddress?