Dr. McKay

Please read about asynchronous JavaScript and callbacks. getPersonas does not return anything useful, you need to provide a callback and wait for the response there.

How often is your internet going down? You could periodically make some request that results in a response, and reconnect if you don't get a response in x time after y attempts.

Wrong module. You aren't using steam-tradeoffer-manager. https://httpstatuses.com/429

The first error means that the data is temporarily unavailable, and you should try again. It's Steam's fault. The second error: https://steamerrors.com/26

When Steam goes down the application will be notified of the connection being closed. Experimental does mean that there could be problems, yes.

Your cookies need to be valid, of course. You also need to send more data when accepting a trade offer. For example, you need to include the offer ID in the POST fields, along with some other stuff.

Linux/Unix doesn't seem to think it very important to notify applications of closed TCP connections when the network goes down. You could use node-steam-client's experimental UDP support if this is a situation that will affect you regularly: var SteamClient = require('steam-client'); var client = new SteamClient.CMClient(SteamClient.EConnectionProtocol.UDP); var user = new SteamUser(client);

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#getconfirmationstime-key-callback

This isn't really the right place to ask for SteamBot help.

loggedOn will be emitted when it reconnects.

You don't need to delete all those properties; steam-tradeoffer-manager will just ignore them. You need to provide a callback to offer.send()

That's slightly tricky with async requests. You may want to use a module like https://www.npmjs.com/package/async

I have never attempted to sign into Steam from PHP. I believe there might be libraries out there that do it, but I can't help you there.

autoRelogin will handle all cases in which it gets disconnected from Steam, including if your Internet goes down. It can't actually tell the difference, really. Steam being unavailable is Steam being unavailable, regardless of whose end the problem is on.

I don't believe there's currently an API or an existing module/library that will do that for you, sorry.

Are you logged in? You need to be logged in to use that.

You can handle trade offers with steam-tradeoffer-manager.

You'll need to either get more IP addresses or make less requests.

You've provided no details, but I can hazard a guess and say that tradeRequest isn't what you're looking for. It's emitted when a Steam real-time trading request is received, not when a trade offer is received.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#getconfirmationstime-key-callback

I believe Steam will sometimes lock down your trades while you're accepting an offer, but I'm not certain about the exact conditions.

You need to call setCookies and wait for its callback before you try to do anything else.

Steam is never in excellent condition, especially at the times when you're getting these errors.

What is the error you're getting?

There should be more output.