You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
It seems that the network IP functionality for the SystemBinding channel is no longer working as expected. Additionally, defining the network interface appears to be either broken or not possible, causing further issues with configuration. The functionality does not seem to behave as intended under certain circumstances.
Steps to Reproduce:
Attempt to configure the SystemBinding channel with a specific network IP.
Try to define or select a network interface for the channel.
Observe that the network interface cannot be defined correctly or results in an error.
Network-related functionality does not work as expected after the configuration.
Expected Behavior:
The SystemBinding channel should allow the proper definition of a network interface and use the provided network IP without issues.
Actual Behavior:
Defining a network interface is either not possible or results in an error. The network IP functionality is broken, and the expected behavior doesn't occur.
Environment:
Version: OH4.3.2
Network Setup:
br-ae4f57fdeda5
docker0
eth0
lo
veth6ae8b01
vethc80153f
vethe07ef92
vethf7407f2
wlan0
Additional Context:
This issue seems to have started recently or after [mention any recent changes, updates, etc., if applicable]. Logs do not indicate any obvious error, but the behavior deviates from expectations, especially with the inability to define the network interface.
Potential Impact:
This issue could impact systems relying on specific network interfaces and IP configurations for communication, potentially causing disruptions in operations.
Proposed Solution :
Select correct interface for openhab which to show in my case wlan0
The text was updated successfully, but these errors were encountered:
miloit
added
the
bug
An unexpected problem or unintended behavior of an add-on
label
Jan 26, 2025
Did this work in OH 4.3.0 or 4.3.1? What is the last version that worked without problems?
Can't comment for sure but it was okay in oh4.1...in this I moved over to dietpi than I realized it
miloit
changed the title
SystemBinding Channel: Network IP Not Functioning Properly
SystemInfoBinding Channel: Network IP Not Functioning Properly
Jan 26, 2025
I am still not sure I understand your issue. The channels on the SystemInfo binding are dynamic. If the binding detects multiple network interfaces, it should create multiple channel groups (numbered) for each interface, each containing 3 channels (IP, networkName and networkDisplayName). Is that not what you see? So it is a question about picking the right channels in your configuration.
If that is not what you are seeing, please describe in detail what you are doing and provide the error you get.
Description:
It seems that the network IP functionality for the SystemBinding channel is no longer working as expected. Additionally, defining the network interface appears to be either broken or not possible, causing further issues with configuration. The functionality does not seem to behave as intended under certain circumstances.
Steps to Reproduce:
Attempt to configure the SystemBinding channel with a specific network IP.
Try to define or select a network interface for the channel.
Observe that the network interface cannot be defined correctly or results in an error.
Network-related functionality does not work as expected after the configuration.
Expected Behavior:
The SystemBinding channel should allow the proper definition of a network interface and use the provided network IP without issues.
Actual Behavior:
Defining a network interface is either not possible or results in an error. The network IP functionality is broken, and the expected behavior doesn't occur.
Environment:
Version: OH4.3.2
Network Setup:
Additional Context:
This issue seems to have started recently or after [mention any recent changes, updates, etc., if applicable]. Logs do not indicate any obvious error, but the behavior deviates from expectations, especially with the inability to define the network interface.
Potential Impact:
This issue could impact systems relying on specific network interfaces and IP configurations for communication, potentially causing disruptions in operations.
Proposed Solution :
Select correct interface for openhab which to show in my case wlan0
The text was updated successfully, but these errors were encountered: