Closed Felixw1077 closed 8 months ago
@Felixw1077 Thank you for your detailed issue report. Although I also have a VBUS/USB adpter running, I can not reproduce your problem, probably because I do not run it in a docker container. So I assume something in your environment must cause the problem. First I would like to ask some questions to understand your environment better:
According to your logfile, you have been running another vbus adapter (iobroker.resol v1.1.6) before starting myvbus v0.2.5 in the same container on the same serial port. Did the iobroker.resol adapter update its objects correctly? Did you start the iobroker.resol adapter again after stopping the myvbus adapter and did the resol adapter update its objects still correctly?
Unfortunately your logfile does not show what happened after myvbus received the first complete data frame. Did the follow-up-frames also contain data or were they all empty []? If they were not empty, was all data in all frames identical? Have there been some additional log messages after the first successfull frame e.g. regarding disconnects or reconnects ? EDIT: Just saw in the logfile, that it contains the answers to these questions already.
Have been running earlier versions of myvbus in the same environment successfully and did this issue show only with v0.2.5 ?
Dear Jens
Thanks for getting back to me and sorry that I did not reply as I usually do but I was travelling a lot on business. Last weekend I digged into the issue much deeper and I found out that there might be a problem with another installed docker container (homematic) that blocks the ttyACM0 interface after the first start of your (or the resol) vbus adapter.
I will run some more tests and will report back on my findings.
@Felixw1077 Did you make progress on your investigation? It would be interesting for me and other users of the adapter if you would share your findings here. Anyway, please let me know if the problem is solved for you so that it can be closed.
@pdbjjens Dear Jens, Thanks for reaching out to me again. I traced the error down to the installation of the raspberryMatic which turns off the ttyACM0 on the main system so that it is not available to any other docker installations (interestingly it is only this connection as others e.g. ttyUSB0 are still available). I also checked with them for an explaination but did not receive any answer so far (haven't logged it as a bug but a question) Maybe I check back with them opening an incident. The solution I for the moment is now: Install it on 2 separate systems. I might try to make a clean and manual install of raspberryMatic and check what will happens if I do not disable the port. Let me know if we should close and reopen the thread once I have done the manual install
@Felixw1077 Thank you for your update on this issue. Although currently it seems to me that this is not an issue of the myvbus adapter, I will leave this issue open until you come back with further findings. Just as a reminder, that there still is an investigation ongoing.
Hi, @Felixw1077 Since there has been no feedback from you since some time, I am closing this issue now. Please feel free to reopen it, if you find that myvbus has an issue. Please be aware that I just released a new version 0.3.0.
Describe the bug
Adapter is configured as standard and /dev/ttyACM0 is made availabe through portainer for docker. First time start of the adapter the data objects are created but afterwards no update of any value will happen
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Updated values (esp. "System time" as it logs every min)
Screenshots & Logfiles
iobroker.2023-04-12.log.gz
Versions:
Additional context
N/A