Tamás, I think that's an issue with the Pushover server. I've had the same effect during my tests, when repeating the request, it would eventually be successful. The issue turned up only with the pushover server. I also recognized the Pushover service checks the user agent, you need to supply a standard agent ID to get it to reply normally. "curl/7.60.0" works, the OVMS agent doesn't. I think the Pushover component needs to address this by a) supplying a user agent & b) doing retries on error. Regards, Michael Am 19.02.20 um 20:47 schrieb Tamás Kovács:
I updated my fork with the main repo and now pushover not working. I send a test message, and get the following in logs: I (548904) webserver: HTTP GET /cfg/notification I (553254) webserver: HTTP POST /cfg/notification I (553284) pushover: Sending message teszt with priority 0 E (570654) mongoose: mg_ssl_mbed_log 0x3fa44e14 mbedtls_ssl_fetch_input() returned -1 (-0x0001) E (570654) mongoose: mg_ssl_mbed_log 0x3fa44e14 ssl_get_next_record() returned -1 (-0x0001) E (570654) mongoose: mg_ssl_mbed_log 0x3fa44e14 mbedtls_ssl_read_record() returned -1 (-0x0001) E (570654) mongoose: mg_ssl_if_mbed_err 0x3fa44e14 SSL error: -1 I (570654) pushover: PushoverMongooseCallback(MG_EV_CONNECT=-3:) E (570654) pushover: Connection failed I (570664) ovms-server-v2: Send MP-0 PIConnection failed
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26