-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature requests: Elero roller shutter #35
Comments
Hi @CsL-007 |
My gateway is V6plus. Able to move blind up,down, stop with html command. Elero blinds have no percentage, just open or close status, but it never worked me. When use /cmd?XC_FNC=SendSC&type=ER&data=0101 get this response: {"XC_SUC": {}}. |
Could you give me the calls for up, down and stop? And could you execute |
Here is what I'm able to get: GET:/cmd?XC_FNC=SendSC&type=ER&data=0101&auth=************ -> HTTP:304 Down: {"type":"ER","sid":"0E","adr":"01","state":"100B","ts":{"m":"65191B4C"}} GET:/cmd?XC_FNC=getStates&at=47ca3b7de2be372bdee71fe63cabd65e -> HTTP:200 |
* elero with ER added Feature request #35
@CsL-007 Could you try out the https://github.com/oelison/ioBroker.mediola-gateway/tree/elero_roller_shutter |
No blind find, get this error: mediola device rejected the request: [object Object] |
Could you execute |
command?XC_FNC=getstates&auth=mypassword work only, Mediola api document write this parameter not the user and password combo |
I will add this as an option, too. |
* elero with ER added * AIO GW V5+ and all start with AIO GW added Feature request #35
* elero with ER added * AIO GW V5+ and all start with AIO GW added Feature request #35
* elero with ER added * AIO GW V5+ and all start with AIO GW added Feature request #35
elero roller shutter fixes feature request #35
https://github.com/oelison/ioBroker.mediola-gateway/tree/authParam |
No further request open, maybe solved. |
Hi!
Like your work, maybe can you add Elero blind support too?
Here is what Elero calls looks like:
{"type":"ER","sid":"10","adr":"03","state":"1002","ts":{"m":"6516B9E4"}}
Thanks in advance!
The text was updated successfully, but these errors were encountered: