Troubleshooting

mmh, but as I mentioned in my first post the node (and all my other notes) reported their status instantly when I restarted my gateway, so I guess it´s a gateway problem.

@tbowmo I will be the first in line to get the GW. I found and old discussion about this same issue here Witch lead me to this GitHub Library But I was unable to get it to work using this also (I just don't know what I'm doing poking around inside Libraries changing files).

This is an issue with the HW SPI port in the atmega328. If configured as an input, the master spi port will turn into a slave, if SS pin is low. Atmega328p datasheet, section 19.3.2: When the SPI is configured as a Master (MSTR in SPCR is set), the user can determine the direction of the SS pin. If SS is configured as an output, the pin is a general output pin which does not affect the SPI system. Typically, the pin will be driving the SS pin of the SPI Slave. If SS is configured as an input, it must be held high to ensure Master SPI operation. If the SS pin is driven low by peripheral circuitry when the SPI is configured as a Master with the SS pin defined as an input, the SPI system interprets this as another master selecting the SPI as a slave and starting to send data to it. To avoid bus contention, the SPI system takes the following actions: The MSTR bit in SPCR is cleared and the SPI system becomes a Slave. As a result of the SPI becoming a Slave, the MOSI and SCK pins become inputs. The SPIF Flag in SPSR is set, and if the SPI interrupt is enabled, and the I-bit in SREG is set, the interrupt routine will be executed. Thus, when interrupt-driven SPI transmission is used in Master mode, and there exists a possibility that SS is driven low, the interrupt should always check that the MSTR bit is still set. If the MSTR bit has been cleared by a slave select, it must be set by the user to re-enable SPI Master mode.

@korttoma Success! Got this ethernet gateway up and running! Thank you very much.

Thank you so much for your elaborate explanations ! It really cleared up some questions I had in mind, especially about the Arduino versions ! Also, I did not know that "Mysensors" is run entirely by volunteers! I will try to become one of those useful volunteers that helps others (like you :) ) rather than coming up with questions all the time ;) :)

Ok, now we're cooking! @tekka, thanks for explaining some of the details that I was missing. I'm sure I read that before, but I guess I swapped "gateway" with "controller" in my head, assuming that the sensor node would be assigned an id by the gateway. I placed the following in my sensor node's sketch: #define MY_NODE_ID 2 This avoided any errors, but I still wasn't seeing the correct message come through MQTT. Not sure if it was required, but I ended up having to add #define MY_PARENT_NODE_ID 1 to the sensor node's sketch, and #define MY_NODE_ID 1 to the gateway node's sketch. Once I did that, the temperature readings started showing up in MQTT! Thanks for the help everybody. I still have quite a bit to learn, but getting a working sensor sending data all the way through the gateway to MQTT was the biggest hurdle to really making progress on implementing these. THANK YOU!

@Yveaux I am so terribly embarrassed! In order to rule out something wrong with the WS5100 I rebuilt the GW using an old Arduino UNO with an Ethernet shield. Still same problem. Then to really make sure I pasted/copied username and password from the cloudmqtt into the sketch. Immediate success! It turned out that I had misread an uppercase I (indigo) for a lower case l (lima). Still the suggestions from the community were good since I could iron out one possible cause after another. Thanks for the support!

@tlpeter Took me a while to find a circuit for the LE33. I use a 0.1 uf keramic capacitor between VIN and GND and a 2.2uf elco between gnd and VOUT. That does the job for me in terms of keeping a stable circuit.

I maybe found the solution. Download the version you had from here https://github.com/mysensors/MySensors/releases then copy Library folder from file to your Arduino installation. I should be great if you can add a text on the page https://www.mysensors.org/about/arduino#installing-the-sensor-libraries that the user is recommended to make a copy before you updating library

@Matt Not sure if you do this. But in my experience, you need to add small delays (wait(15)) in your sketch after communication. Especially when creating large multi sensor nodes. The radio isn't always fast enough to digest all of the communication. Not sure if this is your problem, but it solved my problems.

Ok guys, thanks for your quick replies and please excuse my late reply...

@mfalkvidd Node id's work now. Thank you everyone for your help. Mike

@Tore-André-Rosander you could do a tail on your gateways serial device. Currently @work so I can't look it up for you. But that should show the serial communication between the gateway and domoticz. Also you can check the log of Domoticz in the log console of Domoticz

Beer from you.

Hi there, I had a similar problem gw and sensor saw each other but the sensor did not get an id. Later I found that the controller hands out the id's, not the gateway. So when I connected the controller to the gw and configured it to use the gw arduino it worked. Not sure if this is your problem also but just in case :) Greets, Mark

Thanks for your help, it works !! In addition i have download all examples and libraries from github (one of them missing and i have some errors) link : https://github.com/mysensors/MySensorsArduinoExamples. And thanks again for the works of the community on MySensors . It's a beautiful project.

@chatainsim I couldn't see strange things in your sketch. What I always do when I build a multi sensor node is put a small wait after each message I send to the gateway. I've noticed that the radio cannot always keep up with the speed of the Arduino. So something like gw.wait(15); after each gw.send does the trick for me. These are the though ones to pin point. Because it's 80% for sure a power related issue. If you happen to have a buck converter, you could try to set that to 3.3V. Power it from an adapter and feed the Gateway antenna from the buck converter. Don't forget to connect the grounds of the radio and the Arduino. But it's really hard to help you from a distance. Maybe someone else has some ideas.

I agree with you, if you use have a radio in your system is because you want to control it remotely. But I think that there is more reason: Mysensor could be an additional function on my system, not the only one. So the others system will not work. Safety requirement, the system shall run free without knowledged locks. If the GW go down for any reason, maybe beacause is broken, your system could be no work. Is not a common case, but it's a real case. In my case, my node have a digital input (switch on the wall) and a digital output, the digital output (relay) is manage from the Mysensor node and from the digital input. If the GW is broken, the digital output will not work till I fix or change the GW. It can pass one day or one week it depend of the job. My wife will be very hungry if she can not manage the house manually with the tradional swithes on the wall. Any way, it's a feature that I think that could be take into account for next release. Is not very important because is not usual has not GW in the network, but I think that is a safety requirement to add in next deliveries. Thank a lot for your support. It's a nice forum