@brady-aiello You have to change it on the xxPy device. I usuall switch to station mode in my boot.py script and connect the xxPy device to my home AP.

@bnjroos Yes, the RX1 and RX2 delay are specified in the LORaWAN regional settings. I did not look that up for every region, but the ones I recall use 5 and 6 seconds for OTAA join, and 1 and 2 seconds for other downlink messages as default.

@manuelc1318 as I wrote, you can transmit data in both directions: write to a characteristic to send data from client to server, and either read from a characteristic or use notifications for data from server to client.

@jcaron oh thank you. I will do that. And I need a small help from you. In this code, I am trying to start my downlink once in a day. So I am using this code. import time a = time.localtime() hour = a.tm_hour minutes = a.tm_min if hour == 10 and minutes == 40: print('{0}:{1}'.format(hour, minutes)) But it's not working properly. Do I have to change some conditions ?

Hi @stefan85e, You can find our example project for the Pysense on GitHub here. It has the main.py with the code and the libraries.

@humhrey Starting from the top Pycom-sigfox directory: .../esp32/mods/modlora.c as entry point for the python API Supporting code: .../lib/lora/.... .../drivers/sx27x/... .../esp32/lora/....

Sorry to grave dig, but had I known this earlier it would have been helpful. This post is about the Decagon 5TM, which has two protocols, SDI-12 and DDI. The DDI is typical UART at 1200 baud, which you can read from any UART reader. I've tested it with an FTDI cable and know it works with a LoPy. You do however have to power cycle the sensor to get a new reading. Note: This may not work on new Decagon 5TM sensors if you have changed the SDI-12 address to anything other than 0. Factory default is 0. If you have not used SDI-12 to communicate with the sensor then it should work as expected. We used a mosfet to turn the power on and off for the sensor, controlled by GPIO. Reading the UART within 10s of milliseconds from turning the power on will give you your readings. Its all explained in the integration guide. http://publications.metergroup.com/Integration Guides/18237 5TM Integrators Guide.pdf I know this doesn't help with SDI-12, but jubbs is using the 5TM specifically, which has this dual protocol stack. The sensor was also just powered from 5 volts (same supply source as for the LoPy), the 5TM supports 3.6V-15V, check datasheet for more information including current draw.

@robert-hh said in Lopy4 LoRa 433mhz how to: @lennyz1988 In Raw Lora mode (LoRa.LORA), you can use region EU868 and set the frequency to 433MHz. For Lora WAN, I have adapted the repository to include region EU433. This is the link to the Pull Request: https://github.com/robert-hh/pycom-micropython-sigfox/tree/development Until that is eventually included in the standard images, you have to make you own build to include that. P.S.: You may also use that branch https://github.com/robert-hh/pycom-micropython-sigfox/commits/ctrlf-fix, which in addition includes code allowing to disable reboot on Ctrl-F Thank you for the reply. I am going to test the links you posted! :)

@jcaron My diagram is incorrect sorry, however I tried a new max3232 today and managed to get it to work. Thanks

@robert-hh Thank you so much ! I got the output.

@robert-hh Sorry for the late and Thanks for your reply. I have tried with simple change like adding if statement with particular device address but it's not working. Is there any other possible way ?

Hello, I'm having a similar problem when trying to connect using EAP-PEAP. Has anyone gotten any results? Thank you.

@harish-kumar Well, you're not sleeping, so you shouldn't need to nvram_save/restore, but you're re-creating the LoRa object (twice!) in your loop, using two different modes (raw LoRa and LoRaWAN), and re-joining each time, so no wonder your frame counters get re-initialised. I'm really not sure you can use the current LoRa stack like this to achieve what you want. I'm quite certain it would require some extensive changes to the stack, especially if you really want to maintain true LoRaWAN compatibility (i.e. including ADR, MAC commands, etc.).

hi @Harish-kumar , we released here Lora-Mesh, that I thought it will help you. Well, mesh-network over LoRa, has a specific protocol (Thread), and probably it's not implemented neither in Arduino, nor Multitech. This would work if all 3 devices would be Lopys, the last one (gateway) would be registering itself to TTN as gateway, and forwarding data from the first Lora (sensor), thru the second one (the repeater, which does this automatically, being a Mesh node - router role).

@vanclevector I do not know how you interface the diesel generator to you xxPy device. At leat the AC generated by the unit must be transformed to a clean 3.3 V square wave signal. I understood that this part is done. Do you have a schematic of the interface circuit of a oscilloscope dump of the signal the gets out of that?