after update: no notifications from telegram

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
snuiter
Posts: 72
Joined: Saturday 17 June 2017 12:30
Target OS: Raspberry Pi
Domoticz version: beta
Contact:

after update: no notifications from telegram

Post by snuiter » Thursday 24 August 2017 17:27

After the latest beta upgrade V3.8363 I am not receiving telegram notifications anymore which always worked fine. In the settings menu I pushed the test button but nothing happens. This is what happens in the error log.

2017-08-24 17:09:16.956 Error: HTTP:
2017-08-24 17:09:16.956 Error: Notification sent (http) => Failed
2017-08-24 17:17:57.727 Error: HTTP:
2017-08-24 17:17:57.727 Error: Notification sent (http) => Failed
2017-08-24 17:23:40.339 Error: HTTP:
2017-08-24 17:23:40.339 Error: Notification sent (http) => Failed

Any ideas, suggestions what this could causing this or what I can do more tests to find the root cause?

User avatar
Phantom
Posts: 83
Joined: Saturday 31 December 2016 15:47
Target OS: Raspberry Pi
Domoticz version: 3.8922
Location: The Netherlands
Contact:

Re: after update: no notifications from telegram

Post by Phantom » Thursday 24 August 2017 17:48

Same problem here with version V3.8360 but with using Google Cloud Messaging

2017-08-24 14:59:51.176 Error: GCM: Could not send message, HTTP Error
2017-08-24 14:59:51.176 Error: Notification sent (gcm) => Failed
2017-08-24 15:00:05.403 Error: GCM: Could not send message, HTTP Error
2017-08-24 15:00:05.404 Error: Notification sent (gcm) => Failed

mivo
Posts: 119
Joined: Friday 21 April 2017 8:58
Target OS: Raspberry Pi
Domoticz version: beta
Location: Czechia
Contact:

Re: after update: no notifications from telegram

Post by mivo » Thursday 24 August 2017 18:05

Hi,

I have similar problem in 3.8360 and 8363. DarkSky Weather Lookup returns DarkSky: Error getting http data!
Reverted back to 8356 and everyting is OK
My toys:
Raspberry Pi 3 + UPS PIco HV3.0 A Stack
Minibian (Raspbian Jessie) + Domoticz beta
RFLink 433 Gateway, 1wire DS18B20 temp sensors (GPIO)
RaZberry module + 2x Comet Z-Wave + Z-wave socket
---
Plugins: WeMo Switch, UPS PIco HV3.0A on GitHub

sysedit
Posts: 17
Joined: Saturday 05 October 2013 21:55
Target OS: Linux
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by sysedit » Thursday 24 August 2017 18:26

Same with email, prowl and http notifications:


2017-08-24 18:25:00.124 Error: HTTP:
2017-08-24 18:25:00.124 Error: Notification sent (http) => Failed
2017-08-24 18:25:00.248 Error: SMTP Mailer: Error sending Email to: !
2017-08-24 18:25:00.248 Error: Failed to send Email notification!
2017-08-24 18:25:00.248 Error: Notification sent (email) => Failed
2017-08-24 18:25:00.272 Error: Prowl:
2017-08-24 18:25:00.272 Error: Notification sent (prowl) => Failed

snirf :(

User avatar
blacksn0w
Posts: 118
Joined: Friday 10 March 2017 23:27
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Germany
Contact:

Re: after update: no notifications from telegram

Post by blacksn0w » Thursday 24 August 2017 18:26

Same here with Pushover, seems to be an overall Notification issue.
Migration in progress, hello Home Assistant.

User avatar
LouiS22
Posts: 502
Joined: Friday 27 February 2015 14:21
Target OS: Raspberry Pi
Domoticz version: beta
Location: Budapest, Hungary
Contact:

Re: after update: no notifications from telegram

Post by LouiS22 » Thursday 24 August 2017 18:30

Same with GCM :(

User avatar
DarkoBG
Posts: 7
Joined: Friday 26 August 2016 22:36
Target OS: Raspberry Pi
Domoticz version: beta
Location: Serbia
Contact:

Re: after update: no notifications from telegram

Post by DarkoBG » Thursday 24 August 2017 18:48

Same with all notifications system :(

SweetPants
Posts: 2397
Joined: Friday 12 July 2013 21:24
Target OS: Linux
Domoticz version: V4.10267
Location: The Netherlands
Contact:

Re: after update: no notifications from telegram

Post by SweetPants » Thursday 24 August 2017 21:04

Hmmm, i'm on V3.8363 and see no problems with Telegram (bot) notifications.
Ubuntu 16.04.5 LTS, Intel NUC, MySensors 2.3.0-alpha, Pro Mini 3.3/8M RFM69(HW), ESP8266 (SDK2.2.0), Sonoff, RFLink, RFXcom, MQTT, NodeRed, Domoticz Beta (from source)

User avatar
LouiS22
Posts: 502
Joined: Friday 27 February 2015 14:21
Target OS: Raspberry Pi
Domoticz version: beta
Location: Budapest, Hungary
Contact:

Re: after update: no notifications from telegram

Post by LouiS22 » Thursday 24 August 2017 21:14

SweetPants wrote:
Thursday 24 August 2017 21:04
Hmmm, i'm on V3.8363 and see no problems with Telegram (bot) notifications.
Hm that's weird.

SweetPants
Posts: 2397
Joined: Friday 12 July 2013 21:24
Target OS: Linux
Domoticz version: V4.10267
Location: The Netherlands
Contact:

Re: after update: no notifications from telegram

Post by SweetPants » Thursday 24 August 2017 21:29

Tested email too:

2017-08-24 21:28:32.278 Notification sent (http) => Success
2017-08-24 21:28:32.444 Notification sent (email) => Success
Ubuntu 16.04.5 LTS, Intel NUC, MySensors 2.3.0-alpha, Pro Mini 3.3/8M RFM69(HW), ESP8266 (SDK2.2.0), Sonoff, RFLink, RFXcom, MQTT, NodeRed, Domoticz Beta (from source)

mivo
Posts: 119
Joined: Friday 21 April 2017 8:58
Target OS: Raspberry Pi
Domoticz version: beta
Location: Czechia
Contact:

Re: after update: no notifications from telegram

Post by mivo » Thursday 24 August 2017 21:32

SweetPants wrote:
Thursday 24 August 2017 21:04
Hmmm, i'm on V3.8363 and see no problems with Telegram (bot) notifications.
Hi SweetPants,

please what platform - RPi or x86 ? Jessie or Stretch (new install, or upgraded) ? Precompiled, or compiled yourself ?

Thanks
My toys:
Raspberry Pi 3 + UPS PIco HV3.0 A Stack
Minibian (Raspbian Jessie) + Domoticz beta
RFLink 433 Gateway, 1wire DS18B20 temp sensors (GPIO)
RaZberry module + 2x Comet Z-Wave + Z-wave socket
---
Plugins: WeMo Switch, UPS PIco HV3.0A on GitHub

SweetPants
Posts: 2397
Joined: Friday 12 July 2013 21:24
Target OS: Linux
Domoticz version: V4.10267
Location: The Netherlands
Contact:

Re: after update: no notifications from telegram

Post by SweetPants » Thursday 24 August 2017 21:52

mivo wrote:
Thursday 24 August 2017 21:32
please what platform - RPi or x86 ? Jessie or Stretch (new install, or upgraded) ? Precompiled, or compiled yourself ?
Ubuntu 14.04 LTS 32-bit, Intel NUC, V3.8363 compiled from source (git upgrade)
Test system, Ubuntu 16.04 LTS, Dell LapTop 64-bit, compiled from source (git upgrade)
Ubuntu 16.04.5 LTS, Intel NUC, MySensors 2.3.0-alpha, Pro Mini 3.3/8M RFM69(HW), ESP8266 (SDK2.2.0), Sonoff, RFLink, RFXcom, MQTT, NodeRed, Domoticz Beta (from source)

sysedit
Posts: 17
Joined: Saturday 05 October 2013 21:55
Target OS: Linux
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by sysedit » Thursday 24 August 2017 22:01

mivo wrote:
Thursday 24 August 2017 21:32
SweetPants wrote:
Thursday 24 August 2017 21:04
Hmmm, i'm on V3.8363 and see no problems with Telegram (bot) notifications.
Hi SweetPants,

please what platform - RPi or x86 ? Jessie or Stretch (new install, or upgraded) ? Precompiled, or compiled yourself ?

Thanks
On my side I'm on a Rpi3, using raspbian Jessie. Upgrade, but precompiled (using updatebeta) script.
3.8363 fails.
reverting (i.e. just running updaterelease) to 3.8153 works.

mivo
Posts: 119
Joined: Friday 21 April 2017 8:58
Target OS: Raspberry Pi
Domoticz version: beta
Location: Czechia
Contact:

Re: after update: no notifications from telegram

Post by mivo » Thursday 24 August 2017 22:06

SweetPants wrote:
Thursday 24 August 2017 21:52
Ubuntu 14.04 LTS 32-bit, Intel NUC, V3.8363 compiled from source (git upgrade)
Test system, Ubuntu 16.04 LTS, Dell LapTop 64-bit, compiled from source (git upgrade)
OK, thanks. It makes sense. Problem is now probably with precompiled beta binaries for RPi.
My toys:
Raspberry Pi 3 + UPS PIco HV3.0 A Stack
Minibian (Raspbian Jessie) + Domoticz beta
RFLink 433 Gateway, 1wire DS18B20 temp sensors (GPIO)
RaZberry module + 2x Comet Z-Wave + Z-wave socket
---
Plugins: WeMo Switch, UPS PIco HV3.0A on GitHub

User avatar
DarkoBG
Posts: 7
Joined: Friday 26 August 2016 22:36
Target OS: Raspberry Pi
Domoticz version: beta
Location: Serbia
Contact:

Re: after update: no notifications from telegram

Post by DarkoBG » Thursday 24 August 2017 22:09

I use Pi 2, Raspbian Jessie. Upgrade, but precompiled (using updatebeta) script.
3.8363 fails.

User avatar
andreo
Posts: 30
Joined: Friday 07 August 2015 21:00
Target OS: Raspberry Pi
Domoticz version: 3.8153
Location: Anna Paulowna, Netherlands
Contact:

Re: after update: no notifications from telegram

Post by andreo » Thursday 24 August 2017 22:33

Same problem here with version V3.8363

Error: DarkSky: Error getting http data!.
Greetz Andre.

DavidB
Posts: 12
Joined: Tuesday 25 November 2014 18:44
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by DavidB » Thursday 24 August 2017 22:38

Ditto Dark Sky and Telegram not working

Haringstad
Posts: 27
Joined: Tuesday 22 November 2016 10:54
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by Haringstad » Friday 25 August 2017 9:16

I have the same issues on Rpi 3, Raspbian Jessie, Domoticz 3.8364.

Not working:
  • NMA
    EvoHome API
    DarkSky

JulzJulz
Posts: 1
Joined: Friday 25 August 2017 12:15
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by JulzJulz » Friday 25 August 2017 14:03

Same issue with GCM and Email notifications since beta update 3.8363 and again in 3.8364.

Platform is Raspbian GNU/Linux 8 (jessie) on Pi3,
Kernel 4.4.38-v7+ precompiled as it was in the repo / never rebuilt locally

I've been running Domoticz beta release on this device since this time last year and have never had any issues with notifications up until the last few days.

Here's the logging for an Email test:
2017-08-25 21:09:37.360 Error: SMTP Mailer: Error sending Email to: !
2017-08-25 21:09:37.360 Error: Failed to send Email notification!
2017-08-25 21:09:37.361 Error: Notification sent (email) => Failed
2017-08-25 21:09:37.373 Active notification Subsystems: email, gcm (2/12)

And logging from using the "Send Notification" feature:
2017-08-25 21:19:34.522 Error: SMTP Mailer: Error sending Email to: !
2017-08-25 21:19:34.522 Error: Failed to send Email notification!
2017-08-25 21:19:34.522 Error: Notification sent (email) => Failed
2017-08-25 21:19:45.040 Error: GCM: Could not send message, HTTP Error
2017-08-25 21:19:45.041 Error: Notification sent (gcm) => Failed
2017-08-25 21:19:52.559 Error: HTTP:
2017-08-25 21:19:52.559 Error: Notification sent (http) => Failed
2017-08-25 21:19:52.559 Kodi Notification (224.0.0.1:9777, TTL 5): Test Test Test, This test will probably fail right?, Icon /home/pi/domoticz/www/images/logo.png
2017-08-25 21:19:52.560 Notification sent (kodi) => Success


Some peculiarities:

- Kodi notifications still succeed
- the SMTP Mailer error doesn't show any 'TO' address
- Nothing further after the "Error: HTTP: " within the same line, looks a bit odd like it should print an HTTP URL
- After upgrading with ./updatebeta to 3.8364, upon first login I noticed the "Enabled" checkbox had unchecked itself within the Email settings page.


Some random troubleshooting I tried:

- blanking out the email settings and re-entering, applying, etc.
- tried setting the SMTP server address back to its raw IP (to ensure not a failed DNS lookup)
- toggling the GCM enable setting, applied settings then reverted back again
- checked system time setting was synced to NTP server (just on a hunch)
- did an apt-get update & upgrade (*NOT* dist-upgrade) with no failed queries or timeouts for this whatsoever.

Does anyone have any further ideas about things to try? :?:


Edit: Also rolled back to stable v3.8153 with ./updaterelease and the notifications are working again so it's definitely something broken in the beta builds.

Thanks
Julian

martk
Posts: 30
Joined: Monday 14 March 2016 14:10
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by martk » Friday 25 August 2017 14:48

Same problem here, also "Nest: Error login!" error since this update.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests