Hi Miguel, The Spot'it service is available for all Sigfox development kits including the SiPy

giving up for now and hoping for the FiPy

@bettina I guess they fixed it without bothering to thank me ;)

Hi everyone. I want to tell you that I have already solved the problem. There is a conflict with the line in which I declare a Pin as output and the moment in which it is transmitted: Pin('P5', mode=Pin.OUT, value=1) What I did was change the pin to P13, this ended the problem and I was able to transmit without any inconvenience and see the data in the Sigfox Backend.: Pin('P13', mode=Pin.OUT, value=1) [image: 1504880079593-upload-1af3b981-1883-46c5-afa3-16dfe2bcb8ef.png]

@dommei I have always been in an area near the Sigfox network and don't know of a way to get data into the Sigfox back end any other way. If you just want to get the data for testing you can just save it to an SD card if you have the PySense or Pytrack or wifi. Or are you trying to export the data from the Sigfox back end into a database? If this is the case you are trying to get some test data into the Sigfox backend. I have no idea how to do this Sorry. https://resources.sigfox.com/document/callbacks-documentation might help?

That worked like a charm! Thanks!

@livius Hi livius, That's work!, now I need to understand how work the "format" of the "pack" function and specialy "little and big-endian. Best regards Jiemde

Hi @scg94 Sorry, I'm jumping late in this topic 1/ Did you manage to get this sorted ? 2/ If not, I assume you got this base station through a loan from Phaxsi Solutions ? Please send details to devrelations@sigfox.com so we can have a look 3/ In case you're unaware, Phaxsi is organising two developer events next week in Bogota & Medellin : makers.sigfox.com/tour

The latest firmware, 1.6.12.b1 has fixed this issue for machine.reset(). Typing CTRL-D in Pymakr still causes a crash but that is manageable by testing for machine.SOFT_RESET before attempting to set up Sigfox and if true, do a machine.reset() or machine.deepsleep(1) first.

@jcleloup Yes, correct. The SiPy is not just a modem, it's also microcontroller and many times more powerful than the Arduino

@jmarcelino There u go the WIFI Autoconnect was still on !!!!! Now it works. Thank you guys !!!!!!!

similar problem. this: sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ1) s = socket.socket(socket.AF_SIGFOX, socket.SOCK_RAW) s.setblocking(True) s.setsockopt(socket.SOL_SIGFOX, socket.SO_RX, True) s.send(bytes([0x00, scale(lux.light()[0]), 3, 4, 5, 6, 7, 8, 9, 10, 0xAA, 0xFF])) retval = s.recv(32) print ("received " + retval) gives me: Traceback (most recent call last): File "<stdin>", line 164, in <module> OSError: [Errno 100] ENETDOWN whilst the backend shows me: Status : [ACKED] Data (Hexa) : cafecafecafecafe any idea what i'm missing here? It's definitively not the link - sender and receiver have free LOS. avgSnr=20.74 rssi=-52.00 Used HW: FiPy on '1.17.5.b6'

@jmarcelino Certification is an interesting point. First of all it is available only for 868MHz end devices, but nor for gateways, network servers, etc. Also even if you have a certified product you can reconfigure without hacking to be out of compliance. In the Microchip stack you can do nearly the same config changes as in RN2483 but you can not fully blow it up.

@bucknall For SIgfox backend registration I beleive I need to put the ID and and PAC out put from with hexlifiy print("ID ", ubinascii.hexlify(sigfox.id())) print("PAC ", ubinascii.hexlify(sigfox.pac())) in my case is: ID b'004e3d90' PAC b'c957cd18b7848c0' so ID that I typed is '004e3d90' and PAC 'c957cd18b7848c0' The device seems to be registered but on backend device webpage I can not see it online at all. How I do I know when is connected to the (Luxembourg) Sigfox network and will get online? It is done immediately or shall I wait?

@yunushkin88 You can expect 8 to 10 Km max with line of sight between two SiPy devices. You will expect to see increased range between a SiPy and the Sigfox network as the modulation protocol is different (BPSK). Hope this helps!

@Paolo-Prado Sorry - you're right the downlink is confusingly called "BIDIR" - Have a look at this link for an example of how to get a payload from a server using the downlink https://github.com/nicolsc/sigfox-downlink