@Scott-Basgaard Well at the time I'm pretty sure you could download what was called the "pybytes" firmware and modify it accordingly (with the patch above). But this particular problem was sorted out in a later version of the built-in pybytes library, at least for me.
FWIW, back then you had to set the dns server with socket.dnsserver() before you did from network import LTE.
Hi,
You can either send it as a string ('4045620583'), or use a float to represent the value. Sending it as a string will still make it a number in Pybytes.
Gijs
Hi,
You can set the router to loraserver.pycom.io with the ports you mention. The gateway ID can be generated similar to the TTN connection!
Best,
Gijs
The NO CARRIER error is related to the Modem not being connected to a network, hence the No carrier. Also, it seems your IP address is not correct as "10.164.0.93.255.255.255.255", I believe it should be "10.164.0.93"
@furkan Why would you expect to have the same IP? And what do you need the IP for, anyway? You are most probably behind a large CGNAT with a public IP, shared with tons of other devices, different from the IP you would get here.
If you want an identifier of the device, you should look into getting one of its MAC addresses, not an IP address.
@robert-hh Probably so but for my use I am currently quite ok with my homebrew and Pycoms firmware update tool, but when i level-up I will have a look at your suggestions. Thanks for support!
We are looking into the solving issue! This should not happen of course, thanks for reporting it! Were you able, in the meantime, to get access?
Best,
Gijs
@AlganEren Micropython on ESP32 uses single precision float with a 24 bit mantissa. That means, that it has only about 7 significant digits resolution. Besides other problems of representing a decimal fraction by a binary number that means, that the numbers you presented in you example cannot be represented by the internal number format. If you need more precision, you have to build an image using double precision floats. AFAIK, @rcoliste has pre-built such packages. see https://forum.pycom.io/topic/6234/pycom-firmwares-with-single-double-precision-and-ulab-module?_=1598594340450
Hi,
Sorry for the confusion, you are indeed correct it updates to Pybytes rc11 (not exactly sure why though). It means you should have the Pymesh functionality on the device. Which example code are you then refering to? For me, this works fine:
import time
if pybytes is not None:
if pybytes.__pymesh and pybytes.__pymesh.__pymesh:
pymesh = pybytes.__pymesh.__pymesh
while True:
pkt = "Hello, from " + str(pymesh.mac())
pybytes.send_signal(1, pkt)
time.sleep(20)
From this page: https://docs.pycom.io/pybytes/pymeshintegration/example/
Did you manage to get anything with this command? im using NBIOT and getting :
'\r\n+SQNINS: 0,4,7,,,,,,,,\r\n+SQNINS: 0,13,7,,,,,,,,\r\n\r\nOK\r\n'
which is quite empty....
Hey @ahmadelmasri ,
shame on me - I've simply overseen to enable the IoT core. Sorry bothering you guys with this simple questions. Thanks for your help, Manuel
Ok my assumption is, that the cloud integration is only usable for the signals, because it is mentioned, that it is used 'to persist data for more than 4 months'.
However I had success with following this tutorial:
https://cloud.google.com/community/tutorials/sigfox-gw
with two tweaks:
I needed to comment out line #210 of the sigfox-api.py (in the github repo provided by the tutorial) # send_duplicate=d['sendDuplicate'],
and I needed to adjust one of the message bodies inside sigfox-api-callbacks.json in line #39: "bodyTemplate": "{\r\n\"device\" : \"{device}\",\r\n\"time\" : \"{time}\",\r\n\"temp\" : \"{temp}\",\r\n\"batt\" : \"{batt}\",\r\n\"seqNumber\" : \"{seqNumber}\",\r\n\"lat\" : \"{lat}\",\r\n\"lng\" : \"{lng}\"}"
with that I was able to see my message with gcloud pubsub subscriptions pull sigfox-data-sub --limit 100 --auto-ack
nice.
Hope that helps anyone who stumbles upon the same errors.
