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

Devices return {"Command":"Unknown"} in reply to cmnd/sonoffs/topic, but return proper topic when issued via cmnd/<topic>/topic #5145

Closed
jziolkowski opened this issue Feb 7, 2019 · 6 comments
Labels
question Type - Asking for Information

Comments

@jziolkowski
Copy link
Contributor

Same problem across versions 6.3, 6.4.1 and 6.4 dev bins.

Other commands work, like fulltopic, restart, statuses etc. Didn't try all of them, of course, so maybe other commands don't work as well.

@jziolkowski
Copy link
Contributor Author

oh, tested it with another user, same result.

@ascillato2
Copy link
Collaborator

Hi, I can also confirm this behaviour.

@ascillato2 ascillato2 added the bug Type - Confirmated Bug label Feb 7, 2019
@arendst arendst removed the bug Type - Confirmated Bug label Feb 8, 2019
@arendst
Copy link
Owner

arendst commented Feb 8, 2019

As designed. It's a feature!

Background:
The group command (sonoffs in this case) does not allow commands like hostname to execute as it would mean that several devices would receive the same hostname which will probably make your network a bit unstable.

The same is true for some other commands although this 'group ban' has been lifted from most command over the last year.

To find out which commands are currently under control of this feature search the source code for grpflg

@ascillato2
Copy link
Collaborator

Closing this issue as it has been answered.

Support Information

See Wiki for more information.
See Chat for more user experience.

@ascillato2 ascillato2 added the question Type - Asking for Information label Feb 8, 2019
@jziolkowski
Copy link
Contributor Author

Ok, I get it. Could this "ban" mean they're just read-only in some future revision?

@arendst
Copy link
Owner

arendst commented Feb 8, 2019

Nice idea.

arendst added a commit that referenced this issue Feb 9, 2019
Add status message to former declined group commands (#5145)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Type - Asking for Information
Projects
None yet
Development

No branches or pull requests

3 participants