Did anyone get the OTP thing to work? When I get the code via email and change the status of the text.volvo_otp entity, nothing happens. The add-on did its 15 retries and thatâs it. When I restart it, it creates a new OTP, so I am always ârunning behindâ. What am I doing wrong?
I updated the plugin, filled in the verification code in the âVolvo OTPâ entity and it worked immediately.
When I was beta-testing this last month at first I didnât get the verification code on time because my mail client marked the Volvo email as spam. Itâs just a matter of filling in the âVolvo OTPâ code in time. I immediately received an email with the verification code when starting the add-on.
@Dielee is there a possibility to extend the time between the 15 retries to make sure people can copy the verification code from the email?
How do i trigger new code?
I reloaded Addon and MQTT but both didn trigger new code. I did found Volvo OTP and try to enter old code via âdeveloper toolâ.
I do get a new code whenever I restart the Volvo2Mqtt add-on.
However, I update the âVolvo OTPâ by navigating to all entities (Settings > Devices & services > Entities) and selecting the âVolvo OTPâ entity.
Setting state via Developer tools didnât work for me either.
after stop and start the volvo add-on, i received new code and updated it quickly as you described and it seems to be working. Thx for the quick help, appriciated.
I defined the value of the OTP from the Developer Tools
But I have this error
May 27 13:27:44 volvo2mqtt [106] - INFO: Waiting for otp code⌠Please check your mailbox and post your otp code to the following mqtt topic âvolvoAAOS2mqtt/otp_codeâ. Retry 14/15
Traceback (most recent call last):
File â/volvoAAOS2mqtt/main.pyâ, line 15, in
authorize()
File â/volvoAAOS2mqtt/volvo.pyâ, line 71, in authorize
response = send_otp(auth_session, response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File â/volvoAAOS2mqtt/volvo.pyâ, line 155, in send_otp
raise Exception (âNo OTP found, extingâŚâ)
Exception: No OTP found, extingâŚ
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence â\dâ
âpatternâ: â\d{6}â,
Hi Dielee,
I was unable to make it work with version 1.9.0 : after configuring the OTP on the volvo_otp entity and restarting the add-on, I was getting a new OTP passwork through e-mail.
I just saw that a version 1.9.1 of the add-on was available and it seems to be fine now.
Neverthless I am getting an syntax warning in the logs, but this doesnât prevent the add-on to work correctly.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence â\dâ
âpatternâ: â\d{6}â,
Heya all. I got myself a MY2023 XC40 in the UK, set up the Volvo account, and bumped into configuration set up problems with answers spread out in this thread. To even get config to save:
I needed a password without a special character.
I needed a short API of a dozen numbers unlike the massive token.
I have MQTT running doing other services, so I think thatâs fine.
Q1. The config saves with âGBâ or with âen_GBâ as the locale - which one is correct?
Q2. The log spits out some errors when it runs, and then successfully stops>
May 27 15:41:45 volvo2mqtt [106] - INFO: Starting volvo2mqtt version v1.9.0
Traceback (most recent call last):
File â/volvoAAOS2mqtt/main.pyâ, line 14, in
connect()
File â/volvoAAOS2mqtt/mqtt.pyâ, line 38, in connect
client.connect(settings[âmqttâ][âbrokerâ], port)
File â/usr/lib/python3.12/site-packages/paho/mqtt/client.pyâ, line 914, in connect
return self.reconnect()
^^^^^^^^^^^^^^^^
File â/usr/lib/python3.12/site-packages/paho/mqtt/client.pyâ, line 1044, in reconnect
sock = self._create_socket_connection()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File â/usr/lib/python3.12/site-packages/paho/mqtt/client.pyâ, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File â/usr/lib/python3.12/socket.pyâ, line 828, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File â/usr/lib/python3.12/socket.pyâ, line 963, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -5] Name has no usable address
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped