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.

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

failure to change network settings due to "unknown setting name" #17421

Closed
3 tasks done
spaceserpent opened this issue Jul 27, 2023 · 8 comments
Closed
3 tasks done

failure to change network settings due to "unknown setting name" #17421

spaceserpent opened this issue Jul 27, 2023 · 8 comments
Labels

Comments

@spaceserpent
Copy link

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

received an error stating "Can't update config on enp1s0: device: unknown setting name" when attempting to cahnge network settings: IP, DNS, gateway, etc. Persist despite reboots, resets of network connections, etc.

Currently running HA OS on generic linux

image

Describe the behavior you expected

Expected to change network settings without issue

Steps to reproduce the issue

  1. have pre-existing network config
  2. attempt to change network config of an interface
  3. error recieved
    ...

What version of Home Assistant Core has the issue?

HA OS

What was the last working version of Home Assistant Core?

2023.8.0b1

In which browser are you experiencing the issue with?

Firefox DEV 116.0b8 (64-bit)

Which operating system are you using to run this browser?

Windows 11

State of relevant entities

Issue occurred despite use of different browsers and client devices i.e. android, edge, iphone, etc.

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@spaceserpent
Copy link
Author

occurring regardless of auto network config or selecting the interface

@silamon
Copy link
Contributor

silamon commented Jul 28, 2023

Could you explain the steps to reproduce this? More specificly if you are using the supervisor screen or the network screen. Or perhaps try if it works in any of those.

I thought it would be due to my change in this page but the reviewing takes way longer these days and the pull request I thought would be it is still to be reviewed and not in the August beta.

@silamon
Copy link
Contributor

silamon commented Jul 28, 2023

Still not sure the cause of this, but it might be a supervisor issue seeing there are changes there too: home-assistant/supervisor#4416

@spaceserpent
Copy link
Author

as you might expect, it occurs with any attempted change to the network interface, i.e. from static to auto, IPs, etc.

looks like occurring both in CLI and UI-- let me know if I should try a different CLI method.

image

@silamon
Copy link
Contributor

silamon commented Jul 29, 2023

Thank you for testing further, I would suggest to open an issue on the supervisor repository: https://github.com/home-assistant/supervisor.

@spaceserpent
Copy link
Author

thank you, see after for newly written SU ticket, home-assistant/supervisor#4459

@silamon
Copy link
Contributor

silamon commented Aug 8, 2023

This can be closed since the issue was due to a supervisor change.

Copy link

github-actions bot commented Nov 6, 2023

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 6, 2023
@karwosts karwosts closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants