Hi, thanks for this !
You specify this is for macOs users, do we really need macOS to do that or windows 10 will do ?
Thanks !

Sorry, in my previous comment I didn't write my email. Here it is ! Thanks again, Albion

Thank you for this great tutorial! Please continue to make such good videos. I would love to see how value transactions via Raspberry Pie3 are working. So that I am able to assign a senders address to a username for example(as I understood you right, the sending adress is changing every time). Normaly I use Arduino but there is no complete library out at the moment, so without this tutorial I would be stuck.

Small note: the address of the node in the program code was offline or outdated and had to be exchanged

Keep it up, greetings from Germany

@Albion: Yes ist works the same, but you have to use the windows remote desktop.

Thank you! This tutorial is great. Just tryed it and it worked really good. At the start i've got some problems with the testnets. -> a few of them didnt work. As I replaced the original one mentioned in the code it worked fine.

Very nice tutorial. So far everything runs very well.
I've got a question: Why are there several root addresses when I start the file: mam_sensor.js? Aren't all temperature/humidity information stored under one root?
Greetings from Germany

Hi Robert, thanks for the tutorial, excelent work. I have 2 questions.

1. I want to replicate this system but instead of using a sensor, I want to send the data directly from my PC, just random data numbers simulating the sensor through an Ethernet connection. Can you put me in the right direction?

2. The data is directly published from the PI? Or the Pi sends the data to an IOTA node and from there uploaded to the Tangle?

Hi Robert,

your code uses an external IRI (https://nodes.testnet.iota.org:443). Is it on the Mainnet, Devnet or Spamnet?

Can it be possible to Attach MAM messages to the Mainnet?

Thanks for your work.

Hi Roberto, me again,

You do not directly state that we have to download the iota.js library. Why is that?

To my understanding, the mam.client.js Library needs the iota.js library. I checked in the lib/ repository of the mam.client.js library and it comes with an iota.js document, I opened and is not the complete library its just a 16 line document

Thanks for your work.

I got Error while running mam_publish.js and mam_sensor.js

failed to attach message:
Error: Invalid Response: Error: getaddrinfo ENOTFOUND nodes.testnet.iota.org nodes.testnet.iota.org:443

Solution Please.

at step 13 it says:
failed to attach message:
Error: Invalid Response: Error: getaddrinfo ENOTFOUND nodes.testnet.iota.org nodes.testnet.iota.org:443


how i can fix this?

I got the same error:
Error: Invalid Response: Error: getaddrinfo ENOTFOUND nodes.testnet.iota.org nodes.testnet.iota.org:443

How can we fix it?

Thank you very much Robert for this wonderful in-depth tutorial on IOTA.
Tried the above step and it worked fine.
Just had minor issues like:-

failed to attach message:
Error: Invalid Response: Error: getaddrinfo ENOTFOUND nodes.testnet.iota.org nodes.testnet.iota.org:443

{@Raj Pandey, @Michael, @Oscar Lg}
But this got fixed when i replaced the test node address with anyone of the one which are available on your MAM demo page(https://www.mobilefish.com/services/cryptocurrency/mam.html).
Replace the test nodes in all files namely:- mam_publish.js, mam_receive.js, sensor.js, mam_sensor.js.

Devnet requires mwm to be 9 in mam.client.js

Does it still work exactly like that in the Chrysalis Network?