Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

esp-ebus V6.1 with no signal #81

Open
docava65 opened this issue Oct 15, 2024 · 6 comments
Open

esp-ebus V6.1 with no signal #81

docava65 opened this issue Oct 15, 2024 · 6 comments

Comments

@docava65
Copy link

Hi Daniel,

I still have the disconnecting issue. Regardles of the configuration changes made in ebusd I get always no signal and disconnections,
This is the latest ebusd config: EBUSD_OPTS="--scanconfig -d enh:192.168.129.53:3335 -p 3335 --latency=20000"

doca@RPi3:/etc/default $ sudo systemctl status ebusd.service
● ebusd.service - ebusd, the daemon for communication with eBUS heating systems.
Loaded: loaded (/lib/systemd/system/ebusd.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-10-15 13:04:22 CEST; 33min ago
Process: 5823 ExecStart=/usr/bin/ebusd $EBUSD_OPTS (code=exited, status=0/SUCCESS)
Main PID: 5825 (ebusd)
Tasks: 4 (limit: 779)
CPU: 1.144s
CGroup: /system.slice/ebusd.service
└─5825 /usr/bin/ebusd --scanconfig -d enh:192.168.129.53:3335 -p 3335 --latency=20000

Oct 15 13:04:22 RPi3 systemd[1]: Starting ebusd.service - ebusd, the daemon for communication with eBUS heating systems....
Oct 15 13:04:22 RPi3 systemd[1]: Started ebusd.service - ebusd, the daemon for communication with eBUS heating systems..

doca@RPi3:/var/log $ sudo lsof -i -P -n | grep LISTEN
vncserver 628 root 11u IPv6 4093 0t0 TCP *:5900 (LISTEN)
vncserver 628 root 12u IPv4 4094 0t0 TCP *:5900 (LISTEN)
sshd 677 root 3u IPv4 14842 0t0 TCP *:22 (LISTEN)
sshd 677 root 4u IPv6 14844 0t0 TCP *:22 (LISTEN)
cupsd 2576 root 6u IPv6 66542 0t0 TCP [::1]:631 (LISTEN)
cupsd 2576 root 7u IPv4 66543 0t0 TCP 127.0.0.1:631 (LISTEN)
ebusd 5825 root 5u IPv4 104852 0t0 TCP *:3335 (LISTEN)

doca@RPi3:/etc/default $ ping 192.168.129.53
PING 192.168.129.53 (192.168.129.53) 56(84) bytes of data.
64 bytes from 192.168.129.53: icmp_seq=1 ttl=255 time=92.8 ms
64 bytes from 192.168.129.53: icmp_seq=2 ttl=255 time=115 ms
64 bytes from 192.168.129.53: icmp_seq=3 ttl=255 time=35.7 ms
64 bytes from 192.168.129.53: icmp_seq=4 ttl=255 time=58.4 ms
--- 192.168.129.53 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 35.749/75.498/115.050/30.557 ms

doca@RPi3:/etc/default $ sudo ebusctl info
version: ebusd 23.3.23.3
update check: OK
device: 192.168.129.53:3335, TCP
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

doca@RPi3:/etc/default $ sudo ebusctl find -V
broadcast datetime = no data stored [ZZ=fe, passive read]
broadcast error = no data stored [ZZ=fe, passive read]
broadcast id = no data stored [ZZ=fe, passive read]
broadcast id = no data stored [ZZ=any, active read]
broadcast signoflife = no data stored [ZZ=fe, passive read]
memory eeprom = no data stored [ZZ=any, active read]
memory ram = no data stored [ZZ=any, active read]

doca@RPi3:/etc/default $ sudo ebusd -f -d 192.168.129.53:3335
2024-10-15 13:34:57.471 [bus notice] device status: transport opened
2024-10-15 13:34:57.471 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 192.168.129.53:3335, TCP
2024-10-15 13:34:58.170 [bus notice] bus started with own address 31/36
2024-10-15 13:34:58.170 [network error] unable to start TCP server on port 8888: error 98
2024-10-15 13:34:58.170 [bus error] device status: transport closed
2024-10-15 13:34:58.171 [bus notice] device invalid
2024-10-15 13:35:03.308 [bus notice] device status: transport opened
2024-10-15 13:35:03.308 [bus notice] re-opened 192.168.129.53:3335
....

I've also tried with different PWM values and have tried different firmware versions, same status: no signal

async mode: true
software serial mode: true
uptime: 176483 ms
last_connect_time: 275 ms
reconnect_count: 1
rssi: -58 dBm
free_heap: 158784 B
reset_code: 3
loop_duration: 50 us
max_loop_duration: 3966427 us
version: v7.1
nbr arbitrations: 0
nbr restarts1: 0
nbr restarts2: 0
nbr lost1: 0
nbr lost2: 0
nbr won1: 0
nbr won2: 0
nbr late: 0
nbr errors: 0
pwm_value: 180

After a while, the device can't be contacted

doca@RPi3:/var/log $ sudo ebusctl info
error connecting to localhost:8888

I don't understand why it tries to connect to port 8888, I've included the 3335 port in ebusd???
Could you please also tell me what is the D8 led is actually doing, I see it stays still for almost 8 seconds then off and again lit for 8 sec.?

Hopefully the above information give you hints on what is going on. I think, this device is malfunctioning, see the image below.
image0
@danielkucera
Copy link
Owner

Hi @docava65 ,

can you try to power the device from usb adapter? Don't forget to remove the jumper as described in readme.
Also, can you please provide ebusd logs? Please attach them as txt file.

@docava65
Copy link
Author

docava65 commented Oct 15, 2024 via email •
edited
Loading

@danielkucera
Copy link
Owner

Can you please provide log with all options specified here?
https://github.com/danielkucera/esp-arduino-ebus?tab=readme-ov-file#nothing-helps-i-need-support

@docava65
Copy link
Author

docava65 commented Oct 15, 2024 via email

@danielkucera
Copy link
Owner

Hi @docava65 ,

it looks like the log didn't get forwarded to the issue. Can you upload it manually?

@docava65
Copy link
Author

docava65 commented Oct 16, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danielkucera @docava65