Troubleshooting

Great work @rjad, thanks for reporting back.

It works perfectly now! Thanks Daniele

Thank you for everyone's replies!

@tbowmo You mentioned the version number. I have somehow managed to get a very old IDE. Can't remember where I installed it from, but that seems to be the source of evil. Thank you all again! [image: 1553429030354-7545d537-e6c8-47c0-97bb-f2f72964d25b-image.png]

Thank you @mfalkvidd! I have been busy and had many issues to figure out for myself, but I still can't understand how binding with openHAB works. How does the information from nRF24 get to openHAB? I have MySensors Binding add-on installed in openHAB. I would be very grateful if someone could help with this last step. After this my first little sensor will be ready to go live.

@electrik I already dit set it at 0,5 so it is changing 1 degree. I now have made it even 0.05 so i can change it by 0,1 degree. Thanks for all the help!

I did manage to get this to work this morning. As I mentioned, I have a Freaduino Leonardo clone. This has a selector switch for 3.3v and 5v IO. I decided to go back and try with it at 3.3v and not use logic converters. It also has a ICSP breakout for SPI/IIC. I re-wired this thing many times, but was only able to get it to work when I wired it directly to the ICSP breakout and used the VCC/ground on the ICSP breakout as well. I tried the 3.3v on from one of the other pins on the board and 3.3v from a breadboarded power supply. Maybe it's something more simple that I just don't understand or missed, but it doesn't make sense to me. I made sure the 3.3v was there with each wiring change. I did however set the following: // RFM69 SPI chip select pin #define MY_RFM69_CS_PIN 6 // Define this to override the default RFM69 IRQ pin assignment #define MY_RFM69_IRQ_PIN 2 // RFM69 IRQ number #define MY_RFM69_IRQ_NUM 1 And the log shows: 565 GWT:TIN:IP=192.168.0.75 1565 MCO:BGN:STP 1566 MCO:BGN:INIT OK,TSP=1 1566 TSM:READY:NWD REQ 1566 RFM69:SWR:SEND,TO=255,SEQ=0,RETRY=0 1568 RFM69:CSMA:RSSI=-97 3569 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: I know @Carywin mentioned extending the ICSP connector through the shield and used that. Maybe that's why it worked for him.

By creating the file org.eclipse.smarthome.mqttbroker.cfg in the service folder (/usr/local/etc/openhab2/services in my case, chown to openhab), with the contents name=mosquitto host=192.168.1.69 secure=false port=1883 username= password= retain=true I was able to just create the MySensors MQTT gateway (using paperui) and it stayed online (no mqtt broker defined, but its addon is installed). I had the impressions that with the latest versions it should be possible to do everything in the PaperUI, and that the broker would use the mqtt2 addon (but in paper ui, service, config, mqtt tab, mqtt system broker connection, manage->plus button -> expert mode, I get to see the contents of the cfg file above) But unfortunately, it seems that the discovery services enters a endless loop (maybe I need to update my arduinos sketch to the latest mysensors code?) and I don't get any auto discovered things. If I trigger a new discovery it will stop the previous one and start again. Finally, I was able to manually create a thing, and link items on it. Eventually my battery level and humidity were displayed in the paper ui control page (after some weird delay, not updating once it shows in the log. the temperature didn't show up though). Not sure if my understanding is off (or paperui is limited in this sense) but in the "thing" creation page I only get to specify one child id. Then my multi sensors/value nodes would need to be define in multiple things? As I can't properly define channels for each child id, and I'm not sure what var1-5 are all about. I'll try defining things/channels/items directly in files in the following days, because so far I couldn't enjoy most of the benefits of this new version (auto discovery, logical grouping of physical device in "things", questionable "do-it-all in paper ui"), and I'm almost considering using mqtt1 binding in the new install :(

Oh shhhhoot. So by switching from 328p8m to nanoatmega328p in order to fix some issues, I actually made it worse, because the latter sets F_CPU to 16000000L. What an unbelievable oversight on my part. That explains why I had to monitor the serial output at 1/16th of the baud rate. Overwriting the frequency in the config file with board_build.f_cpu = 8000000L did the trick. No need to adjust the SPI bus speed anymore. Baud rate set to 57600, monitoring at 7200 (1/8th, CKDIV8 enabled). All good! Thanks for pointing that out, @tekka! I feel embarrassed, that I didn't notice that myself. Small update -- after some more testing, setting board_build.f_cpu = 1000000L and #define MY_BAUD_RATE 9600 seems to be even better with CKDIV8 enabled. 1ms is actually 1ms and communication between nodes is way more responsive. Powering the sensor node on, initializing, finding parent, presentation, etc,.. is now done withing 6 seconds instead of roughly 30 seconds.

Cool, thanks for your help!

@flyingdomotic certainly. But I do not have time for MySensors development at the moment, only support. But pull requests are always welcome!

@tmandel @rejoe2 Thank you for your effort with patching the FHEM module. You're wellcome! Wrt your patch: To get that into the mysensors repo, you'll have to use the (very painfull, but due to copyright reasons necessary) regular github mechanisms to get registered as kind of mysensors developer. Then you can send it as a pull request against the MySensors repo. As you use a new flag (?), you'll have to add some short decription wrt that also. I'm not very familiar with all these processes, but in case you need help wrt that you may also contact me via FHEM forum for assistance. Btw: Good job!:clap: :clap: :clap:

@mfalkvidd Deleting that folder(and reinstalling everything once again) helped. After succesfull upload i've looked at serial monitor(without connecting nrf), and there was few messages. Next i've connected radio, and it stopped working. Problem was capacitor on radio. Without capacitor everything is working ok. Thank you again.

@flyingdomotic I agree that references to relevant part of the datasheet for each delay would be good. Now they are just magic numbers. Without such references, understanding, reviewing, extending and maintaining the code is extremely hard. For [solved], edit your first post and change the headline (you might need to scroll up to see the headline if you are on mobile)

@rjgmba Home Assistant should connect to the mosquitto broker

@zachflem using the nrf without cap often (almost always) leads to failed transmission, but it should not affect initialization of the radio.

I need too