@tomstoffen I just briefly read your message. The first thing is TTN have their own fair use policy, so when sending a message every 5 seconds you will deplete your air time very soon. Depending on your payload size, you should be fine if you send a message every 15 minutes (that's what I've tested), maybe even every 5 minutes should be OK. from this page: https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html Finally, on The Things Network’s public community network, we have a Fair Access Policy that limits the uplink airtime to 30 seconds per day (24 hours) per node and the downlink messages to 10 messages per day (24 hours) per node. If you use a private network, these limits do not apply, but you still have to be compliant with the governmental and LoRaWAN limits.

@hayesey I am looking for a SIM card NB-IoT enabled in the UK. Could you let me know how you get your SIM card, or where I can find one please?

@Xykon Telia allows tcp/ip mqtt access. It was as I suspected, a DNS server issue. I solved it by modifying the pybytes source code to use Google DNS. diff --git a/lib/pybytes_connection.py b/lib/pybytes_connection.py index b7c3f49..3d16201 100644 --- a/lib/pybytes_connection.py +++ b/lib/pybytes_connection.py @@ -130,6 +130,10 @@ class PybytesConnection: print("You need a device with FiPy or GPy firmware to connect via LTE") return False try: + # use Google DNS servers + socket.dnsserver(0,'8.8.8.8') + socket.dnsserver(1,'8.8.4.4') + from network import LTE time.sleep(3) print_debug(1, 'LTE init(carrier={}, cid={})'.format(lte_cfg.get('carrier'), lte_cfg.get('cid', 1))) And also need to reset modem on boot-up, because otherwise it can hang when connecting to the MQTT server, for whatever reason (?): # boot.py -- run on boot-up from network import LTE print("Resetting modem...", end="\r") lte = LTE() lte.reset() lte.send_at_cmd('AT^RESET') print("Resetting modem... Done.") I have to disable pybytes autostart in the json file, to get this working, obviously. // Erik

@jirkakrepl today there is no data displayed the last samples are from 3 days ago. if i have a pull size of 20 it says no recent data. the best thing for me with those line graphs is to select the time scale and it plots al the data points in between.

@dnear1 We deployed the fix now

Ive pointed the correct people at this thread. one of them should be able to answer soon :)

Heya, There is currently no system in place to export data. but one should be ready soon. Paul

@weingami Hi, I deployed hotfix and tested wifi, sigfox and lora connections. I correctly received the data. We need to test more things and there are a few more bugs, that we know and we're about to fix now.

@cirobr glad that got it fixed for you. Not sure if it was a case of overload. More just having time to develop rate limiting that never existed previously.

@protean Hi, when you click on "get location button", Device scans the wifi networks around and sends the result to Pybytes. Pybytes is using Google location API to figure out and the location.

@belal-chaudhary Can you confirm is your wireless network the standard wep/wpa-2 setup or does it use fancy certificate based authentication? Nothing strange going on Re Network proxy's like Eduroam/mobile providers are likely to have?

Just got around to getting back to this issue - thanks so much Xykon, problem solved! robert-hh: I did do erase during update yep, a few times, but eventually was solved with advice from the post above :)

Hi @klaus, Currently, you can only configure one WiFi network, and save multiple in the Pybytes console.

@jirkakrepl Thanks. I had worked this out.

@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.

Hi @nicoloboatto, Indeed it is not supported currently, but it's on our list.

This is strange behavior. When I assign it a new ssid / pw, it acts as an access point, and I can directly connect to it. When I delete the device, and add it again with an ssid / pw for the local wifi, it connects to that, and subsequently connects to PyBytes.