Up until 28th April I used node-red-node-twitter extensively with the Twitter API v1.1 within my House Alarm system to provide notifications and in conjunction with IFTTT and location on my mobile to activate and deactivate the alarm system. Unfortunately the Twitter API v1.1 which node-red-node-twitter utilises appears to have been deprecated and replaced with v2.0. Are there any plans to update node-red-node-twitter to use v2.0 of the API?
No. Nothing is planned on my part. Given how restricted the API has become with no free access it isn't something that I'm strongly compelled to spend time on.
If anyone in the community is interested in working on it, you'll be welcome to.
I would recommend switching to another API. Possibly Telegram or even Matrix/Element.
Personally, I would never have trusted Twitter with alarm data even before Musk screwed it up.
There is a limited free access Twitter API Documentation | Docs | Twitter Developer Platform.
For write-only use cases and testing the Twitter API
- Low rate-limit access to v2 tweet posting and media upload endpoints
- 1,500 Tweets per month - posting limit at the app level
- 1 app ID
- Login with Twitter
- Cost: Free
BUT not sure how write-only would allow one to test the Twitter API.
Thanks, I guess I will have to find another way to get notifications.
The system worked fine until April 28th. Thanks, I'll have a look at your suggestions.
There is an open PR for this node here:
If this were accepted, would it resolve your issue?
@PdeJ have you looked at:
Provided you have access to the v2 API, you should be able to integrate this as a function node without issue. The v2-specific documentation is still valid and working (as of writing), but the future of Twitter v2 API support does not look bright at all...
On the node-red side you will need to install the module before setting up your streams etc.
Thanks Wooferguy and Chuank, but I will have to leave it to someone more competent to implement any changes to the Twitter node.