Status Update
Comments
an...@google.com <an...@google.com> #2
Thank you for posting.
For further checking, kindly provide the expected exact location/coordinate of the provided address Lot 19 1RN, Mosa, Middlesex, ON, CA
.
mx...@googlemail.com <mx...@googlemail.com> #3
the totally *irrelevant* responses that geocoder returns. Why does the
Maps application understand that Camden is a township in Kent county, but
the geocoder gives me CAMDEN, DELAWARE, USA! When I look for similar
locations in Michigan I always get a meaningful response. It does not
throw in a location with a similar name in FRANCE!
I am not fussy about the exact location/coordinates returned as long as it
is in the vicinity. If you choose to ignore leading parts that you do not
understand until you find something in your database that is meaningful,
fine by me. Why, when I have supplied both a valid township and county
name do you sometimes return only the County as a response. And sometimes
when I ask about a location in Canada the very first result is the STATE OF
CALIFORNIA!
The Google geocoder handles urban addresses, but not rural addresses.
Rural properties in both Canada and the United States are generally
identified by lot, concession, and township, like this example. In the
case of Mosa township street names and numeric addresses were only added
about 20 years ago in order to facilitate fire department service, because
these locations are serviced by the Canadian equivalent of RFD. 1st Range
North of Longwoods Road in Mosa township
<
Middlesex county, Ontario is such a concession. I have provided a link to
the record in my database that describes that concession. I believe that
you are entitled by the contract that I have for the use of your API to
copy any location and boundary information that I have added for a
location. I have even provided an alternative interface by which you can
obtain this information as a JSON document
tool is documented at
example to get all locations in my database that contain the string '1RN,
Mosa' ask for
I am not expecting you to return a perfect response. For example if
geocoder had returned your record for all of Mosa township, I would have
been happy. But instead in most cases with this sort of location I get
either the whole county, or the province of Ontario, or the STATE OF
CALIFORNIA!
The ideal response to my request for the specific location is
.
As I indicated I understand that you are entitled to copy any additional
information that I have accumulated using your geocoder and Maps
interfaces. It is fine with me if others benefit. There are almost 30,000
locations in my database.
On Mon, 18 Dec 2023 at 01:30, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
mx...@googlemail.com <mx...@googlemail.com> #4
island of South Uist, in the Outer Hebrides, which is administered as part
of the county of Invernessshire in Scotland. No matter what I entered into
geocoder it kept returning the the ENTIRE COUNTY OF INVERNESSSHIRE. This
is not a helpful response. I was forced to waste time looking up Bornish
south uist on Google Maps and then copy and paste the coordinates from the
URL. Please fix this!
On Mon, 18 Dec 2023 at 01:30, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
mx...@googlemail.com <mx...@googlemail.com> #5
Thank you for the information.
Please note that there are many reasons why Geocoding returns the incorrect/unexpected result like when the data is not available on our end or the data is problematic. This is why we are requesting users to provide additional information like the sample of the request where the issue is encountered with the expected correct result including the official source that can validate that it is correct.
Another reason for inaccurate results can be because of the request itself like when there are ambiguous or incorrect addresses. For this, kindly visit and check
mx...@googlemail.com <mx...@googlemail.com> #6
code. My code worked fine with the geocoder v3.4 interface. It always
gave me a useful answer. You then started WHINING that I was accessing an
obsolete interface and demanded that I upgrade to the current interface.
You then *BROKE* the geocoder interface, from my point of view explicitly
to force me to rewrite all of my code to some NEW service which you are
springing on me! I do not appreciate your laying the blame for this
problem on your customers! Why should I have to *rewrite* all of my code
just because you invented a new product?
Please fix your geocoder interface rather than force me to rewrite all of
my code!
I demand an apology and an assurance that you are not going to avoid
treating your customers in this shady manner.
On Thu, 21 Dec 2023 at 02:00, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
mx...@googlemail.com <mx...@googlemail.com> #7
let url = "
`?input=${locn}` +
`&types=(regions)` +
`&key=${googleKey}`;
let options = {}; // are there other
headers I should be sending?
options.errorHandler = function() {alert('script Google Places
Autocomplete not found')}; // this alert always pops
HTTP.get(url, // this is the AJAX library from
"Javascript: the Definitive Guide" by David Flanagan
gotLocs,
options);
but this is rejected by my Firefox browser as a "Cross-Origin Request
Blocked: The Same Origin Policy disallows reading the remote resource at
<
(Reason: CORS header 'Access-Control-Allow-Origin' missing). Status code:
200."
I do not understand all of the description of this error, but it seems for
me to send a request to
'Access-Control-Allow-Origin' header from your site. I am using the same
client key that I use for geocoder from My Project 64975. What do I have
to do to get you to send that header?
I have enabled the Places API in Google. Still doesn't work and contrary
to the explanation I do not see the Places API in my dashboard.
This would seem to me to be a very common error but I cannot find ANY WEB
SITE that even mentions it.
On Thu, 21 Dec 2023 at 02:00, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
an...@google.com <an...@google.com> #8
a JSON response, but that JSON response is useless if I cannot process it
in my Javascript code. I have to be able to make requests from my
JavaScript code, which is running on my web server at 23.111.69.250. I DO
NOT WANT YOUR PLACES LIBRARY. Is there some configuration tool to
authorize these requests? I have read through the Identity and Access
Management API and I am completely baffled as to whether it will permit me
to include an authentication token in my requests.
On Thu, 21 Dec 2023 at 02:00, <buganizer-system@google.com> wrote:
--
James Cobban jamesalancobban@gmail.com
911-500 Springbank Dr,
London, ON, CANADA
N6J 4G6
1-226-504-7603
mx...@googlemail.com <mx...@googlemail.com> #9
But I have another third-party device in my flat and connected to google home.
It has a button to toggle its state. If I open my google-home-app and watch the state..
It turns from on to off (for example) when I am pressing the button!
No refreshs, nothing pressed.. just the app opened!
So, it must be possible somehow.. and I would like to do that too with our own integration! ;)
an...@google.com <an...@google.com> #10
Can you please confirm the device type and the device trait for your other third-party device? Is the device type also "Outlet" and the is trait "OnOff" available for that other device?
mx...@googlemail.com <mx...@googlemail.com> #11
That particular device is a "Switch" and has "OnOff" too for sure. :)
I already tried to switch from "outlet" to "swtich", but my device acts the same way though :/
an...@google.com <an...@google.com> #12
Hi,
As I mentioned earlier GHA relies on both Report State and query. So, the issue is probabaly generating from your query implementation & my recommendation is to check your implementation in the Google Home Graph Viewer (
mx...@googlemail.com <mx...@googlemail.com> #13
Thanks!
Yeah, I already double-checked that. Please, we are not dumb..
Let me tell you again all the insides:
If I am using this tool:
I can see the home-graph state to be "on: false".. Then I use my hardware-switch to toggle the state.. Click refresh and the state is "on: true". The report-state call gets a 200 answer, the home-graph state is updated.. so everything is fine, right?
Lets make a check to the report-state thingy! We did it, well done.. ;D
So.. lets go back to the query api.. If I start the google-home-app .. it will call our endpoint and executes a query.. I can see that in my logs! AND the google-home-app is showing the right state. Fine for now. If I test my implementation, all tests are green. so.. query works fine and as expected!
BUT after reporting the new state back, there is no query executed by the google-home-app nor by any google-service??!
The google-home-app has an old state.. BUT if I long-click the device to get into its detail-view OR pull down the google-home-app view to refresh (and execute a query).. the state is fine!
SO: both APIs are working fine, separately but not together :(
mx...@googlemail.com <mx...@googlemail.com> #14
any news on this topic? we would like to push this to prod-readyness! :) the question is: how can we enforce the GHA to execute a query?
mx...@googlemail.com <mx...@googlemail.com> #15
it started working for no reason. no software changes since weeks! and today it worked.. what changed, my device. Pixel 7.. vs pixel 3 before.. I will re-test it tomorrow using my old phone! :)
mx...@googlemail.com <mx...@googlemail.com> #16
nope, not the device.. I guess I found it..
if someone finds this thread..
it only works IF the device is part of any room.. it won't update if it is just under "other devices connected to your account" .......... :(
got damn it! :D
an...@google.com <an...@google.com>
he...@google.com <he...@google.com> #17
Hi,
This issue will be marked as Won’t Fix (Obsolete) since it has been more than one month without any response. If it’s necessary, please feel free to reopen it. Thanks.
de...@gmail.com <de...@gmail.com> #18
mx...@googlemail.com <mx...@googlemail.com> #19
no idea how to reopen it. there is no button or so..
did you try to add the device to a room?
ha...@google.com <ha...@google.com>
pa...@googlemail.com <pa...@googlemail.com> #20
ha...@google.com <ha...@google.com> #21
Thank you for informing me of the issue. I have reopened it.
Would you be able to try uninstalling and reinstalling the Google Home App to see if the issue still persists?
If it does, could you kindly provide us with the following information so that we can further investigate and help you debug the issue:
- Version of the Google Home App:
- Version of Android:
- Version of the Google App:
- SYNC response:
Thank you.
pa...@googlemail.com <pa...@googlemail.com> #22
I removed the Google Home App.
The issue still persists. On both test devices.
Android Device
Version of the Google Home App: 2.65.1.6
Version of Android: 12
Version of the Google App: ?
SYNC response: added to file
iOS Device
Version of the Google Home App: 2.66.106
Version of iOS: 16.3.1
Version of the Google App: ?
SYNC response: added to file
ha...@google.com <ha...@google.com> #23
Dear Developer,
After reviewing your SYNC response, we have identified some errors in the response that need to be addressed. Errors:
data.payload.devices[0].attributes.availableThermostatModes should be an array
data.payload.devices[0].attributes.availableThermostatModes should be an array
We recommend that you update your SYNC response accordingly and re-check if the issue persists.
To validate your SYNC response, we suggest using the
If the issue still persists even after you have fixed the error, please let us know and we will be happy to assist you further. Thank you.
ha...@google.com <ha...@google.com> #24
This issue will be marked as Won’t Fix (Obsolete) since it has been more than one month without any response. If it’s necessary, please feel free to reopen it. Thanks.
Stay up-to-date on the latest news, features, and requirements from Google Home, subscribe here:
pa...@googlemail.com <pa...@googlemail.com> #25
The issue in the app is still there.
he...@google.com <he...@google.com>
ha...@google.com <ha...@google.com> #26
Dear Developer,
We'd like to ask you to try using the Smart Home Playground tool to try to reproduce the issue. The Smart Home Playground tool is a great way to test your device implementation and make sure that it's working correctly on Google Home.
To get started with the Smart Home Playground tool, please visit the following link:
Smart Home Playground tool
Smart Home Playground tool can be used in the following scenario:
- Designing a Smart Home device.
- Before fully implementing a device, use Smart Home Playground to test how the device types & traits will behave on Google Home App, Google Hubs and Google Assistant.
- Testing your device implementation is correct.
- Smart Home Playground is the golden standard of “how” your Smart Home device should work on Google Home. Provided you have completed the design your your device with a valid SYNC JSON (if you are unsure, use the
).SYNC Data validator tool
- Smart Home Playground is the golden standard of “how” your Smart Home device should work on Google Home. Provided you have completed the design your your device with a valid SYNC JSON (if you are unsure, use the
Please share with us the results of your reproduction with the Smart Home Playground. It will enable us to better understand the situation and assist you effectively.
Thank you.
ha...@google.com <ha...@google.com> #27
This issue will be marked as Won’t Fix (Obsolete) since it has been more than one month without any response. If it’s necessary, please feel free to reopen it. Thanks.
Stay up-to-date on the latest news, features, and requirements from Google Home, subscribe here:
Description
I am playing around with the nodejs packages
googleapis
andactions-on-google
.I am stuck reporting the state, which changed without googles note, so that google keeps in sync! Sadly this does not work. I am using this method:
homegraph.devices.reportStateAndNotification()
.described here:https://developers.google.com/assistant/smarthome/reference/rest/v1/devices/reportStateAndNotification
The call is fine, I am getting a correct answer and everythign seems fine. Except that my google home app does not update the state.
I have another thirdparty-device which has a button to toggle the state, this works fine. So the app has no bug, it must be on my side..
I am wondering if this "feature" does only work in production and not during the test phase?