randyth
-
Posts
294 -
Joined
-
Last visited
Everything posted by randyth
-
Whoa, wait, what?! Is this the email Amazon SPAMs (er, sends) out every week? You better not be pulling my leg. In any case, I would greatly appreciate it if the people who find this skill useful help out my efforts by giving it a positive review here on Amazon's website. (Yes, a shameless plug -- sorry.) It took a good amount of talking to convince Amazon to let this thing loose since, well, it's not exactly the "mass market" type of thing they are used to approving. Good reviews help convince them I'm not just a crazy nerd trying the abuse my access to their notification system. Well, I might be, but I'm a harmless crazy nerd. -Randy
-
Glad I could help.
-
Did you launch the skill yet (that's what triggers the email). And, if so, what did it say? To launch the skill, just say, "Alexa, launch Notify Me." -Randy
-
*UPDATE* This beta test is complete. A big THANKS to everyone who participated. As of March 20, 2018, the skill is now live for everyone. (Hooray!) If you find the skill useful, please do give it a positive review on the Alexa skill store. Positive reviews help support the development of this and other skills like it. Thanks, -Randy
-
Great stuff, Bumbershoot. FWIW, there's a bit of a hidden feature in the ways you can manipulate Alexa's speech, from specifying how she interprets numbers (time, date, telephone number, street address, etc) to the tone and speed of her voice. You can also play short audio files and even make her whisper. See this link for more info: https://developer.amazon.com/docs/custom-skills/speech-synthesis-markup-language-ssml-reference.html#ssml-supported BE WARNED, however. If you don't get the syntax perfectly right, Notify Me will either tell you your accessCode is missing (because your quotes are mismatched, causing an invalid JSON structure) or pretend to send the message but not (because Alexa rejects it at the last minute due to bad syntax). With that warning said, here is an example of how you can make Alexa whisper: {"notification":"Would you like to hear me whisper? <amazon:effect name=\"whispered\">This is me whispering</amazon:effect>","accessCode":"amzn1.ask.account...
-
This is as designed. The Echo's ring glows (usually a light yellow) whenever you have a notification waiting for you.
-
It does appear that curl does not behave the same under Windows as on other platforms (ugh). It looks like Microsoft recommends you use their Invoke-RestMethod instead. Using PowerShell, here is the Invoke-RestMethod command you can use instead of curl: Invoke-RestMethod https://api.notifymyecho.com/v1/NotifyMe -Method POST -Body '{"notification":"Hello World!","accessCode":"ACCESS_CODE"}'
-
Oh, YES! The JSON (you might look that up) body data must be surrounded by curly braces.
-
Yes, though that string might vary slightly for some users. In any case, it is part of the access code.
-
I wish we could just make Alexa emit a notification as well, but Amazon does not officially allow that yet. As it stands now, notifications require some interaction from the user to hear them. As for Windows cURL, it might be a format issue. Is Content-type set to application/json in the header? Could you share the cURL command you are using here, scrubbing the access code from your example, of course.
-
Please do remove both curly braces when replacing {ACCESS_CODE} with your actual access code. I really should simply remove those from the instructions -- they are likely only creating confusion.
-
Spying on the skill's log files, it looks like you're finally in, Teken!
-
90 minutes! Ack! Unfortunately, I'm not sure we can control that (we tell Amazon to post all notifications immediately), but I'll look into our log files to see if there is anything funny going on with that initial call. Hopefully this was a one-time issue that has already cleared itself up.
-
The email will come from from notifyme@notifymyecho.com via amazonses.com. Did you launch the skill ("Alexa, open Notify Me")? If so, what did it tell you? (Note: Enabling the skill does not trigger the email; launching the skill does that.) -Randy
-
By last count, approximately 50% of the beta test pool is from Canada. -Randy
-
Hey Teken, My bad for "cross posting" an inline edit to my initial reply. I have since updated it to say we may have already fixed the Canada issue. We'd love it if you could verify this for us. We recommend you disable and then re-enable the skill to be safe. Thanks, -Randy
-
Interesting. A couple things: Thanks to steveng57, we recently discovered that this initial release does not work in Canada (d'oh!). I think this has been corrected, so please try to launch the skill again (launching the skill is what triggers the email with the access code). If your Alexa device is registered in Canada, you might need to disable and then re-enable the skill to get it working. Did you successfully launch the skill ("Alexa, open Notify Me")? If so, what did it say? Definitely let me know if you can't launch the skill. -Randy
-
Great. Just message me the email address associated with your Amazon account (the one you used to set up your Echo device) and I will email you an invite link. -Randy
-
Hey Memphis2k, Timely request. Please check out my post here about a new skill you might be interested in:
-
*UPDATE* This beta test is complete. A big THANKS to everyone who participated. As of March 20, 2018, the skill is now live for everyone. (Hooray!) If you find the skill useful, please do give it a positive review on the Alexa skill store. Positive reviews help support the development of this and other skills like it. Thanks, -Randy ----------------------- I’m looking for about 10 to 20 ISY owners who are interested in beta testing an Alexa Skill called Notify Me. This skill lets you push notifications to your Alexa device using a simple RESTful API. (See the bottom of this post for an example on how to do this via an ISY Network Resource.) When you send your Alexa a notification, it makes a “bing” sound and its ring glows yellow. To hear your notification, just ask, “Alexa, what are my notifications?” Further details can be found at www.notifymyecho.com If you want to be part of this skill’s ISY beta test, please message me with the email address attached to the Amazon account you used to register your Echo device(s). I will then send you a link you can use to enable the skill. Comments, feedback, and (of course) compliments can be posted to this forum. Using Notify Me with the ISY Notify Me requires at least ISY Firmware Release 4.6.2 or 5.0.11 due to its dependency on SNI support Once you’ve received your access code from Notify Me, you can set up a separate network resource for each message you want to send. Here are the instructions for ISY Firmware 4.6.2: Go to Configuration->Networking->Network Resources Click on Add Give your resource a name, like “Hello World” Click on the new resource’s URL column to edit it Use the following settings: HTTPS POST Host: api.notifymyecho.com Port: 443 Path: /v1/NotifyMe Check Use SNI Set timeout(ms) to at least 2,000 Mode: Raw Text Headers: Change Content-Type to application/json Body: enter the following... {"notification":"Hello World", "accessCode":"ACCESS_CODE"} ...replacing ACCESS_CODE with the access code Notify Me emailed you. Click Update; then click Save Click the Save button found at the bottom of the main window. Select the name of the Resource from the list and then click Test
-
Just installed the Schlage Connect today on three doors. Installation was a breeze, though I had trouble adding the first lock as a Z-Wave device to my ISY. Disconnecting and reconnecting the battery on the lock and trying again did the trick. The last two locks were added on the first try. It's been less than 6 hours since the installation, but so far I'm loving it. Very impressed with the locks and ISY integration. -Randy
-
This is fantastic. It's working great for me. -Randy
-
I'd be curious to know what time your admin console shows for your current Sunrise and Sunset (look at the top of the window). You don't live near the North Pole, do you? -Randy
-
Speaking of 2016 technology, looks like LG is prepping an Echo-like audio player and smarthome hub that "serves as a gateway to smart sensors and connected appliances": http://www.engadget.com/2015/12/30/ces-lg-smartthinq-hub/
-
Try this: From the admin console's Configuration->Networking->Network Resource tab, select Import and load one of the ZIP files.
