Hi all,
Has anyone contacted geotogether recently about enabling the API. I had a response yesterday saying “This is not a service we provide.”
Hi all,
Has anyone contacted geotogether recently about enabling the API. I had a response yesterday saying “This is not a service we provide.”
sorry - I anonymised my PublicationObjectStagingIds=nnnn
substitute your area to get the correct CV for your area.
I agree it is fiddly to find it, so I understand that it does not make sense to add it to your integration.
I used the multiscrape intergration in HACS. You may need to modify it if using the scrape integration
in my configuration.yaml
file
multiscrape: !include hacs_multiscrape.yaml
in my hacs_multiscape.yaml
- resource: "http://mip-prd-web.azurewebsites.net/CustomDataDownload\
?LatestValue=true\
etc
etc
Thanks, it was the fact that it was multiscrape that I was missing. It works for me now - very neat.
I’ve emailed customer services to enable my account for api access, I was getting the 401 error, they replied with, as others suggested, with “ This is not a service we provide I am afriad.” and then closed the ticket.
Any suggestions?
I had a working Geo Home integration using the (paid for) WiFi module on the back of the Geo Trio II IHD, and getting Geo to fix something to allow me to get a code for the Geo Home app.
This was working from around November (2022) until 22nd Dec (2022) after which I appear to have had no readings in either HA or the Geo Home app. I’m guessing this is linked with the problems other folk are having setting this up but thought I’d report it here anyway.
Does anyone have a currently working Geo Home integration?
I’m thinking of splashing out for the Hildebrand Glow IHD with local MQTT feature (if it really works – Geo Home is also supposed to work!), but reluctant to do so after buying the WiFi module for the existing IHD.
The Geo Together API works for me currently. It did get disconnected from my meter at some point, and this messed up the data I was getting.
I recommend exploring the API using Postman. That really helped me troubleshoot things, and ultimately get the issue resolved with the Geo support.
My guess is that if the Geo Together app works for you the API should also.
It works for me too, and I think you are right @dunxd - the apis are almost certainly what powers the app
I actually found from another forum post using curl I can login to the api and retrieve system info etc
So I don’t know why when I put my email address and password into the configuration and restart ha that all sensors are unknown and there are 401 errors in the logs.
Any ideas on the beta way to troubleshoot?
The code is here;
You could try hard coding the values from your curl command and so on to see what the difference is
Thanks, I’ll do some digging later.
Hi,
FYI: I’m receiving a 401 error from custom_components/geo_home/geohome.py:115
When I test the same APIs used in the integration in postman I can login and retrieve the device details.
APIs I have tested:
Any pointers what else I can debug?
Thanks, appreciate your time.
Are you sure your authentication details are entered correctly? The code is just doing a post in python with those details. There’s not much to it as you can see
Hi,
The issue was that the initial username I entered was incorrect and sticky. Even when I updated it ,from the geo home configuration dialogue, it remained at the incorrect value I had set when I first installed the integration. I checked this by adding some debug to the async_auth function in geohome.py
I removed the geohome integration and then reinstalled it. This then fixed the problem.
Cheers
I wonder if I have coded something wrong there then. It should update. I’ve logged issue Updating username doesn't work · Issue #12 · mmillmor/geo_home · GitHub for that. If anyone has more info, feel free to add it there.
Thanks - This fixed my issue
In case anyone else hits the issue, can you confirm how you fixed it?
Thanks
Martin
I removed the device from home assistant and added again. Looks like while updating the username and password appears to work as the value displayed if you go back to edit, it doesn’t actually fix what’s being used by the API. Removal fixes this
Possibly something like trying to fetch a token, failing, but then not replacing that token when the login details are changed
Anyone else having issues since the update was carried out a few weeks ago?
I’ve tried everything I can think off. I’ve removed the plugin from HACS and made sure there was no install directory, then rebooted. I know the login and password combination is fine as I have the Geo app on my phone which uses the same Credentials.
I keep on getting
[%key:common::config_flow::error::unknown%]
I’ve even tried on a second temporary install and get the same.
Hi, not sure if anyone is monitoring this thread, but having loaded the Geo integration and entered the same credentials as the Geo app, I just don’t seem to be able to pull any data. No matter which entity I select, all I get is…
Any clues would be welcome
UPDATE on this. I completely removed the integration , re-installed it and made sure I got the credentials right, first time.
I then initially got the “statistics_not_defined” message, waited a couple of hours and bingo! now getting data.
I know someone reported that if you got the credentials wrong, correcting them didn’t seem to work. I definitely got them wrong, first time around, and got no joy after correcting them.
Hope this is helpful to other folk.
In the past when people have had issues logging it, it has generally been that their password was set wrong. To correct it, you need to uninstall and re-install I’m afraid (updating it in the options doesn’t work at the moment)