Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason

[jh2k19]

[hacki11]

Can you enable debug logging and also try to remove the 20200.x values to see if it is related to that? What versions do you use? BSB adapter and BSB firmware?

[jh2k19]

ioBroker BSB-LAN-Adapter, Version 0.3.1 BSB-LAN, Version 3.3.2-20231115201023

If i delete the Values 2020x.x in ioB Objects and delete the 20200.1/20201.1 in ioB Adapter Config there is no more warning for Adapter Objects loke 2020x.x

But if i delete only the Values 2020x.x in ioB Objects it will be created automaticaly new but the debug Log shows the warn again as before.

debug on and deleted 20200.1/20201.1 in Adapter Config 1.txt

debug on and deleted 20200.1/20201.1 in Adapter Config and in BSB-LAN Webinterface set BME280 sensors from 2 to 0 2.txt

Hope that helps to find the issue. Let me know what i can do to help to fix the problem. Thanks

[hacki11]

I guess it is also related to https://github.com/hacki11/ioBroker.bsblan/issues/238

Currently support for .x or !x is not implemented so the behaviour is currently undefined. Support for that needs to be added within the adapter.

[hacki11]

Can you try if the following will fix your issue? Install from custom github: https://github.com/hacki11/ioBroker.bsblan/tree/multidimensional-id

I have sanitized the . in the key so it won't create a folder which should be an object.

[jh2k19]

Now i've installed BSB-LAN Version: 3.3.4-20240301014054 from freetz and ioB BSB-LAN Adapter V 0.3.2 Here is the result:

1.txt

[hacki11]

Despite the warning it looks better, doesn't it? Is the data coming as expected for you? Then I just need to verify why the warning is popping up here.

[jh2k19]

Unfortunately no. Previously the data came correctly despite the warning status in the log. Now the current values ​​are no longer fetched.

[jh2k19]

One more note. This issue was about the constant and independent termination and restart of the adapter. According to the log, this problem is still there. The adapter always shows this. It always turns red and green. Can we rename or combine issues #219 and #239.

[hacki11]

https://forum.iobroker.net/topic/53414/zigbee-instanz-scheduled-restart/5

The log line "scheduled restart" looks like you configured the adapter to be restarted regularly. Can you check that? I guess the adapter should then run stable.

Regarding the value I need to verify

[hacki11]

I have updated the branch with support for ID.x, can you check if this works for you now?

Responses of parameters with .0 are not containing .0 anymore, therfor a matching was not possible. Responses of parameters with .1 and higher are containing the .x.

This special behavior was needed to be implemented. The result is, that the .0 is also omitted within iobrokers object view.

219 should be also fixed with this

[jh2k19]

Great work. Everything works as expected. No warning messages and no errors. And yes, scheduled restart was configured. I don't know if that was me. I'm sorry I didn't see that. Thank you very much for the great support

1.txt

[hacki11]

Thank you for bringing this to the table so I could improve the adapter. I will make a release soon

[hacki11]

solved in v0.3.2