-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verification Request: homebridge-http-sensors-switches #755
Comments
🔴 The following checks failed:
🟢 The following checks passed:
If updating your |
/check |
🟢 The following checks passed:
🎉 All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team. |
Plugin Name
homebridge-http-sensors-switches
Link To GitHub Repo
https://github.com/kreso975/homebridge-http-sensors-switches
Plugin Icon (Optional)
No response
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟢 Yes
The plugin successfully installs and does not start unless it is configured.
🟢 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
🟢 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
🟢 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
🟢 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
🟢 Yes
More Information
Hi,
This is simple HTTP plugin covering Interaction with Switch and reading Sensor JSON data. Each accessory can be adjusted inside config (see Config example).
Main reason i have wrote this code is not to be dependent on non maintained plugins which were causing my homebridge to crash.
I'm using it on iot devices built by my self.
There are similar plugins out there but none of them are verified. I'm new to this kind of process, I hope i did it OK :)
Best regards,
Kreso
The text was updated successfully, but these errors were encountered: