Open xxLexanixx opened 1 year ago
You missed something out of the setup. Start at the beginning and try again.
I've gone through the instructions a second time. Unfortunately, there is still no sensor to be seen.
sudo systemctl status isp-rpi-reporter.service
● isp-rpi-reporter.service - RPi Reporter MQTT Client/Daemon Loaded: loaded (/opt/RPi-Reporter-MQTT2HA-Daemon/isp-rpi-reporter.service; enabled; vendor preset: enabled) Active: activating (auto-restart) since Wed 2022-10-19 09:03:33 CEST; 359ms ago Docs: https://github.com/ironsheep/RPi-Reporter-MQTT2HA-Daemon Process: 2212329 ExecStart=/usr/bin/python3 -u /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py (code=killed,> Main PID: 2212329 (code=killed, signal=PIPE) Status: "Oct 19 09:03:31 - * MQTT connection established." CPU: 929ms
You'll need to adjust your config.ini to provide the hostname and domain correctly and/or fix why your system doesn't know its own hostname.
The rpi-{hostname} says to me that this is not configured well, nor automatically being discovered.
OK. I checked my config. next to sensor name is: sensor name = Pascal Somfy Pascal-Somfy is the hostname of the Pi Is it correct?
@xxLexanixx Please check the following: (on your RPi)
hostname -f
to see if it also reports your hostnameifconfig
to see if it has either a wired or wireless connection with an IP addressuname -a
report?Also, what OS image are you running?
pi@Pascal-Somfy:~ $ hostname -f Pascal-Somfy
pi@Pascal-Somfy:~ $ uname -a Linux Pascal-Somfy 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
pi@Pascal-Somfy:~ $ ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.178.22 netmask 255.255.255.0 broadcast 192.168.178.255 inet6 fe80::6f03:4658:6fb4:a71d prefixlen 64 scopeid 0x20 ether b8:27:eb:75:03:a1 txqueuelen 1000 (Ethernet) RX packets 6397020 bytes 1243808343 (1.1 GiB) RX errors 3 dropped 0 overruns 0 frame 0 TX packets 6611067 bytes 4842818537 (4.5 GiB) 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
OS is Debian.
Wow, I'm not seeing anything wrong with this so far.
Can you get MQTT Explorer and look at what is being seen by MQTT.
You can paste that here (there's a copy-to-clipboard function. A JSON Pretty Print website can format the values copied to the clipboard before you paste them here.
sorry that I'm just now replying. What do I have to do exactly to get the JSON file?
i think i have the problem found. the service restart every seconds.
here the error: 1659 ExecStart=/usr/bin/python3 -u /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py (code=killed, signal=PIPE)
@xxLexanixx can you please report more of the error you see? The line you posted is insufficient for determining the cause.
THere should be more lines after that
pi@Pascal-Somfy:~ $ systemctl status isp-rpi-reporter.service ● isp-rpi-reporter.service - RPi Reporter MQTT Client/Daemon Loaded: loaded (/opt/RPi-Reporter-MQTT2HA-Daemon/isp-rpi-reporter.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2023-05-02 08:33:10 CEST; 3 weeks 1 days ago Docs: https://github.com/ironsheep/RPi-Reporter-MQTT2HA-Daemon Process: 10126 ExecStart=/usr/bin/python3 -u /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py (code=killed, signal=TERM) Main PID: 10126 (code=killed, signal=TERM) Status: "May 02 08:33:09 - * MQTT connection established." CPU: 1.069s
May 02 08:33:08 Pascal-Somfy systemd[1]: Starting RPi Reporter MQTT Client/Daemon... May 02 08:33:10 Pascal-Somfy systemd[1]: Started RPi Reporter MQTT Client/Daemon. May 02 08:33:10 Pascal-Somfy systemd[1]: Stopping RPi Reporter MQTT Client/Daemon... May 02 08:33:10 Pascal-Somfy systemd[1]: isp-rpi-reporter.service: Succeeded. May 02 08:33:10 Pascal-Somfy systemd[1]: Stopped RPi Reporter MQTT Client/Daemon. May 02 08:33:10 Pascal-Somfy systemd[1]: isp-rpi-reporter.service: Consumed 1.069s CPU time.
Unfortunately, no sensors are displayed to me. Why is that? I don't see anything in the home assistant either. Why is [that?