Hi Rob, I'be been noticing the battery voltage device in the plugin on my OMNI Pro II drop from 13.68V to zero for awhile. I've double-checked with PC Dealer Access 3.0 and with a volt meter and the battery voltage is fine. Stopping and starting the Plugin would restore it back to 13.68V.
Today I've had time to tinker with it, so I added an event to HS3 to send me a PushOver message when the battery device changes to zero. About an hour later, I picked up the telephone to make a call and I immediately received the PushOver message that the Battery had gone to zero. I reset the plugin again and took the phone off hook....and voila I received another battery device message. So it would appear that something is amiss. PC Dealer Access says it's fine as does the volt meter, so I'm thinking something in the plugin?
As I was tracking this down, I reviewed the MySQL logs that the plugin is generating. In so doing, I discovered another anomaly. I am seeing CODE 1 DISARM events being logged for one of my Areas (named CARRIAGE) every time the phone goes on and off hook. And the eventMsg references the last time I disarmed that area. Please see attached PDF. This behavior goes all the way back to December 2017 when I changed the plugin from HAI to OMNI. I checked the prior logs when it was HAI and this behavior didn't exist. I am currently on OMNI v3.0.2.12
The OMNI Pro II is not showing any signs of having a problem and its interaction with HS3 is fine except for the Battery going to zero. Any thoughts?
Today I've had time to tinker with it, so I added an event to HS3 to send me a PushOver message when the battery device changes to zero. About an hour later, I picked up the telephone to make a call and I immediately received the PushOver message that the Battery had gone to zero. I reset the plugin again and took the phone off hook....and voila I received another battery device message. So it would appear that something is amiss. PC Dealer Access says it's fine as does the volt meter, so I'm thinking something in the plugin?
As I was tracking this down, I reviewed the MySQL logs that the plugin is generating. In so doing, I discovered another anomaly. I am seeing CODE 1 DISARM events being logged for one of my Areas (named CARRIAGE) every time the phone goes on and off hook. And the eventMsg references the last time I disarmed that area. Please see attached PDF. This behavior goes all the way back to December 2017 when I changed the plugin from HAI to OMNI. I checked the prior logs when it was HAI and this behavior didn't exist. I am currently on OMNI v3.0.2.12
The OMNI Pro II is not showing any signs of having a problem and its interaction with HS3 is fine except for the Battery going to zero. Any thoughts?
Comment