nioc / xmpp-bot

XMPP Bot is a tiny little bot making the link between XMPP conversations and webhooks.

Languages

Main projects

Home automation

Vue-dom Web front end for the home automation software Jeedom.

Jeedom Websocket Plugin to provide a client-server communication over websocket protocol.

Netatmo Node.JS API Node.js wrapper for Netatmo API.

Netatmo collector PHP script for requesting measures from Netatmo devices.

Synology SRM Node.JS API Node.js wrapper for Synology Router Manager (SRM) API.

Synology SRM PHP API PHP wrapper for Synology Router Manager (SRM) API.

XMPP

XMPP Web Lightweight web chat client for XMPP server.

XMPP Bot A tiny little bot making the link between XMPP conversations and webhooks.

Media

Web Music Player [unmaintained] Play your own music on any device connected to the web (pc, smartphone, tablet, ...). It can work as a standalone application or in your smartphone browser.

Tumblr Photo Browse [unmaintained] Android application for browsing photos posted on Tumblr.

Miscellaneous

Own My Money Stay on top of your banking from any web browser.

Registry & published packages

Skills

Tools & environment

For fun...

xmpp-bot's Issues

[Feature]

Hi, is it possible that the bot responds with an attachment instead of plain text?
Thanks

"username" in config has wrong example

"username": "[email protected]",

should really be:

"username": "botname",

connect ECONNREFUSED

Describe the bug
Hello, not sure if it's a bug but it looks like my server refuses connection to the bot and I just don't know what's the issue.

To Reproduce
Steps to reproduce the behavior:

1. Configure the bot credential and server/room info + certificate
2. Start script with "node lib/server.js"
3. Bot errors out and quits

Logs

[2023-01-20T00:08:36.041] [INFO] default - Start xmpp-bot service - version 2.2.0
[2023-01-20T00:08:36.177] [TRACE] default - Status changed to connecting
[2023-01-20T00:08:36.429] [DEBUG] default - App is started with uid: 1000
[2023-01-20T00:08:36.430] [DEBUG] default - Start HTTPS on port 8001, private key: /home/debian/sources/xmpp-bot/certs/privkey.pem, cert: /home/debian/sources/xmpp-bot/certs/fullchain.pem
[2023-01-20T00:08:36.430] [DEBUG] default - Can read private key
[2023-01-20T00:08:36.430] [DEBUG] default - Can read certificate
[2023-01-20T00:08:36.442] [INFO] default - Listening webhooks on http://localhost:8000/webhooks http://192.168.1.20:8000/webhooks http://127.0.0.1:8000/webhooks
[2023-01-20T00:08:36.442] [INFO] default - Listening webhooks on https://localhost:8001/webhooks https://192.168.1.20:8001/webhooks https://127.0.0.1:8001/webhooks
[2023-01-20T00:08:38.657] [ERROR] default - XMPP client encountered following error: connect ECONNREFUSED MYSERVER_IP_ADDRESS:5223
[2023-01-20T00:08:38.659] [WARN] default - Received 99/undefined (application is closing), disconnect from XMPP server
[2023-01-20T00:08:38.661] [DEBUG] default - Synchronize logs file

Environment (please complete the following information):

• Operating system Debian Bullseye on WSL 1 (Windows 10 x64 full up-to-date)
• npm version (npm -v) 8.19.2
• Node.js version (node -v) v18.12.1
• Code version / commit reference 2.2.0

Additional context
I'm running prosody on Debian Bullseye as well and I see no traces of login or connection attempts in logs.

[Feature] Gitea Webhooks

Is your feature request related to a problem? Please describe.
In the gitea webhook settings I cannot set a destination as body

Describe the solution you'd like
Maybe it would be possible to add a second (or more) incoming webhook(s) with a fixed destination

Additional context
The hook is working, but I get this in console:
[2024-01-22T17:11:26.262] [ERROR] default - Destination not found