homebridge-actron-neo

[bwp91]

Link To GitHub Repo

https://github.com/bstillitano/homebridge-actron-neo

Link To NPM Package

https://www.npmjs.com/package/homebridge-actron-neo

(on behalf of @bstillitano)

[github-actions[bot]]

:white_check_mark: Pre-checks completed successfully.

[bwp91]

Hi @bstillitano

One thing I would like to suggest is to add some keywords here so that Homebridge UI users can search for say "actron neo" and your plugin comes up!

Also I appreciate 0.0.X versions of plugins probably don't have changes (im referring to your release notes) but please remember that these release notes appear for users in the homebridge UI. The github release notes appear for a user before they update - hence the verification request that a user makes a github release for each version with notes.

So with this in mind please continue to create the github releases, and populate the notes with any important changes to the plugin 👍

But for me all good, happy to verify this plugin, I appreciate the time you spent to rename the plugin so it looks nice in the homebridge UI 👍

[github-actions[bot]]

• [x] - The plugin must successfully install.
• [x] - The plugin must implement the Homebridge Plugin Settings GUI.
• [x] - The plugin must not start unless it is configured.
• [x] - The plugin must be of type dynamic platform.
• [x] - The plugin must not offer the same nor less functionality than that of any existing verified plugin.
• [x] - The plugin must not execute post-install scripts that modify the user's system in any way.
• [x] - The plugin must not contain any analytics or calls that enable you to track the user.
• [x] - The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.
• [x] - The plugin must be published to npm and the source code available on GitHub.
• [x] - A GitHub release should be created for every new version of your plugin, with patch notes.
• [x] - The plugin must run on all Active LTS versions of Node.js, at the time of writing this is Node.js v18.
• [x] - The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
• [x] - If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.

---

Everything Looks Good!

[github-actions[bot]]

Congratulations! Your plugin has been verified.

You can now add the Verified by Homebridge badge to your plugin's README:

[![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

Your plugin is now also eligible to display a :heart: Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.

If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our unmaintained plugins repo. We can take ownership until another willing developer comes along.

Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!

Thank you for your contribution to the Homebridge Community. https://homebridge.io

[bstillitano]

Hey @bwp91 appreciate the feedback. I'll start to the better populate the release notes and will address the keywords. Thanks for approving this so quickly and for all the help getting it to an approvable state.

[bstillitano]

Just a follow up @bwp91 , as agreed, keywords and changelogs should be populating properly now for the plugin.

[David-Allen-Arteaga]

Details

import "./styles.css"; export default function App() { return (

Hello CodeSandbox

Start editing to see some magic happen!

); }

[David-Allen-Arteaga]

Details

https://support.google.com/paymentscenter/answer/9031403?p%3Dgoogle_marketplaces%26visit_id%3D636785063042510889-22186422%26rd%3D1&sa=D&ust=1603732545524000&usg=AOvVaw0aaytTN3XImTHdbxynfqLq