This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
I first removed my own bot, then I tried to register the Homey bot, then afterwards my bot... As from the text on the settings page, it gave me the impression that I needed to use the Homey bot if I wanted to use groups...
Anyway, so now if I send “ping” to the default Homey bot, then my own custom bot replies with “pong”. Is that the expectation?
Secondly, by doing all of this, I seem to have added myself to the list of users. but, how do I now add other users, and specifically groups?
But I do not see any users/groups under settings.
I don't know how that would even work? Where are you trying to get the users/groups from?
Should I be able to send from a flow to @telegramname directly? Or do you need to enumerate users/groups first?
Normally I would just send a telegram to a group/user by embedding the name in the url. I think that should be possible by using "naam ontvanger" (name recipient) as a variable so you can just fil in in the flow just like the message part?
I tried:
/register XXXXXXXX
and
/register@athomhomey_bot XXXXXXXX
As soon as I add an image of a hikvision IP camera, the telegram app crashes (log send to maker)
http://name:password@ipnumber/ISAPI/Streaming/channels/101/picture
Everything worked perfectly for the update
I did a "test run" on Homey and it sends my image using Telegram without a problem.
Please note:
- The apps now use official Image Tokens. They are incompatible with the old format. You will have to set it up using the new image tokens, or it will not work
- Not currently compatible with the images that you grab using the Synology app.
I did not do anything with the tokens just updated both apps.
Then there will be the problem. Later today I will reinstall both apps and see how I can setup the new tokens.
I will make "/register XXX" (XXX is your Homey unique device_id) reset the message id counter in the next version.
The problem was caused by the fact that I have Homey "remember" the last message id received, because sometimes Telegram sends the messages twice.
I used to check if the new message id was higher than the last message id, otherwise discard the message; now I just check if it is different than the last one. So if it doesn't work, just do it two or three times and it should succeed
I noticed that that the ID used for register didn’t change, is that correct?
Did you invite the bot into the group?
With a group chat or with a normal chat?
Please also doublecheck if the URL for the Telegram webhook is correctly set:
https://api.telegram.org/bot<CUSTOMTOKEN>/setWebhook?url=https://webhooks.athom.com/webhook/5795eeea20ad3acc0b868ced
(replace <CUSTOMTOKEN> with the token of your custom bot).
Although ive since removed my custom bot.