I attached my Amazon Echo Dot device into Alexa for Business.
Initially, status was "Synced". But, when I added this device into given room, it entered into state "Sync in progress", and stuck in that state only.
Required information-
Device software version - 597464620
Address in Room profile - Mexico City/New York (Tried with Area)
Alexa for Business Region - us-east-1 (N. Verginia)
My location - Bengalore, India
Device Name - Amazon Echo Dot.
Found one forum discussion over this, but didn't get much help - https://forums.aws.amazon.com/thread.jspa?messageID=824543&tstart=0
Please help me out here.
Related
I found this quickstart guide on how to do it locally. But there is no information about on how I can deploy my smartcontract to devnet or mainnet.
So I changed endpoint:
const client = new TonClient({
network: {
endpoints: ["https://net.ton.dev"]
}
})
According to comment, I removed useGiver:
// Request contract deployment funds form a local TON OS SE giver
// not suitable for other networks.
// Deploy `hello` contract.
await helloAcc.deploy(/*{ useGiver: true }*/);
And got this this error message:
Account does not exist. You need to transfer funds to this account first to have a positive balance and then deploy its code
How do I fund my account, is there any automatic method like airdrop?
We added a couple of guides about how to deploy and configure your own giver in developer network. Please, check them out:
Work with devnet with everdev tool - https://github.com/tonlabs/everdev/blob/main/docs/work_with_devnet.md
Configure giver in AppKit - https://tonlabs.gitbook.io/appkit-js/guides/custom_giver
You need to first calculate the contract address in the target chain and then tip it up to 1 EVER for deployment to succeed.
The amount of gas needed depends on the code of the contract, but cannot exceed 1 EVER.
There are no automatic givers in net.ton.dev now. But you can get rubins from here: faucet.extraton.io Also you can create automatic giver in this test network by yourself.
I´m trying to deploy a AWS EC2 Mac instance.
During the process of setting the instance up, I get asked to allocate a dedicated host for it.
When I try to do it, I keep getting the following message:
Your request for accessing resources in this region is being validated, and you will not be able to launch additional resources in this region until the validation is complete. We will notify you by email once your request has been validated. While normally resolved within minutes, please allow up to 4 hours for this process to complete. If the issue still persists, please let us know by writing to aws-verification#amazon.com for further assistance.
It´s been more than a day since I started trying, so the problem isn´t the 4 hours mentioned in the message.
Anyone has any ideas how to solve this?
Thank you!
Is the AWS account in which you are trying to provision those resources brand new?
Messages like the one you are seeing are usually seen in case the account in question hasn't been fully activated or lacks billing information.
If my assumption is correct check the root account email inbox for confirmation/verification email requests from AWS. And make sure that your credit card information is up to date.
I have been doing a bit of experimentation with Amazon Lex but I can't get voice to work in the console at all.
I'm using the Flower bot demo with the associated Python Lambda function connected and working with text on Chrome browser running on a Mac (10.13.1).
I am able to log any text entered into the test bot on the console from the Lambda function along with the rest of the event.
By going to the monitoring tab of the bot in the console I can see utterances from previous days (seems to be a one day delay on utterances appearing wether missed or detected, no idea why…).
I made a bunch of attempts to use voice yesterday that appear in the utterance table as a single blank entry with a count of 13 now that it is the next day. I'm not sure if this means that audio isn't getting to Lex or if Lex can't understand me.
I'm a native English speaker with a generic American accent (very few people can identify where I'm from more specifically than the U.S.) and Siri has no trouble understanding me.
My suspicion is that something is either blocking or garbling the audio before it gets to Lex but I don't know how to find what Lex is hearing to check that.
Are there troubleshooting tools I haven't found yet? Is there a way to get a live feed of what is being fed to a bot under test? (All I see for the test bot is the inspect response section, nothing for inspecting the request.)
Regarding the one day delay in appearance of utterances, according to AWS documentation:
Utterance statistics are generated once a day, generally in the
evening. You can see the utterance that was not recognized, how many
times it was heard, and the last date and time that the utterance was
heard. It can take up to 24 hours for missed utterances to appear in
the console.
In addition to #sid8491's answer, you can get the message that Lex parsed from your speech in the response it returns. This is in the field data.inputTranscript when using the Node SDK.
CoffeeScript example:
AWS = require 'aws-sdk'
lexruntime = new AWS.LexRuntime
accessKeyId: awsLexAccessKey
secretAccessKey: awsLexSecretAccessKey
region: awsLexRegion
endpoint: "https://runtime.lex.us-east-1.amazonaws.com"
params =
botAlias: awsLexAlias
botName: awsLexBot
contentType: 'audio/x-l16; sample-rate=16000; channels=1'
inputStream: speechData
accept: 'audio/mpeg'
lexruntime.postContent params, (err, data) ->
if err?
log.error err
else
log.debug "Lex heard: #{data.inputTranscript}"
Go to Monitoring tab of your Bot in Amazon Lex console, click "Utterances", there you can find a list of "Missed" and "Detected" utterance. From the missed utterances table, you can add them to any intent.
All,
I am using Ubuntu OS in my AWS EC2 instance. My previous developer has created some custom messages once we SSHed into the Instance (Attached). But I would like to change it. Googled extensively, but no luck. Can someone help?Text I want to change is "Live 1A"
Edit the file /etc/motd
motd stands for Message Of The Day
MOTD(5) - Linux Programmer's Manual
NAME
motd - message of the day
DESCRIPTION
The contents of /etc/motd are displayed by login(1) after a successful login but just before it executes the login shell.
The abbreviation "motd" stands for "message of the day", and this file has been traditionally used for exactly that (it requires
much less disk space than mail to all users).
I have an application that creates a report and emails it to a recipient name typed in by the user. On top of this we have built an automation layer so the report can be scheduled to run a specific times and email the same recipient each time. This is achieved by recording the windows messages received in a file and using PostMessage to play them back later. This works without a problem when run by the logged in user but fails when started from a service that is logged on with the same user account. The re-play of the recipient email address changes from recipient_nam#domain.com to recipient_name~domain.com
The '#' symbol in the email address is being replaced with a '~' which I believe is due to the keyboard layout in use when started from a service. The # symbol has a virtual key code of VK_OEM_3 on an English UK keyboard but on an English US keyboard that corresponds to the key under the 'Esc' key and that, combined with shift, gives the '~' character. This is also backed up by calls to GetKeyboardLayout() which yield 0x0809 (United Kingdom (GB)) when launched by the user and 0x0409 (United States (US)) when launched by the service logged on as the same user account.
All of the language and regional settings I can find are showing as English UK. Where could the English US keyboard layout be picked up from? Can I force the layout to English UK?
A Microsoft customer services representative played around with the region/keyboard settings on the server in question and managed to get them reset so the service account used an English UK keyboard.