I recently bought an AWS IoT Button generation 2, and I'm trying to set it up.
I followed the steps in this tutorial: http://docs.aws.amazon.com/iot/latest/developerguide/iot-gs.html
I can connect to the wifi network generated by the button. I went to the .../index.html, attached my certs, etc.
Everything seemed fine, until I tried to use the button. When using the desktop-based instructions, I went to the MQTT Client and subscribed to it, but saw nothing when I clicked the button. When I tried to use the iOS app setup, I set the button action to send me a text message. I never got the text message. In both cases, the below occurred:
When I click the button, it blinks white for about a minute, then 3 short red blinks (meaning there was an error connecting to the wireless network).
I've tried these steps in my secure home network as well as the open network at my local library. Same results.
I've also tried starting over, repeating all steps from the tutorial and creating new certificates, etc. Same results.
Seems I'm not the only one having this problem.
Any help is much appreciated.
My button is now connected, although I have no idea why it wasn't working. I just followed the exact same steps I had been following on the same wifi network and everything, and all of a sudden it connected. Still looking for insight if anyone has some!
Related
I have set up a pixel streaming in UE5 in AWS(Amazon Web Services) it works perfectly on my laptop, mobile and my colleagues system (same WiFi).
When I send that public IP4 link to my client in another city it just appears blank, after clicking the triangle (play button) in Pixel Streaming.
Edit 1: when I change the location(IP) using VPN, it also not working on my laptop too.
EDIT 2:
I'm using UE5 pixelStreaming, It works on many devices/locations, but it didn't work on some locations. I contacted AWS the checked different locations and its working on their side.
surprisingly i didn't do anything it worked on all devices in all locations the next day.
On the next day this problem arise again it didn't work in my client's whole office.
after a few hours, it started to work on some of my client devices(mobile /web browser).
I checked the remote desktop I find out that webRTC data is not coming there.
Why WebRTC data not coming in some of the devices?
I think it might be because you didn't allow access from other networks on AWS, so it only allows those on your network to see it. While not this exact issue, something similar happened to me before.
Im trying to connect to my Amazon Workspace using the Workspace client on Ubuntu. I keep getting this. I can connect no problem from my windows machine at work, but keep getting Display Error at home on my linux machine. .
I had same trouble but solved the problem. Please try following process.
Uninstalled AWS.
Re-start PC and installed AWS again.
Wait for couple of hours. while you waiting, try to keep pushing Refresh button or re-start AWS again and again untill the windows shows log in screen.Because it may take some time to clear old registration information and refresh it in the host side according my IT dept says.
Anyway, I've sent the log files to the AWS help desk and are waiting for their reply.
good luck!
Here we can not assume that it is not working because of so and so reasons, instead we should exactly get to know the root cause for this error. So in order to get the RCA, check the log files present in this directory:
C:\Users\yourname\AppData\Local\Amazon Web Services\Amazon WorkSpaces\logs
So, for me, it was showing the AWS URL access was forbidden.
I have been looking for a way to send commands to my google home by pressing a button connected to an ESP8266. What I am trying to do is have my Google home turn off / on my Smart lights by pressing a button rather than saying the command.
I have some generic Wi-Fi controlled smart lights that are connected to my Google Home and I control them with the basic on/off commands (turn them on I say "OK Google, turn on my lights." and for off "OK Google, turn off my lights."). I would like to be able to press a physical button and have the ESP8266 push the command to my Google Home and have it execute it. Essentially a light switch that uses code to toggle the lights on and off rather than cutting the power, or go into an app, or say a verbal command.
I would prefer it not to use IFTTT but if that is necessary I will oblige to doing so. I have seen countless people send commands TO an ESP8266 FROM a google home, but I have never seen it accomplish way around besides 1 GitHub post showing that you can send voice commands using his Library called Google Home Notifier. While this does work for having my Google say something I don't know how (if even possible) to use it to have Google receive and execute a command.
As I stated earlier I don't know if this is even possible. I believe there is some way to do this I just don't know-how. I would really appreciate any help that can be given or a point in the right direction on how to accomplish this.
Why do you even want to use your Google Home ?
What if you connect your ESP8266 to home-assistant, and trigger an automation when the button is pressed ? This automation could turn off the lights, or call a Google API if that's what you want
N.B: I guessed you have a home assistant setup because of the tags in your question. If that's not the case, please edit
I am doing automated tests [Android / Appium Java JUnit] with the AWS Device Farm service, but they are interrupted by the use tutorials that appear on the devices, for example, the tutorial of how to use the camera. I want to know if there is a way to disable the tutorials of the use of the device. Thanks.
I work for the AWS Device Farm team.
We detected and root caused this issue where a one-time tutorial popup appears on some phone's camera apps. We've corrected it, so feel free to try again and let us know if this problem is still affecting you.
Looks like there is also a script you can run from this AWS forum post
https://forums.aws.amazon.com/thread.jspa?threadID=294719
Hi,
I'm so sorry this keeps happening to you. We do currently only have the dismissal running on some devices like the Samsung S9, and are going to be enabling it for other devices soon, in the coming weeks. What I can do now is provide you a script to verify that theyre dismissed yourself at the beginning of your test. If you're using "custom environment mode", add the following 2 lines to the pre-test section of your test spec file:
curl https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/chrome_initialization_and_popup_detection.py -o chrome_initialization_and_popup_detection.py
- python chrome_initialization_and_popup_detection.py -v --retries 2 --output-dir $DEVICEFARM_TEST_PACKAGE_PATH/popup_dismissal
This will run our popup dismissal script in your own code to verify that any device you run on gets all popups dismissed. It shouldn't be necessary for some devices like the S9, but just in case any do happen to creep up, this will dismiss them for you. I'll also double-check on our end why some popups like the S9 popup aren't getting dismissed properly.
I am setting up my AWS DeepLens and all the steps have been successful until I try to connect to my home WiFi. How do I fix this issue?
I created a hotspot on my phone to test against a different network and this connection was successful. Then, I switched back to my home WiFi and it connected successfully.
This section of the troubleshooting guide will also fix the problem.
We found that the AWS DeepLens only has one network adapter which it uses both for its own hotspot and connecting to the network. If you are connected to it via any other means (e.g. via a phone) it will throw a hissy and start dropping the connection, repeatedly and seemingly randomly.
When we connected a monitor directly we then found it was stuck on a viewable password prompt, hence why it was not connecting to our network.
Best method by far (and from our experience, only usable option) is to connect directly to the device so you can see what it is doing. To do this you need USB keyboard and mouse, and a mini-HDMI to HDMI cable to hook up a monitor. This will free up the network card to do only one thing.
When connecting please note that the default admin password on ours was "aws_cam". This does not seem to be noted anywhere in the documentation. This will change when you go through the setup process and sync it with your AWS account.
Repeat the process by inserting a pin in the hole at the back of DeepLens. Wait for a few seconds, the wifi indicator (the middle light) would blink and then you can connect with Deeplens wireless network. Then you can open http://deeplens.config where you can configure your home wifi and complete the setup.