A set of Node Red nodes to access the Transmission torrent client remote API
Depends on nodejs package transmission v0.4.9: https://github.com/FLYBYME/node-transmission
-
Transmission List Torrents:
- Gets the current torrent list JSON data from the Transmission Instance.
- Returns an Array of the RPC JSON data in msg.payload with a msg.topic of '/transmission.v1/torrentData'
- See the 3.3 Torrent Accessors section of the RPC-Spec (https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt)
-
Transmission Add Torrent:
- Adds a new torrent via the config panel URL field or msg.url payload value containing a .torrent file or a magnet URL reference.
- Returns a single instance of the RPC JSON data in msg.payload with a msg.topic of '/transmission.v1/torrentAdd'
- See the 3.3 Torrent Accessors section of the RPC-Spec (https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt)
-
Transmission Remove Torrent:
- Remove a torrent from download queue
- NOTE : This does not trash torrent data i.e. does not remove it from disk
- Remove a torrent via the hashString value of a torrent in Transmission using 'msg.ids'.
- Returns an empty object in msg.payload with a msg.topic of '/transmission.v1/torrentRemove'
- See the 3.3 Torrent Accessors section of the RPC-Spec (https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt)
- Add the other Transmission functions from https://github.com/FLYBYME/node-transmission
- Jay Long - Author for the Initial build - jlong23
- Miguel Coquet - Corrections & Bugfixes - mcoquet
- Mark Funston - Further Documentation and Enhancements - mlfunston
This project is licensed under the Apache License, Version 2.0 - see the LICENSE file for details
- Updated minor release version
- Added various documentation
- Included code fixes to allow url to be sent to the add torrent function via msg.url
- Moved the nodes to the 'transmission' category
- Added Features:
- Remove Torrent
- Original release version
- Features:
- List Torrents
- Add Torrent