All:
This topic has appeared before with no answers and for some reason been de-listed (not a valid question). The Nest Device Access Console states to ask questions on this forum so I will try again:
I have followed all the steps to get a Nest Doorbell to publish events/messages to Google pub/sub (i.e. https://developers.google.com/nest/device-access/get-started) and yet nothing is being pushed to the topic (i.e. flat line in pub/sub subscription window). Is there something obvious I'm missing, not read, regarding support for the Nest doorbell and pub/sub?
In short, it would be nice if a Google representative/expert could weigh in on this topic and provide some insight.
Thanks,
Rob.
Probably something on Google's part. At my home the doorbell is working again as well :-) So you probably didn't misread anything and were just part of some sort of glitch.
Problem
If you choose to use avoidArea, exclueCountries or avoidLinks (and probably some more that I wasn't able to test) in your request router enforces fastest route mode.
Given is route from Poland to Germany.
Official testing client: http://refclient.ext.here.com/
First request (no avoids, no excludes, mode:shortest) was:
https://route.api.here.com/routing/7.2/calculateroute.json?app_code=pxIXqdtgOSwQDXSDfjLQpw&app_id=cgZPrYfgRePXzXC3PbBp&jsonattributes=41&language=en-us&legattributes=le&maneuverattributes=po,ti,pt,ac,di,fj,ix&metricsystem=metric&mode=shortest;car&routeattributes=sh&waypoint0=geo!stopOver!53.49012,18.80973&waypoint1=geo!stopOver!53.61957,12.43167
This resulted in a quite straightforward route like below.
If we add now any country exclusion (e.g. GBR, CHE, CZE) the route is now routed via motorways like fastest mode was enforced.
https://route.api.here.com/routing/7.2/calculateroute.json?app_code=pxIXqdtgOSwQDXSDfjLQpw&app_id=cgZPrYfgRePXzXC3PbBp&avoidseasonalclosures=false&excludecountries=CHE,GBR,CZE&jsonattributes=41&language=pl-pl&legattributes=le&maneuverattributes=po,ti,pt,ac,di,fj,ix&metricsystem=metric&mode=shortest;car&routeattributes=sh,zo&waypoint0=geo!stopOver!53.49012,18.80973&waypoint1=geo!stopOver!53.61957,12.43167
EDIT 1 BEGIN
I checked out the new routing API and results are similar:
Without avoids:
https://route.ls.hereapi.com/routing/7.2/calculateroute.json?apiKey={API_KEY}=41&language=en-us&legattributes=le&maneuverattributes=po,ti,pt,ac,di,fj,ix&metricsystem=metric&mode=shortest;car&routeattributes=sh&waypoint0=geo!stopOver!53.49012,18.80973&waypoint1=geo!stopOver!53.61957,12.43167
With avoids:
https://route.ls.hereapi.com/routing/7.2/calculateroute.json?apiKey={API_KEY}&avoidseasonalclosures=false&excludecountries=CHE,GBR,CZE&jsonattributes=41&language=pl-pl&legattributes=le&maneuverattributes=po,ti,pt,ac,di,fj,ix&metricsystem=metric&mode=shortest;car&routeattributes=sh,zo&waypoint0=geo!stopOver!53.49012,18.80973&waypoint1=geo!stopOver!53.61957,12.43167
On a sidenote, http://refclient.ext.here.com/ doesn't have option to test new API
EDIT 1 END
Question
Why is it happening? Is it designed behavior? If not, when can we expect this to be fixed?
Ok, I've got an answer for you from engineering. I'm rewording a bit so any mistakes/confusion blame me, not him. :)
So yes, the API here is ignoring your request to use shortest.
Quote from developer: Specifically in this case, when using "shortest" mode and requesting additional "avoids", routes more than 300km or so are not "good". It does not fall back to "fastest" mode but another mode where "fastest" route shape has more of an influence.
You mentioned wanting to avoid tolls, be aware that you can ask for that option when calling the API, so that may be a solution for you.
I hope this helps a bit, and thank you for being patient.
I have a Symfony project, that is now being tested on live system, and I'm using the delivery_address to prevent sending email to real recipients.
I needed also some exceptions for this, so I have used a very nice delivery_whitelist option (like here).
Right now, the white-listed emails are going both to original target and to delivery_address, but I'd like them to get sent only to the original, white-listed address.
Is that possible in some way?
As #userfuser suggested, here is my slightly altered comment as an answer:
Since your requirement contradicts the semantics of the configuration options, your only option seems to be adding some logic to your mail sending component. I am sure that you will be able to extract the white list and other options programatically so you can build your edge case.
I'm wondering if anyone has any form of solution for this? I've been googling for some time now and can't seem to find a solution.
Is there a way to either remove Hubot from Slacks default #general channel or have him so he mutes himself and doesn't respond to commands in the channel directly, perhaps instead private messages the person? I want to implement my bot into my organization but I want to avoid situation where he floods general chat by responding to a command.
Did you try to "/kick hubot" command on the #general channel?
It should work like for any other users
I've briefly looked around for an answer to this and it doesn't seem to be doable, but figured I'd ask on here. I am about to launch a survey on qualtrics, but would prefer, if at all possible, to customize the URL address for my survey. I would like to do this only because I plan on printing out a few advertisements to display around campus, and requiring people to then go back to their computers and type in a lengthy and complex web address is not exactly ideal.
Cheers
Use a url shortening service like goo.gl.