how do i send a message to a channel.

[Khyretos]

i can connect and recieve messages but i can only respond when i recieve a message

i made a very simple function to send a message to a channel but i keep getting this error:

Uncaught (in promise) Not connected to server.

this is the function:

function sendMessage(message) {
	client.join(settings.TWITCH.CHANNEL_NAME);
	client.say(settings.TWITCH.CHANNEL_NAME, message);
}

i just want to know how to send a simple message.

thanks in advance.

[Khyretos]

i dont know if this is the correct way but this is what i came up with:

const tmi = require('tmi.js');
let message = ''

const client = new tmi.Client({
	options: {
		skipUpdatingEmotesets: true,
	},
	identity: {
		username: config.settings.TWITCH.USERNAME,
		password: `oauth:${config.settings.TWITCH.OAUTH_TOKEN}`,
	},
	channels: [config.settings.TWITCH.CHANNEL_NAME],
});

client.on('connected', () => {
	console.log(`${message}`);
	if(message !== ''){
		client.say(config.settings.TWITCH.CHANNEL_NAME, message);
	}
	message = '';
});

function sendMessage(text) {
	client.connect().catch(console.error);
	message = text
}

client.connect().catch(console.error);

sendMessage("test");

i dont know if there is a more effective way to do this but this is all i got.

[AlcaDesign]

I don't know why you would create a global variable to decide what to say on connect -- I would only imagine the word "connected" or "ready" or some dynamic stat about the existing state of the bot if it had to reconnect. But maybe you're creating a transient service to connect, immediately send a message, and disconnect because you're working on a cloud worker script or something. I suggest learning about the event driven model of the JavaScript engine.

function sendMessage(message) {
    return client.say(config.TWITCH.CHANNEL_NAME, message)
    .catch(console.error);
}

client.on('connected', () => sendMessage('Connected'));
// *or*
client.connect().then(() => sendMessage('Connected')).catch(console.error);

[Khyretos]

thank you, im still learning javascript. my chat tool's purpose is to recieve messages and send messages but through different ways, so depending on what he recieves he can awnser but it also needs the possibility to just send messages.

[Khyretos]

well it works now as intended, thank you for your knowledge.

const tmi = require('tmi.js');

const client = new tmi.Client({
	options: {
		skipUpdatingEmotesets: true,
	},
	identity: {
		username: config.settings.TWITCH.USERNAME,
		password: config.settings.TWITCH.OAUTH_TOKEN,
	},
	channels: [config.settings.TWITCH.CHANNEL_NAME],
});

function sendMessage(message) {
	console.log(message);
	client.say(config.settings.TWITCH.CHANNEL_NAME, message).catch(console.error);
}

client.connect().catch(console.error);

[AlcaDesign]

It takes time for things to happen on the network. (Decide to connect, lookup address in DNS, begin establishing a websocket connection (http request, then request upgrade from http to websocket, handshake), begin the IRC handshake including authorization, now it's ready) JavaScript will not wait on each line or code unless you tell it to with async/await syntax (or you can utilize Promise callbacks ("then" and "catch", etc.)). In order to send a message you must first fully connect just like the error says. You don't have to join a channel in order to send a message to that channel (but that also does take time to join a channel because of network and rate limiting). If you just want to send a message to announce that the bot is ready, use the "connected" event or by using the "connect" Promise:

client.connect()
.then(() => client.say(config.settings.TWITCH.CHANNEL_NAME, 'Connected'))
.catch(console.error);

client.on('connected', () => {
    client.say(config.settings.TWITCH.CHANNEL_NAME, 'Connected');
});
client.connect().catch(console.error);

You don't need to add "oauth:" to your token as tmi.js will do that for you.

[Khyretos]

thank you! then i will use the promise, just for context i have a simple chat window where i recieve my chat, and i wanted to complete it by having the possibility sending a message as well.

what i find weird is that i will always recieve all the messages but for some reason i have to reconnect (client.on... again?) to send a message. that is why i was so confused.

my apologies and thanks.

[AlcaDesign]

You don't have to reconnect to send a message, you just have to be connected in the first place before sending.