-
Notifications
You must be signed in to change notification settings - Fork 40
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
[%key:common::config_flow::error::cannot_connect%] #92
Comments
What was the host and port you were using with the old version? I am assuming you used: Its weird you are getting auth error with the hased password so it means its actually connecting. Are there any other logs in the HA logs? (Developer -> Logs) |
I did notice the string was off a while back and forgot to create an issue :( |
Yea the string works for core integration but not for custom, I hope they will support it in the future. I left it cause it still mostly provided the relevant error |
Ah ok |
I have had much the same experience as jjanderson. I was updating from the previous version, followed the instructions on removal and ran into this same error. Tried all the different combinations of port and ip address similar to jjanderson and have been unable to connect. Additionally I have DNS name setup for my controller -- that also doesn't connect. http://IP address:port Nothing works. I have tried the old md5 hashed password, unhashed. For mac address I was using the MAC address of the controller. I looked the code and it looks like this is just used to establish a unique id and not for connectivity? So I also tried just putting some text in there as well. I am running on docker. This was all I could find in my HA logs:
|
Its basically supposed to the same URL you use to open the OpenSprinkler UI. I assume that loads in the browser? I find OS quite finicky when you try to access it using different IP/Hosts. Try rebooting the OS controller and loading the OS UI and then use the same url for the integration. You are right about the mac address, its not used for connectivity so should not be relevant here |
What firmware version are you each on? |
I updated to hass-opensprinkler 1.0.1, restarted HAS, rebooted OpenSprinkler controller. I verified the IP address, can access it directly. I attached to the docker container and verified it can ping the ip as well (this was working pre-1.0.0, so seems unlikely to be connectivity). OpenSprinkler firmware is 2.1.7. |
Pre 1.0.0 the requests library was used...now we use httplib2 and I’m wondering if there’s something more stringent with the request with older firmware (like a missing header or something that was sent by requests perhaps but not httplib2). |
That could be a possibility, but its hard to test without it failing for us. Maybe we can switch to request and test. @hellfire51 @jjanderson are you guys comfortable with python to be able to run the pyopensprinkler module by itself with we created a git branch with some changes to help us test? |
Or maybe reach out privately and give us a temporary password to run some tests.. |
I am not really comfortable with giving access sorry... If you could send me steps, i am happy to help with testing in python... I am running firmware 2.1.8(4) on ospi.. |
Is there an particular reason why you guys have not upgraded to 2.1.9? |
Will try that... |
Could be hardware related as well. I also don’t know when |
I used to get an update notification when new firmware was available. I have now tried updaing the firmware but it does not seem to work... Have logged a ticket here: https://openthings.freshdesk.com/support/tickets/9207 |
Same error |
Upgrading past 2.1.5 Requires modifying (soldering some pins) and having a HW programmer . |
funny, got mine (ospi) to 2.1.8(4)... will wait to hear from Ray as it is not clear to me on the best way forward with the firmware... |
Ok, I think it’s pretty clear there’s some minor difference that’s required in the request for the older firmware. When I get back to my desk I’ll send over some basic curl commands to have you try and we’ll see what happens. |
I too am basically stuck at firmware 2.1.5 due to having version 2.1 hardware. I have the same issue connecting with the new integration. Below are the two errors that are logged in HA while attempting to setup the integration. Hopefully this information is helpful to someone. Logger: backoff Giving up request_http(...) after 3 tries (pyopensprinkler.OpenSprinklerConnectionError: Cannot connect to controller) Logger: custom_components.opensprinkler.config_flow Unexpected exception |
Ok cool. I’ll send send over some curl commands to have everyone to send over the results which should help. |
OK, if everyone could run this it would be helpful:
And subsequently for those that want to attempt hacking the code:
From what I can tell the most simple difference between |
Will this log a password? |
Yes as well as the headers (since the pw is in the path)...cleanse the output before sending it over and/or clean logs as necessary. |
Maybe change it to:
In this case we probably don't need to know the full url. this will not log the password |
I can send a variant that will print it with params before the pw is added in a bit...afk at the moment. |
I pretty-printed the JSON and redacted a few things:
|
@hellfire51 can you try to apply the header portion of the patch above by chance and see what happens? You’ll need to hack the files and the restart hass. |
An update, I have dusted off my old raspberrypi and compiled a few versions of the firmware to test:
But I have included the header change and some better error handling/msgs to the PR above, we will see if that helps. |
I don't understand what it means but I am getting: _* Trying 192.168.1.8:894...
|
@osteospurnum might want to change your password now FYI, make sure you cleanse any output you send over :( I'm mostly after hacking the code below the curl example...need to see what's going on with the response from the integration perspective. |
I think that maybe beyond my pay grade |
I wanted to report back that I upgraded to the latest version of hass-opensprinkler and was able to complete the integration installation now. It discovered my programs and stations. I haven't tried any services yet. |
Nice! Glad we’re getting more coverage. |
Thanks for all your assistance with this yesterday Travis. It was greatly appreciated, still unable to set up the integration but I reckon at the moment I am out of options. I will keep looking and let you know if I find the cause. |
Yeah we need to get some better logging in place for failure scenarios.. |
Why does the MAC address need to be included? Surely a URL or IP address is sufficient? |
The short answer is we need a unique identifier for the device and the HA people don't like url/hostname/ip as that. However we are hoping in the next OpenSprinkler firmware release this will become optional/not required (only required for non-latest firmware) |
Had the same problem on OSPi 2.19 |
Have the same problem. On HAAS I added the integration Opensprinkler via Configuration-Integration-Add and filled in the fields: What am I doing wrong? the capture shows a successfull tcp handshake betwenn HAAS and OSPI, I also get HTTP1.1 200 OK |
I've still got the same problem. |
just wanted to follow up. |
I ran into this same problem today installing opensprinkler on a new HASS instance. In the configuration pop-up I used an EXTERNAL IP:8080 with port forwarding on my router, rather than internal 192.168.xxx.xxx and was able to connect. |
Hi! |
Unfortunately not.
I have still the same problem
… Am 20.11.2021 um 18:51 schrieb nanosonde ***@***.***>:
Hi!
Has this issue been fixed?
Is anybody working on fixing this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Have you tried any of the curl commands mentioned in previous comments? |
I have copied the output as is except for md5 hash of password and the MQTT password. |
If someone is willing I can hop onto the integration slack channel or hass discord and do an interactive debug session. It seems pretty odd the behavior observed :( |
Good news. While analysing the OpenSprinkler UI again, I realized that one of the German Umlaut ("ä") was not correctly shown. I replaced the German Umlaut by its ASCII variant ("ae"). After this change the integration was able to connect and successfully configure itself. BTW: Only now I have realized that this topic is about [%key:common::config_flow::error::cannot_connect%], but I got this one: The questions is how to solve this. How can we make it more robust when it comes to "broken" names/string in Opensprinkler FW?
|
I had the same issue. Running 2.1.9. I tried everything in the IP feild, and could not make it work. But suddenly, it configured, like on the 15th try. I just wrote HTTP://OS LOCAL IP with no port number, my OS pasword, and left eh MAC adress field blank. |
I have solved it now. thanks for the hint.
The problem was related to german characters like ä,ö,ü.
I substituted with ae, oe and ue.
The only problem left is the fact that switches on haas have no effect.
It looks like I have just read access to these entities.
Any idea?
… Am 28.11.2021 um 17:21 schrieb Sleepy81 ***@***.***>:
I had the same issue. Running 2.1.9. I tried everything in the IP feild, and could not make it work. But suddenly, it configured, like on the 15th try. I just wrote HTTP://OS <http://os/> LOCAL IP with no port number, my OS pasword, and left eh MAC adress field blank.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR5Z3VLPR5HE6BDVUVOCHXLUOJJIXANCNFSM4NPLS5GQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Which switches exactly? |
Valves and programs
Best
Markus
… Am 28.11.2021 um 19:21 schrieb Travis Glenn Hansen ***@***.***>:
Which switches exactly?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
You toggle the switch and after a few moments it goes back to the original state? What are your expectations when it is toggled? |
The switch shows state on but is off.
I would expect the button to show off state and to be able to turn it on for the last defined time.
Best
Markus
… Am 28.11.2021 um 23:20 schrieb Travis Glenn Hansen ***@***.***>:
You toggle the switch and after a few moments it goes back to the original state?
What are your expectations when it is toggled?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
The built-in switches do not run the valves/programs, they only enable/disable them. To run a valve/program you must use the services and create your own switches/ui to handle that. Was that the issue is just a problem with expectations? Or did you create custom switches to invoke the services and those are not working? |
Also worked for me. HTTP://xxx.xxx.xxx.xxx |
Just hit this bug, too. Adding a default protocol prefix should be the fix here, but at the very least it should return a more actionable and obvious error message. |
Hi,
I have now deleted all the trace elements of the pre 1.0 version.
I have uninstalled from HACS.
I rebooted
I then re-installed in HACS.
When I try and configure in the integrations, I get [%key:common::config_flow::error::cannot_connect%]
Further info:
I am running OSPI.
My url I have tried is:
Password is the password, but I also tried with the old Hashed password and I got a different error around authentication
Mac address --> I used the mac address of the raspberry pi
Controller name --> Left as is...
The text was updated successfully, but these errors were encountered: