Figured this out. When connected, I can query all characteristics and create references to them - easy.

Hello @Carl-Folkesson, On the latest Pybytes firmware we have implemented the downlink feature over MQTT. Steps: Once the device is activated pybytes.set_config('pybytes_autostart', False) in your main.py you have to initialize pybytes To send a JSON string via MQTT to the device, you need to use topic d+<device_id> The message should start with 0x08h + MESSAGE example: To send {"test":"value"} the hex code is: 087b2274657374223a2276616c7565227d main.py Test Code: def callback_function(message): print(message) if (len(pybytes_config['username']) > 4 and len(pybytes_config['device_id']) >= 36 and len(pybytes_config['server']) > 4): from _pybytes import Pybytes pybytes = Pybytes(pybytes_config, user_callback=callback_function) if pybytes.connect_wifi(): # SEND PING pybytes.send_ping_message() # SEND DEVICE'S INFORMATION # The INFO message should always be sent, otherwise, Pybytes could not be aware # of some important information regarding this device, like its firmware version. pybytes.send_info_message() # ENABLE TERMINAL # This should always be enabled if you're using firmware that is compatible with the pybytes terminal. # The terminal messages will use the virtual pin (or signal) 255. pybytes.enable_terminal() else: print("Failed to connect to Pybytes! Invalid credentials or network issues?") else: print("Could not load Pybytes configuration!") NB: Kindly note that this is still experimental. Let me know if you face any errors. Have a nice day. Best Regards, Ahmad El Masri

Hello @almeos, If the potential problem being claimed is still presistent please drop an email to support@pycom.io with the logs and screenshots. I will have this redirected to our teams. Thank you.

@goldfishalpha thanks for your reply I need to change the order of network preferences: pybytes.set_config('network_preferences', ["lte", "wifi"])

@jirkakrepl Any update?

@Johann-Fournier I have the same problems, but downgrading to r4 dosent help....

Hi All, Thank you for being patient. We have fixed the issue. Please try to read your project using the order number. Note: the Count of the months will be count from the first day you activate your sim. Let me know if you got any issues during the adding/activating a sim under Pybytes Best Regards, Ahmad EL Masri

I have same issue with Fipy. Sometimes it was online and sometimes offline, quite unstable. but last days just offline, even disconnecting and connencting to wifi manually did not help. But in device manager I can see last response in seconds

@Gijs Hi, you are referring to the 30sec logs that get printed in the REPL console ? I have put the gateway next to me and wait for it to disconnect and will let you know. thx

Depending on which hardware version of the Pysense you're using, you should load the correct pycoproc file. You can find the latest versions of the file here: https://github.com/pycom/pycom-libraries/tree/master/shields/lib pycoproc_2.py is for Pysense v2.0 X, where pycoproc_1.py is for Pysense 1. This also changes the initialisation argument. For Pysense 1, you should put py = Pycoproc(Pycoproc.PYSENSE), whereas Pycoproc 2 does not require an argument To get a working example, you can load one of the zip files from here: https://github.com/pycom/pycom-libraries/releases/tag/v2.0.0 for the correct board version

the pin configurations (except for P12, as it is connected to the antenna switch) should not make a difference in WiFi connectivity. Especially as your routers' SSID already shows up in the scan, I suspect you made a mistake in the password, or choosing the correct access point (not sure if there might be multiple around you with the same SSID, you can verify that by checking the BSSID with the routers'. Perhaps you could try to connect to an access point without a password?

@robert-hh Or to cite the last mail to us kickstarter funders. "This means our manufacturer will be shipping of items to Pycom Europe mid to late June. We will ship all items to you all in the weeks following this." But no indication that shipment has been started. I have mails like these promising progress since mid 2019. So what should I expect?

From what I understand, the custom payload filters out the keywords mentioned underneath the textbox and replace them with the appropriate data. Other than that, you can format the message how you like (it does not have to be JSON), probably within the acceptable limits of HTTP. You can carry out some tests using https://webhook.site to view what the payload would look like

Hi, Thanks for your patience. The issue is indeed with the PSRam. I cannot tell you exactly, but the coredump also pointed me to a similar section, explaining the external ram could not be initialized. Can you contact me at support@pycom.io and we will handle it from there!

That means you initially registered (probably accidentally) your device as a Sipy. Could you PM me your device WMAC and we can correct that

No worries If the WDT is over 21 minutes, the fipy should try to reconnect to pybytes, shouldn't it? Yes, though it will take 21 minutes before the reset happens (it will trigger a full system reset, similar to machine.reset()). This is independent of lte.isconnected() or pybytes.isconnected(). As I mentioned before, it will send/receive a PING message from Pybytes every 10 minutes, and when there is no response, it will try again 10 minutes later. If there is still no response, it will trigger the system reset. The solution I finally found is to insert a callback in my code: lte.lte_callback(LTE.EVENT_BREAK, lte_cb_handler) If the callback has been triggered because of a disconnection, then the fipy tries to reconnect to pybytes using pybytes.connect() This the only efficient command that I found. It does work but this solution is not so good: there are too many callback occuring so that the fipy spends much time to reconnect to pybytes. When the callback triggers, you will need to check manually (by for example doing a socket.getaddrinfo() whether the BREAK was caused by a 'permanent' disconnect or something else. We also explain this in the documentation: https://docs.pycom.io/tutorials/networks/lte/#lte-connectivity-loss

@gerard-jamin I do not help with atom but you have alternatives. you can use Visual Studio Code or even ftp e.g. FileZilla