-
Notifications
You must be signed in to change notification settings - Fork 470
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
[Eve]: Support for Eve Energy Outlet #1195
[Eve]: Support for Eve Energy Outlet #1195
Conversation
Timac
commented
Jan 30, 2024
- Add Eve Energy Outlet fingerprint
- Only create the polls (create_poll_schedule and create_poll_report_schedule) if the device supports capabilities.powerConsumptionReport
- When the device is initialized, create child devices with the profile plug-binary for each additional outlet
- Update component_to_endpoint, endpoint_to_component and find_child to support multiple children
- Each time an oulet is turned on or off, store the value in a dictionary
- If one of the outlet is on, we should create the poll to monitor the power consumption
- If all the outlet are off, we should delete the poll
- Add Eve Energy Outlet fingerprint
- Add Eve Energy Outlet fingerprint - Only create the polls (create_poll_schedule and create_poll_report_schedule) if the device supports capabilities.powerConsumptionReport - When the device is initialized, create child devices with the profile plug-binary for each additional outlet - Update component_to_endpoint, endpoint_to_component and find_child to support multiple children - Add a check in on_off_attr_handler to make sure the polling functions are only called for the parent device/endpoint 1, which supports powerConsumption
- Each time an oulet is turned on or off, store the value in a dictionary - If one of the outlet is on, we should create the poll to monitor the power consumption - If all the outlet are off, we should delete the poll
Channel deleted. |
Test Results 55 files ±0 352 suites ±0 0s ⏱️ ±0s Results for commit 321aa8b. ± Comparison against base commit d57f980. This pull request removes 2 and adds 4 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 321aa8b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small change, but this looks good! The device should arrive for testing shortly and we can confirm everything is working as expected.
Thank you for your help @Timac !
Only run the device_init function for the parent device.
* Eve Energy Outlet - Add Eve Energy Outlet fingerprint * Eve Energy Outlet - Add Eve Energy Outlet fingerprint - Only create the polls (create_poll_schedule and create_poll_report_schedule) if the device supports capabilities.powerConsumptionReport - When the device is initialized, create child devices with the profile plug-binary for each additional outlet - Update component_to_endpoint, endpoint_to_component and find_child to support multiple children - Add a check in on_off_attr_handler to make sure the polling functions are only called for the parent device/endpoint 1, which supports powerConsumption * Eve Energy Outlet - Each time an oulet is turned on or off, store the value in a dictionary - If one of the outlet is on, we should create the poll to monitor the power consumption - If all the outlet are off, we should delete the poll * Remove unused log to fix luacheck * Don't change the profile, this breaks the unit tests * Eve Energy Outlet Only run the device_init function for the parent device.