Glad that you find it useful !!😄

Thanks for the comments !!

Thanks, Good question !! mqtt broker supports both raw TCP and Websocket. We are using browser as our client in this video and that's why we are using websocket for real time updates. Using raw TCP connection in mqtt is not easy in a browser 😄 hope it helps !! Keep supporting !!👍

@@techbeast-org thanks for the clarification. I was more curious to understand as to whether or not is a constraint from aws t2.micro that MQTT is not allowed and WebSockets was a workaround.

@@vikrantmakwana No...AWS EC2 won't restrict anything, it will allow all the protocols we define in the rule list😄

Thanks for the support !! Please do send email to hello@techbeast.org and we will notify you regarding our upcoming events in future 😀keep supporting !!

Thanks for the support !!

Yes, it works the same way if you use a nodemcu as client but you need to include the mqtt client library to pub/sub to our broker in AWS.....Share with the community if you try it out :)

You need to assign an elastic IP address for your instance to keep your IP address same after every restart, hope it helps !!

Yes, you need to run broker in your cloud. So that you can pub/sub messages from anywhere !!

you can simulate the sensor values , a simple math.random() function will be helpful for you !!

Yes, please make sure the details and credentials are correct in your mqtt client. You managed to fix the error ? :)

you need to add your password file path first in default.conf file as shown in 11:23 sec of the video, then sudo mosquitto_passwd -c /etc/mosquitto/passwd will do the rest, please restart your mosquitto service and try again :)

Make sure there is an empty file named "ssh" available in your boot image !! Hope it helps

@@techbeast-org Thank you very much! It really helped! I did everything else like the video but now everything works, from my raspberry pi terminal I can see that the sensor is publishing data to the broker but every time I refresh the index.html file it does not update the temperature value and I tried to test if it is publishing correctly by going to test section of aws and subscribing to the topic but while it says it is publishing data to the broker from the raspberry pi terminal, nothing appears in the aws testing section Could you help me with this? t Thank you!

You don't need to refresh as the browser is subscribing over websocket which is real time. 1. Please make sure the websocket is enabled in the mqtt conf file and run this code in your laptop github.com/techbeast-org/aws-mqtt-dht 2. Please check the websocket port 9001 is allowed in your security group in AWS

Hi Krishna, yes you can change the allow_anonymous to true and remove the password config in the mqtt config file. This will make your broker publicly accessible, you can change that at this step ukposts.info/have/v-deo/bJybl3ilbIh0kYU.html , hope it helps !!

resolved it now , actually the .PEM key pair file was not in the directory I was trying to run it from . but now could get through it. Thanks

@@saveplanet3977 that's cool, keep supporting us😄

hi you can add like this sudo vim /etc/mosquitto/conf.d/default.conf in above file add this line listener 8083 protocol websockets certfile /etc/letsencrypt/live/mqtt.example.com/cert.pem cafile /etc/letsencrypt/live/mqtt.example.com/chain.pem keyfile /etc/letsencrypt/live/mqtt.example.com/privkey.pem

AWS IoT have 12 month free tier when you sign up as a new customer, which you can leverage on to learn IoT upto certain limit. You can filter IoT and check here aws.amazon.com/free/