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.
User avatar
heggink
Posts: 534
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: after update: no notifications from telegram

Post by heggink » Tuesday 29 August 2017 21:38

As said, copy and compile/build solves it. Happy to solicit my rpi3 compile. Anyone with some generally available storage?
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

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 » Tuesday 29 August 2017 21:50

I'd assume that Domoticz dev team would like to understand what's wrong and how to make sure it's not happening again.

I know we're talking about a beta (and that it sounds like releases are now more frequent than they used to be couple of years ago, meaning stable version does not mean 2 years old version anymore), but broken http / notifications for a home automation system is kind of major issue.

Just to clarify: I'm not blaming anyone (that would be completely wrong when you see the time spent by gizmocuz and others on Domoticz) - just trying to see how we can help finding the issue - and building locally won't help as it seems the issue can only be reproduced with binary versions.

User avatar
heggink
Posts: 534
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: after update: no notifications from telegram

Post by heggink » Tuesday 29 August 2017 21:56

We all want new stuff but we are also quite dependent on a stable system. A decent backup allows a roll back in case of mishap. Obviously anyone would want to understand how to prevent but that's no substitute for an incremental backup.
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

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 » Tuesday 29 August 2017 22:01

Sure - I've hourly backups, and reverting to stable was a no brainer, so I can't say I've been really impacted anyhow by this issue. Again, I'm more in a "if there is anything we can do to help please yell we'll be very happy to do it" mood - definitely not ranting because it's not fixed yet.

BTW - https://github.com/domoticz/domoticz/issues/1782 - Sounds like @gizmocuz is reinstalling the build system.

User avatar
heggink
Posts: 534
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi
Domoticz version: V4.9999
Location: NL
Contact:

Re: after update: no notifications from telegram

Post by heggink » Tuesday 29 August 2017 22:03

Yup. Noticed. Couldn't wait
Pi3, latest beta
RFXCOM, z-wave (AEOTEC, switches, temhum, pir, contacts),
Plugwise2py, P1 'smart'meter & solar panel
Alexa, Wifi Cams motion detection
ESP: relays, PIR & Temp/TempHum
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest

oxedgar1
Posts: 4
Joined: Tuesday 02 June 2015 20:40
Target OS: -
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by oxedgar1 » Saturday 09 September 2017 7:52

Hi have the samme problem... ALL notifications cannot work with any params on the last beta version...

remkolodder
Posts: 7
Joined: Sunday 02 August 2015 23:52
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by remkolodder » Saturday 09 September 2017 11:10

sysedit wrote:
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 :(
+1;

benbammens
Posts: 30
Joined: Tuesday 30 May 2017 19:43
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by benbammens » Tuesday 19 September 2017 11:52

Problem solved with the most recent beta here...

mgrom
Posts: 6
Joined: Saturday 07 April 2018 8:11
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: after update: no notifications from telegram

Post by mgrom » Thursday 12 April 2018 9:20

I've got the same problem:

Code: Select all

Version: 3.9208
Build Hash: ff40091a
Compile Date: 2018-04-08 17:15:17

Code: Select all

2018-04-12 08:38:46.633 Notification: Domoticz test
2018-04-12 08:38:46.829 Error: Pushover:
2018-04-12 08:38:46.830 Notification sent (pushover) => Failed
2018-04-12 08:38:46.840 Active notification Subsystems: (0/14)

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

Re: after update: no notifications from telegram

Post by SweetPants » Sunday 15 April 2018 11:40

Please don't hijack an existing topic. This one is about Telegram notifications, yours is about Pushover. You better open a new topic.
Ubuntu 16.04.3 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)

funnybu
Posts: 6
Joined: Monday 07 May 2018 14:48
Target OS: Raspberry Pi
Domoticz version: 3.9272
Location: Russia, Novosibirsk
Contact:

Re: after update: no notifications from telegram

Post by funnybu » Sunday 13 May 2018 15:54

is any way to get notification from last beta?

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

Re: after update: no notifications from telegram

Post by SweetPants » Tuesday 15 May 2018 20:12

funnybu wrote:
Sunday 13 May 2018 15:54
is any way to get notification from last beta?
Notification on latest Beta 3.9440 is just working fine on my side.
Ubuntu 16.04.3 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
EdddieN
Posts: 452
Joined: Wednesday 16 November 2016 12:31
Target OS: Raspberry Pi
Domoticz version: 4.9700
Location: Scotland
Contact:

Re: after update: no notifications from telegram

Post by EdddieN » Tuesday 15 May 2018 21:53

SweetPants wrote:
Tuesday 15 May 2018 20:12
funnybu wrote:
Sunday 13 May 2018 15:54
is any way to get notification from last beta?
Notification on latest Beta 3.9440 is just working fine on my side.
Running same version, however I do not seem to get the notifications to work under Blockly. Does it work for you a simple IF somethign ON then send Telegram?

On simple notification, like directly on a device it works ok.
11101101 - www.machinon.com

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

Re: after update: no notifications from telegram

Post by SweetPants » Wednesday 16 May 2018 7:28

EdddieN wrote:
Tuesday 15 May 2018 21:53

Running same version, however I do not seem to get the notifications to work under Blockly. Does it work for you a simple IF somethign ON then send Telegram?

On simple notification, like directly on a device it works ok.
I do not use Blockly but dzVentz as Blockly is limited in features and new development.
Ubuntu 16.04.3 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
EdddieN
Posts: 452
Joined: Wednesday 16 November 2016 12:31
Target OS: Raspberry Pi
Domoticz version: 4.9700
Location: Scotland
Contact:

Re: after update: no notifications from telegram

Post by EdddieN » Wednesday 16 May 2018 8:24

But does it work for you?
11101101 - www.machinon.com

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

Re: after update: no notifications from telegram

Post by SweetPants » Wednesday 16 May 2018 18:11

EdddieN wrote:
Wednesday 16 May 2018 8:24
But does it work for you?
Yes, this blocky works with Telegram
bl_telegram.png
bl_telegram.png (22.17 KiB) Viewed 415 times
Ubuntu 16.04.3 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)

funnybu
Posts: 6
Joined: Monday 07 May 2018 14:48
Target OS: Raspberry Pi
Domoticz version: 3.9272
Location: Russia, Novosibirsk
Contact:

Re: after update: no notifications from telegram

Post by funnybu » Wednesday 16 May 2018 21:20

i solve my problem. Now i have Telegram notification on Domoticz 3.9272

I use socks5, bkz in Russia Telegram blocked now.

Settings -> Notification
tele1.png
tele1.png (22.8 KiB) Viewed 405 times
And telegram.sh

Code: Select all

#! /bin/bash

# Proxy setup
PROXY_IP="80.*.*.*"
PROXY_PORT="1080"
PROXY_USER="al***"
PROXY_PAS="*****"

# Bot setup
BOT_ID="bot********"
TOKEN="*********"
CHAT_ID="******"

curl -x socks5://$PROXY_USER:$PROXY_PAS@$PROXY_IP:$PROXY_PORT "https://api.telegram.org/$BOT_ID:$TOKEN/sendMessage?chat_id=$CHAT_ID&text=$1"

If u dont't need proxy, just use this

Code: Select all

#! /bin/bash

# Bot setup
BOT_ID="bot********"
TOKEN="*********"
CHAT_ID="******"

curl "https://api.telegram.org/$BOT_ID:$TOKEN/sendMessage?chat_id=$CHAT_ID&text=$1"

User avatar
EdddieN
Posts: 452
Joined: Wednesday 16 November 2016 12:31
Target OS: Raspberry Pi
Domoticz version: 4.9700
Location: Scotland
Contact:

Re: after update: no notifications from telegram

Post by EdddieN » Wednesday 16 May 2018 22:36

SweetPants wrote:
Wednesday 16 May 2018 18:11
EdddieN wrote:
Wednesday 16 May 2018 8:24
But does it work for you?
Yes, this blocky works with Telegram
bl_telegram.png
thanks for confirming that, obviously I have something broken then...
11101101 - www.machinon.com

maxcross
Posts: 8
Joined: Thursday 25 January 2018 14:23
Target OS: Raspberry Pi
Domoticz version: 3.8590
Contact:

Re: after update: no notifications from telegram

Post by maxcross » Monday 27 August 2018 20:07

Hello guys, I also have a problem with Telegram notifications, in my log I see just:

Code: Select all

2018-08-27 21:04:36.997 Status: Notification: Domoticz test
2018-08-27 21:04:37.087 Notification sent (telegram) => Failed
2018-08-27 21:04:37.100 Active notification Subsystems: telegram (1/13)
2018-08-27 21:04:37.087 Error: Telegram:
Version: 4.9822
Platform: Raspberry Pi3

Is there some news related to this issue? I saw that many users faced with that issue

jannnfe
Posts: 22
Joined: Tuesday 30 January 2018 1:27
Target OS: Linux
Domoticz version: Beta
Location: Germany
Contact:

Re: after update: no notifications from telegram

Post by jannnfe » Wednesday 29 August 2018 19:32

Any news to get the telegram bot working with the newest beta. Like to send a snapshot of my camera to telegram

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 5 guests