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

TP-Link JetStream enable is not being sent #3271

Open
bdg-robert opened this issue Sep 16, 2024 · 2 comments
Open

TP-Link JetStream enable is not being sent #3271

bdg-robert opened this issue Sep 16, 2024 · 2 comments

Comments

@bdg-robert
Copy link
Contributor

I'm running into an issue with enable not working for an S5500-48GP4XF. They identify as JetStream for the model, but the commands in the model file are the same as those used to pull the configuration. From what I see in the debugging, the post-login command is nil - no enable command is sent, though it does try to send the password.

I see that the post-login block was edited in PR #2796 - could this be the cause? Any thoughts, @mirackle-spb?

@skiera6
Copy link

skiera6 commented Sep 21, 2024

Can you send your config? From what I can see in the source code, it checks if enable is set to true in your configuration. If it is, it sends the enable command. If enable is set to another value, it sends that value instead.

So, if the enable variable is not set correctly or is returning nil, that would explain why the enable command isn't being sent. Double-check your entry and make sure the enable value is properly defined and accessible in your model. If you're still having trouble, sharing your configuration might help identify the issue further.

@eabeukes
Copy link

I had the same issue across several TP-Link switches. Reverting the change in PR #2796 fixes the problem. My install was working before this commit, a recent update to Oxidized then introduced this fix and no config was captured. The new code does not actually send "enable" to the switch, according to the debug logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants