Skip to content

arest has no documented option for defining port to send html command to. If I append it to the ip address the module receives a command, but then on and off commands fail to work. #37860

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

Open
rkgladney opened this issue Mar 7, 2025 · 1 comment
Labels
Stale The PR had no activity for quite some time, and is marked as Stale

Comments

@rkgladney
Copy link

Feedback

Documentation for arest appears to say that pins: can be used as an name, however pins: throws an error message saying not in dictionary.
Documentation does not offer an entry for identifying port (i.e., 80) for switch to recognize and respond.
If I append the port id to the resource (i.e., http://192.168.1.184/digital/12/1:80) The module turns on, but never responds to a switch on or switch off.
If I enter http://192.168.1.184:80 as resource then nothing happens.

URL

https://github.com/home-assistant/home-assistant.io/issues?q=is:issue%20is:open%20sort:updated-desc%20label:%22integration:%20arest%22

Version

2025.3

Additional information

No response

@rkgladney rkgladney changed the title arest has no documented option for defining port to send html command to. If I append it to the ip address the module receives a command, but then the body-on and body-off commands fail to work. arest has no documented option for defining port to send html command to. If I append it to the ip address the module receives a command, but then on and off commands fail to work. Mar 7, 2025
Copy link

github-actions bot commented May 6, 2025

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.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has 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 The PR had no activity for quite some time, and is marked as Stale label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale The PR had no activity for quite some time, and is marked as Stale
Projects
None yet
Development

No branches or pull requests

1 participant