I have a Raspberry Pi 3 running HS3. It's connected to a CM15A and X10 to a couple of lights I want to control via Alexa.
Current Date/Time: 5/14/2020 2:48:47 PM
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.548
Linux version: Linux momrpiw 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux System Uptime: 0 Days 3 Hours 44 Minutes 31 Seconds
IP Address: 192.168.11.83
Number of Devices: 2
Number of Events: 1
Available Threads: 399
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Enabled Plug-Ins
3.0.0.5: CM15A
I've been able to control the lights manually via the HS3 webpage for a long time now. After several months Alexa has finally recognized the two devices via the Homeseer SmartHome skill. I don't know why Alexa recognized the devices, it just happened recently all by itself. However the Alexa voice command use is erratic. Sometimes it will turn the lights on and off, and sometimes not. Alexa always seems to think the command executed OK whether or not it actually did. However, logging on mochad indicates that the command never made it to mochad when the Alexa command fails. HS3 logging has entries like
that appear whenever I issue a command via Alexa or manually through the webpage. This is true with Alexa whether or not the light actually does something.
The syslog shows entries like
mono[475]: 02:36:54:4383:[Device Control]->Device: Upstairs Hall Upstairs to On (100) by/from: CAPI Control Handler
whenever Alexa works or I toggle the light through the webpage, but not when Alexa fails.
To summarlize, somehow Alexa and CAPI Control Handler always respond even when the Alexa command doesn't work. But when it fails mono and mochad don't get anything. There's a disconnect somewhere even though Alexa seems to be getting a command succeeded response back from HS3.
Any ideas on what is going on or what I could try will be appreciated.
Current Date/Time: 5/14/2020 2:48:47 PM
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.548
Linux version: Linux momrpiw 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux System Uptime: 0 Days 3 Hours 44 Minutes 31 Seconds
IP Address: 192.168.11.83
Number of Devices: 2
Number of Events: 1
Available Threads: 399
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Enabled Plug-Ins
3.0.0.5: CM15A
I've been able to control the lights manually via the HS3 webpage for a long time now. After several months Alexa has finally recognized the two devices via the Homeseer SmartHome skill. I don't know why Alexa recognized the devices, it just happened recently all by itself. However the Alexa voice command use is erratic. Sometimes it will turn the lights on and off, and sometimes not. Alexa always seems to think the command executed OK whether or not it actually did. However, logging on mochad indicates that the command never made it to mochad when the Alexa command fails. HS3 logging has entries like
Device Control | Device: Upstairs Hall Upstairs to On (100) by/from: CAPI Control Handler |
The syslog shows entries like
mono[475]: 02:36:54:4383:[Device Control]->Device: Upstairs Hall Upstairs to On (100) by/from: CAPI Control Handler
whenever Alexa works or I toggle the light through the webpage, but not when Alexa fails.
To summarlize, somehow Alexa and CAPI Control Handler always respond even when the Alexa command doesn't work. But when it fails mono and mochad don't get anything. There's a disconnect somewhere even though Alexa seems to be getting a command succeeded response back from HS3.
Any ideas on what is going on or what I could try will be appreciated.
Comment