Closed c-o-m-m-a-n-d-e-r closed 1 year ago
Could please add a debug log for when you open the admin page? The field should get filled in correctly after the admin page requests the current list of serial ports from ioBroker - maybe something is broken there.
of course ... can deliver on monday ... atm at the train ... tomorrow late back home.
thanks for looking in!
i'm little bit confused ... is there any information i can filter at ? switched to debug but only see message debugs from my meters... nothing from the interface itself ... or is there something special to do to get admin interface debug log ?
thanks
There should be a few messages when actually open the admin interface of the adapter because it queries some information from it
Am 5. Juni 2023 11:09:18 MESZ schrieb Paul @.***>:
i'm little bit confused ... is there any information i can filter at ? switched to debug but only see message debugs from my meters... nothing from the interface itself ... or is there something special to do to get admin interface debug log ?
thanks
-- Reply to this email directly or view it on GitHub: https://github.com/lvogt/ioBroker.wireless-mbus/issues/133#issuecomment-1576420800 You are receiving this because you commented.
Message ID: @.***>
hi, i double checked, the only thing i found is this
2023-06-07 07:21:11.829 - info: admin.0 (1908) ==> Connected system.user.admin from ::ffff:192.168.10.21 2023-06-07 07:21:12.230 - info: wireless-mbus.0 (17058) List of port: [] 2023-06-07 07:21:15.264 - info: wireless-mbus.0 (17058) List of port: [] 2023-06-07 07:21:18.309 - info: wireless-mbus.0 (17058) List of port: [] 2023-06-07 07:21:18.807 - info: admin.0 (1908) <== Disconnect system.user.admin from ::ffff:192.168.10.21
all the other debug stuff is message receiving and decrypting etc.
Interesting. Do you use the new "serial over tcp socket" feature? Or what do you have configured as your serial port?
I have a fix, but right now it is not published to npm (or tagged). Are you able to test the current master branch or do you need me to publish it I would rather wait for your feedback and publish it afterwards to npm.
no, i only mapped that device via : /dev/im871a:/dev/im871a and also in the ENV with : USBDEVICES=/dev/im871a /dev/im871a is just via serial mapped to /dev/ttyUSB0
i can test from master branch ... gimme a second
I can report success ... with 0.9.1 it is working as expected.
Thanks a lot!
Thanks for reporting and testing :) I published 0.9.1 to npm now as well.
Fixed with 0f679b9e92dc747bc8d34983d0b9580e673e421e
Describe the bug
when open the instance for edit the interface entry is always empty
To Reproduce
Steps to reproduce the behavior: just edit the installed instance. everything is setup and also working, but after revisiting the instance settings, the interface /dev/... is empty (but still works when i dosen't change anything
Expected behavior
the configured interface should apear as path
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
Additional context![Bildschirmfoto 2023-06-02 um 10 06 36](https://github.com/lvogt/ioBroker.wireless-mbus/assets/815885/b7e46d61-ca10-47bb-a802-2bda5bfaee35)
Add any other context about the problem here.