I have a problem with reliability of my X10 system for some reason. I'm not sure where it's coming from, but I'm having mystery dimming, missed commands, incorrect commands, etc. I'm also having issues with my code breaking for no apparent reason, but at least that's something I can figure out.
I'm working on determining what's causing my issues, but for one temporary fix, I'm looking to add a heartbeat of sorts that will send a single command on a house code that I'm not utilizing. This will keep a missed address command from causing commands from being applied to the wrong module.
The problem is, I'm not able to get the heartbeat to work. The setup is simple. I've created an X10 module "H1" and a scheduler event that should fire every 10 minutes called "heartbeat" (*/10 * * * *). I have set the "Scheduled On/Off" to Off "@heartbeat". But, it fired the first time and that was it. I figure the issue is that HG won't send an off command if it thinks the module is on, so I turned the module on and waited 10 minutes. Yup, with it turned on, it turns off.
Why am I not allowed to send an off command if it's already off? I reviewed the C# script and I see that it's set up that way. Why? What is the down side of allowing an on or off command from being sent if the module is already in that state. Among other things, this allows the system to be re-synced at a scheduled time. I'm going to modify my code, but I don't understand why it's set that way.
