Version
Which HomeGenie version/OS/.NET framework version are you using. (REQUIRED)
HomeGenie 1.3-stable.19
Describe the bug
A clear and concise description of what the bug is.
When a module has been deleted from all groups so it is basically not part of an automation setup, the code associated with the module still runs in the background. There is no way to disable this without adding the module back in, changing the settings, then deleting OR deleting the module via Modules Cleanup function.
Code to Reproduce
Write a small snippet to isolate your bug and could be possible to our team test. (REQUIRED)
None required. Set up a module with a some kind of automation (scheduled ON/OFF for example), then delete the module from all groups. There is no way to see what the module is set up to do and yet it will continue to run automation code in the background.
Expected behavior
A clear and concise description of what you expected to happen.
When a module is deleted from all groups, I would expect that no automations should process. Modules that are not part of any group are not part of a HG setup so they should not run in the background. If they can run in the background and this is a desired feature, I would request a way to setup the module without having to go through extra steps to add it, modify settings, then delete it.
Screenshots/Stacktrace
If applicable, add screenshots/stacktrace
Additional context
Add any other context about the problem here.
I experienced a situation over the last few days where I was getting a flood of X10 A8 OFF commands. These all seemed to be triggered at 10s intervals. Disconnecting the CM15A stopped the flood as did restarting the RPi or HG. It took a lot of time to determine why this was happening because I deleted that module years ago and no code should have been associated with the module at all.
Version Which HomeGenie version/OS/.NET framework version are you using. (REQUIRED) HomeGenie 1.3-stable.19
Describe the bug A clear and concise description of what the bug is. When a module has been deleted from all groups so it is basically not part of an automation setup, the code associated with the module still runs in the background. There is no way to disable this without adding the module back in, changing the settings, then deleting OR deleting the module via Modules Cleanup function.
Code to Reproduce Write a small snippet to isolate your bug and could be possible to our team test. (REQUIRED) None required. Set up a module with a some kind of automation (scheduled ON/OFF for example), then delete the module from all groups. There is no way to see what the module is set up to do and yet it will continue to run automation code in the background.
Expected behavior A clear and concise description of what you expected to happen. When a module is deleted from all groups, I would expect that no automations should process. Modules that are not part of any group are not part of a HG setup so they should not run in the background. If they can run in the background and this is a desired feature, I would request a way to setup the module without having to go through extra steps to add it, modify settings, then delete it.
Screenshots/Stacktrace If applicable, add screenshots/stacktrace
Additional context Add any other context about the problem here. I experienced a situation over the last few days where I was getting a flood of X10 A8 OFF commands. These all seemed to be triggered at 10s intervals. Disconnecting the CM15A stopped the flood as did restarting the RPi or HG. It took a lot of time to determine why this was happening because I deleted that module years ago and no code should have been associated with the module at all.