Vodafone SIM in Spain not working [solved, wrong DNS sever]

[claus]

GREAT!! Thanks a lot, it is working!

[Guillermo del Campo]

@Gijs Hello Gijs! I'm having a similar issue and I don't know what else to try.

I have a Vodafone SIM bought from pycom, but I am not able at all to connect to Pybytes using LTE. If I do it via WiFi, everything works as expected.

This is mi pybytes_config.json file:

{"wifi": {"ssid": "", "password": ""}, "wlan_antenna": 0, "dump_ca": false, "server": "mqtt.pybytes.pycom.io", "ssl": false, "lte": {"apn": "pycom.io", "cid": 1, "reset": false, "carrier": "standard", "band": 20, "type": "IP"}, "device_id": "xxxx", "network_preferences": ["lte"], "ota_server": {"port": 443, "domain": "software.pycom.io"}, "pybytes_autostart": false, "username": "xxxx"}

When I try to connect, it certainly says:

>>> pybytes.connect()
Initialized watchdog for WiFi and LTE connection with timeout 1260000 ms
LTE connection established
connect_lte with start_mqtt is now removed please call communication_protocol or start_mqtt directly
Connected to MQTT mqtt.pybytes.pycom.io
Pybytes connected successfully (using the built-in pybytes library)

But when I try:

>>> pybytes.send_ping_message()

it stalls forever... same if I try to send a signal. Moreover, if I try:

>>> socket.getaddrinfo('www.pycom.io', 80)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 202] EAI_FAIL

Please, can you, or anyone else, provide any help? I'm going crazy...

[Gijs]

Did you try the suggestion above? Let me know what the result is of socket.dnsserver() . As mentioned above, the EAI_FAIL error is related to an issue with the DNS server

[Guillermo del Campo]

@Gijs Yes... I tried with no success. This is the output:

>>> socket.dnsserver()
('0.0.0.0', '0.0.0.0')

[Gijs]

Please try setting the dns servers manually before starting pybytes, as mentioned in the other ticket. This is an issue with Vodafone where the DNS servers do not get set correctly. We talk about it in the other thread: https://forum.pycom.io/topic/6350/error-while-connecting-pybytes-with-lte
Like this:

from network import LTE
import socket
lte = LTE()
lte.attach()
...
lte.connect()
...
socket.dnsserver(0, '172.31.32.100')
socket.dnsserver(1, '172.31.32.100')
# check if get addr info works
print(socket.getaddrinfo('www.pycom.io', 80))
#make sure to have pybytes loaded, but not autoconnect at boot, if pybytes is not loaded, use this: https://docs.pycom.io/pybytes/api/
pybytes.start()

Sorry I did not get around to testing the script completely, but you should be able to make it work using a procedure like this
Best,
Gijs

[Guillermo del Campo]

@Gijs I also tried that, as I saw it on other post but it does not work... Here is the output:

Not starting Pybytes as auto-start is disabled
Pycom MicroPython 1.20.2.r4 [v1.11-ffb0e1c] on 2021-01-12; FiPy with ESP32
Pybytes Version: 1.6.1
Type "help()" for more information.
>>> from network import LTE
>>> import socket
>>> lte=LTE()
>>> lte.attach(band=20, apn="pycom.io")
>>> lte.isattached()
True
>>> lte.connect()
>>> lte.isconnected()
True
>>> socket.dnsserver(0, '172.31.16.100')
>>> socket.dnsserver(1, '172.31.32.100')
>>> socket.dnsserver()
('172.31.16.100', '172.31.32.100')
>>> print(socket.getaddrinfo('www.pycom.io', 80))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 202] EAI_FAIL

[Gijs]

Sorry, my mistake. The vodafone simcards do not resolve pycom.io, but should be able to resolve pybytes.pycom.io!
Let me know if that works for you

[Guillermo del Campo]

@Gijs Oh yes!! Thank you so much :) Now it works and I can send messages!

[Gijs]

Im looking to add this to the documentation, as it seems an intermittent issue, could you recommend the place where you first looked for this?

Let me know

[Guillermo del Campo]

@Gijs I think it should be here: https://pycom.io/webshop-2/services/cellular-services/faq-for-vodafone-pycoms-nb-iot-services/ or maybe somewhere around here: https://docs.pycom.io/tutorials/networks/lte/
I believe it's also important to highlight that the modem firmware may need to be updated and modified to the NB-IoT version, since I took some to realise that as well... my FiPys come with the LTE-M version installed.