Announcement

Collapse
No announcement yet.

Warning No response/improper response from Elk M1 to command 'cv5900'

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Warning No response/improper response from Elk M1 to command 'cv5900'

    Using Ultrajones support template:
    ​​​​​​ 1. What Operating System Are You Using: Windows 10
    2. Are you running HomeSeer as a service? No
    3. How is HomeSeer connected to the Elk M1? M1XEP
    4. Do you run any anti-virus programs? Windows Security

    Noticed these errors in HS log while setting up other plugins. Anyone have an idea where to start?

    Jun-09 1:41:50 AM Warning No response/improper response from Elk M1 to command 'cv5900'
    Jun-09 1:41:49 AM Warning Raw data was: 0DCV700000006C
    Jun-09 1:41:49 AM Warning Invalid checksum 0 for command CV as data 700000

    Jun-09 12:25:46 AM Warning No response/improper response from Elk M1 to command 'cv3400'
    Jun-09 12:25:45 AM Warning Raw data was: 0DCV3000000070
    Jun-09 12:25:45 AM Warning Invalid checksum 0 for command CV as data 300000

    Jun-08 7:56:48 PM Warning No response/improper response from Elk M1 to command 'cv5600'
    Jun-08 7:56:47 PM Warning Raw data was: 0DCV600000006D
    Jun-08 7:56:47 PM Warning Invalid checksum 0 for command CV as data 600000


    Turned on debug logging, then noticed these errors in HS log

    Jun-09 9:45:55 AM Warning No response/improper response from Elk M1 to command 'cv4000'

    Jun-09 11:15:50 AM Warning No response/improper response from Elk M1 to command 'cv0700'

    Jun-09 12:25:57 PM Warning No response/improper response from Elk M1 to command 'cv3700'

    forwarded debug log to ultrajones email

    #2
    Seeing the same. Any response from UltraJones on this for resolution?

    1/1/2022 12:52:59 AM UltraM1G3 Warning Watchdog Timer reconnect attempt failed :Could not communicate with ELK M1 System!
    1/1/2022 12:52:59 AM UltraM1G3 Informational Could not communicate with Elk M1 ...
    1/1/2022 12:52:56 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:56 AM
    1/1/2022 12:52:53 AM UltraM1G3 Warning Invalid RegExp for data 5507112008
    1/1/2022 12:52:53 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:53 AM
    1/1/2022 12:52:50 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:50 AM
    1/1/2022 12:52:50 AM UltraM1G3 Informational Attemping initial communication with Elk M1 ...
    1/1/2022 12:52:16 AM UltraM1G3 Warning Watchdog Timer reconnect attempt failed :Could not communicate with ELK M1 System!
    1/1/2022 12:52:16 AM UltraM1G3 Informational Could not communicate with Elk M1 ...
    1/1/2022 12:52:13 AM UltraM1G3 Warning Raw data was: 0122010007C
    1/1/2022 12:52:13 AM UltraM1G3 Warning Invalid checksum 50 for command 22 as data 010
    1/1/2022 12:52:13 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:13 AM
    1/1/2022 12:52:10 AM UltraM1G3 Warning Invalid RegExp for data 20002000F
    1/1/2022 12:52:10 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:10 AM
    1/1/2022 12:52:07 AM UltraM1G3 Informational Updating ELK M1 internal real-time clock to 1/1/2022 12:52:07 AM
    1/1/2022 12:52:07 AM UltraM1G3 Informational Attemping initial communication with Elk M1 ...
    1/1/2022 12:51:42 AM UltraM1G3 Warning Raw data was: 10002010007D
    1/1/2022 12:51:42 AM UltraM1G3 Warning Invalid checksum 97 for command 00 as data 2010

    Comment


      #3
      No, not expecting an answer as he is no longer actively supporting his plug-ins.

      Comment


        #4
        Attached is the Elk M1 RS232 command set. Looks like your Elk is not responding correctly to a request for counter value data....Not an expert on either this plugin or Elk serial communication. I have the plugin which has been working perfectly in HS3 and HS4. Perhaps a fault in the Elk?
        Attached Files

        Comment


          #5
          Ended up being a bad cable. Oddly, it worked on another M1, but not on mine. I ordered the same cable (yes seemed insane), but the new one seems to work now. A bit frustrating they are that sensitive.

          Comment

          Working...
          X