diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
index e4ad6b2ca85..4a528bcf30d 100644
--- a/sass/custom/_paulus.scss
+++ b/sass/custom/_paulus.scss
@@ -495,7 +495,8 @@ a code {
   color: $primary-color;
 }
 
-twitter-widget {
+twitter-widget,
+.twitter-tweet-rendered {
   margin-left: auto;
   margin-right: auto;
 }
diff --git a/source/_posts/2020-11-23-tplink-local-access.markdown b/source/_posts/2020-11-23-tplink-local-access.markdown
new file mode 100644
index 00000000000..4f7ce51aa7a
--- /dev/null
+++ b/source/_posts/2020-11-23-tplink-local-access.markdown
@@ -0,0 +1,31 @@
+---
+title: "TP-Link offers way to add local API back"
+description: "TP-Link last week decided to publish a firmware upgrade that removed access to the local API. They are partially reverting this decision."
+date: 2020-11-23 00:01:00
+date_formatted: "November 23, 2020"
+author: Paulus Schoutsen
+author_twitter: balloob
+categories: Public-Service-Announcement
+og_image: /images/blog/2020-11-23-tplink/forum-post-send-ticket.png
+---
+
+Last week TP-Link released an update for their HS100 and HS110 plugs that removed the local API. This was done because of a "security concern". I put this in quotes because it has not been verified and this reason has been given before when removing interoperability. TP-Link communicated this via Twitter in response to a user voicing their concern.
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">There were security vulnerabilities on the plug for the local management, the latest firmware version fixed these security issues. It is suggested to use the TP-Link official App KASA to manage the plug. If you have issues, pls feel free to let us know.</p>&mdash; TP-LINK UK (@TPLINKUK) <a href="https://twitter.com/TPLINKUK/status/1328687659133399043?ref_src=twsrc%5Etfw">November 17, 2020</a>
+</blockquote>
+
+Lots of users, rightfully so, got angry. They bought the plugs assuming the local API was a feature. Removing this feature and forcing users through the TP-Link cloud sucks. It removes the one feature why TP-Link stood out among many smart plugs.
+
+After a week of angry users, it looks like TP-Link has listened… _somewhat_. They are offering a temporary solution to roll back the firmware. We haven't found any public documentation, but there are forum posts by their employees [here](https://community.tp-link.com/en/home/forum/topic/236268#topic-reply-523030) and [here](https://community.tp-link.com/en/home/forum/topic/237614#topic-reply-520984) about it.
+
+<p class='img'>
+<img src='/images/blog/2020-11-23-tplink/forum-post-send-ticket.png' alt='TP-Link employee on the forums explaining how to downgrade the firmware'>
+<a href="https://community.tp-link.com/en/home/forum/topic/236268#topic-reply-523030">Forum post</a> by a TP-Link employee to send in a ticket.
+</p>
+
+We are hoping for a better solution, but for now this is what you should do:
+
+1. Submit a ticket to [technical support](https://www.tp-link.com/en/support/contact-technical-support/#E-mail-Support). Make sure to include the MAC address of your plug.
+2. Go to the forums and send [this user](https://community.tp-link.com/en/home/uc/info/650029) a message with your ticket ID and MAC address (just to be sure).
+
+TP-Link, if you're reading along, please reach out to us at hello@home-assistant.io so we can discuss a better long term solution for local control. Happy to talk!
diff --git a/source/images/blog/2020-11-23-tplink/forum-post-send-ticket.png b/source/images/blog/2020-11-23-tplink/forum-post-send-ticket.png
new file mode 100644
index 00000000000..0dd80cfb6be
Binary files /dev/null and b/source/images/blog/2020-11-23-tplink/forum-post-send-ticket.png differ