anthon710 Posted March 8 Posted March 8 I'm receiving the following error and I cannot figure out where the issue is: 2024-03-08 17:41:26,623 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message SD!!! 2024-03-08 17:41:33,372 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message SD!!! 2024-03-08 17:41:38,382 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message KA!!! 2024-03-08 17:41:47,157 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message SD!!! 2024-03-08 17:41:52,175 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message KF!!! 2024-03-08 17:41:57,185 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message CS!!! 2024-03-08 17:42:02,190 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message SD!!! 2024-03-08 17:42:11,125 ELK-10623 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message SD!!! Any help would be much appreciated!
Jimbo.Automates Posted March 8 Posted March 8 Sorry I am traveling with spotty Internet, I'll try to look those up when I can.Sent from my Pixel 8 Pro using Tapatalk 1
anthon710 Posted March 19 Author Posted March 19 Just bumping this up. ThanksSent from my iPhone using Tapatalk
Jimbo.Automates Posted March 19 Posted March 19 I'll be back home early tomorrow morning so will try to look soon.Sent from my Pixel 8 Pro using Tapatalk 1
anthon710 Posted March 30 Author Posted March 30 Hey Jimbo, any chance you could take a look at this today? I really can’t seem to figure out what the problem is. Sent from my iPhone using Tapatalk
Jimbo.Automates Posted March 31 Posted March 31 I'm not sure why you are seeing SD's, the manual says: These commands allow programming and reading Insteon device addresses via the M1XSP Serial Port Expander configured in the Insteon mode So the SD is a response back from the M1EXP with an insteon device description. Must not be supported by the Python API I use. The KA is M1EXP response saying which areas all the keypads are assigned to. No need to worry about this one. The KF is M1EXP response reporting a function key was presses, not sure why you would see a timeout. The CS is M1EXP response reporting the control output status. I'm not seeing any of these timeouts in either of my ELK plugin logs. I'll have to dig into the Python API to see if I can figure out why it's complaining.
anthon710 Posted March 31 Author Posted March 31 Thank you. Yeah I’ve been baffled by it. I will take a look at my elk system again and see if there’s anything odd that I spot there. Sent from my iPhone using Tapatalk
anthon710 Posted May 22 Author Posted May 22 Thank you Jimbo.Automates for all your help! I discovered the problem so I wanted to post it in case anyone else has the same issue. It seems that if you have more than one device trying to talk to the Elk M1EXP, then it will throw that error. The M1EXP is only able to talk to one device at a time.
Recommended Posts