Announcement

Collapse
No announcement yet.

Error Message - Appears to trigger event

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Error Message - Appears to trigger event

    12/23/2004 10:41:34 PM~!~HAI System~!~Checksum calc error: 39EC and message has C4 for message type 23
    12/23/2004 10:41:45 PM~!~Event Trigger~!~Value change trigger (Alarm House Status - OFF):Security Status from: 4 to: 0
    12/23/2004 10:41:46 PM~!~Info~!~Sending email To:

    12/26/2004 12:17:43 AM~!~HAI System~!~Checksum calc error: 42BD and message has 2D6 for message type 23
    12/26/2004 12:18:21 AM~!~Event Trigger~!~Value change trigger (Alarm House Status - OFF):Security Status from: 4 to: 0
    12/26/2004 12:18:21 AM~!~Value change trigger (Alarm House Status - OFF):Security Status from: 4 to: 0~!~ Send email to:


    This last one went off ater midnight last night and it is an event triggered by an HAI system value change. (its happened 2-3 times this past week - but it has occurred during the day).
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    #2
    pcalleros,

    Turn on HAI Debugging:
    hs.plugin("HAI_System").Set_Log_Debug(1)
    hs.plugin("HAI_System").Set_Debug_Level(3)

    (To turn off again: hs.plugin("HAI_System").Set_Log_Debug(0)
    or use the web interface to enable/disable)

    This will create a file called HAIPlugin.log.

    Match up where you're getting checksum errors to the times in the log and posts parts of the Hai log.

    I want to see the panel comms during this time to try and see why you are getting the checksum errors to start with.

    Ross.

    Comment


      #3
      Debugging Info I

      Here is a detail related to one error early this morning.

      On HS Log

      12/28/2004 1:25:26 AM~!~HAI System~!~Checksum calc error: 8A41 and message has 4940 for message type 27

      On DEBUG Log

      12/28/2004 1:25:25 AM:005125.98 ~Entered HAI_Request_System_Status
      12/28/2004 1:25:26 AM:005126.00 ~Entered Send_Command to send type SYSTEM STATUS, length of 3
      12/28/2004 1:25:26 AM:005126.00 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.00 ~Sending to panel: 5A-1-13
      12/28/2004 1:25:26 AM:005126.03 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.03 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.03 ~Exiting HAI_Request_System_Status
      12/28/2004 1:25:26 AM:005126.05 ~Polling item 1 which is type z and unit 1
      12/28/2004 1:25:26 AM:005126.05 ~Entered HAI_Check_Special_Alarms
      12/28/2004 1:25:26 AM:005126.06 ~Entered HAI_Polling_Timer to set to False currently it is True
      12/28/2004 1:25:26 AM:005126.06 ~Exiting HAI_Polling_Timer
      12/28/2004 1:25:26 AM:005126.06 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.08 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.08 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.09 ~Sending to panel: 5A-3-15-B1-B1
      12/28/2004 1:25:26 AM:005126.11 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.13 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.13 ~Entered Receive_Specific looking for: ZONE STATUS the stack is 1
      12/28/2004 1:25:26 AM:005126.13 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.17 ~Receive_From_Panel just got: THERMOSTAT STATUS
      12/28/2004 1:25:26 AM:005126.17 ~Received from panel: 5A-8-1F-0-78-71-81-1-0-0-29-3
      12/28/2004 1:25:26 AM:005126.17 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.19 ~Entered HAI_Eval_Thermostat_Status
      12/28/2004 1:25:26 AM:005126.19 ~Exiting HAI_Eval_Thermostat_Status
      12/28/2004 1:25:26 AM:005126.20 ~Entered Receive_From_Panel

      12/28/2004 1:25:26 AM:005126.23 ~Received from panel with CHECKSUM ERROR: 5A-1-27-40-49

      12/28/2004 1:25:26 AM:005126.23 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.25 ~HAI_STAT_SecValidate message received. Should not be handled here.
      12/28/2004 1:25:26 AM:005126.25 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.28 ~Receive_From_Panel just got: SYSTEM STATUS
      12/28/2004 1:25:26 AM:005126.28 ~Received from panel: 5A-27-14-1-4-C-1C-2-1-18-34-0-6-2E-F-30-EB-0-0-0-0-0-0-0-0-80-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-AF-2F
      12/28/2004 1:25:26 AM:005126.28 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.30 ~Entered HAI_Eval_Armed_Status
      12/28/2004 1:25:26 AM:005126.30 ~Exiting HAI_Eval_Armed_Status
      12/28/2004 1:25:26 AM:005126.31 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.34 ~Receive_From_Panel just got: ZONE STATUS
      12/28/2004 1:25:26 AM:005126.34 ~Received from panel: 5A-3-16-10-0-EC-40
      12/28/2004 1:25:26 AM:005126.34 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.36 ~Receive_Specific: Looking for ZONE STATUS and this is loop 4
      12/28/2004 1:25:26 AM:005126.36 ~Exiting Receive_Specific with: ZONE STATUS the stack is 0
      12/28/2004 1:25:26 AM:005126.38 ~Executing HAI_Process_Zone_Status for Zone 177
      12/28/2004 1:25:26 AM:005126.38 ~Exiting HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.38 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.39 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.39 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.41 ~Sending to panel: 5A-3-15-B2-B2
      12/28/2004 1:25:26 AM:005126.42 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.44 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.44 ~Entered Receive_Specific looking for: ZONE STATUS the stack is 1
      12/28/2004 1:25:26 AM:005126.45 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.48 ~Receive_From_Panel just got: ZONE STATUS
      12/28/2004 1:25:26 AM:005126.48 ~Received from panel: 5A-3-16-10-0-EC-40
      12/28/2004 1:25:26 AM:005126.48 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.50 ~Exiting Receive_Specific with: ZONE STATUS the stack is 0
      12/28/2004 1:25:26 AM:005126.50 ~Executing HAI_Process_Zone_Status for Zone 178
      12/28/2004 1:25:26 AM:005126.52 ~Exiting HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.52 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.52 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.53 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.53 ~Sending to panel: 5A-3-15-BA-BA
      12/28/2004 1:25:26 AM:005126.56 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.56 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.58 ~Entered Receive_Specific looking for: ZONE STATUS the stack is 1
      12/28/2004 1:25:26 AM:005126.58 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.61 ~Receive_From_Panel just got: ZONE STATUS
      12/28/2004 1:25:26 AM:005126.61 ~Received from panel: 5A-3-16-10-0-EC-40
      12/28/2004 1:25:26 AM:005126.61 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.63 ~Exiting Receive_Specific with: ZONE STATUS the stack is 0
      12/28/2004 1:25:26 AM:005126.63 ~Executing HAI_Process_Zone_Status for Zone 186
      12/28/2004 1:25:26 AM:005126.64 ~Exiting HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.64 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.64 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.66 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.66 ~Sending to panel: 5A-3-15-C2-C2
      12/28/2004 1:25:26 AM:005126.69 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.69 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.70 ~Entered Receive_Specific looking for: ZONE STATUS the stack is 1
      12/28/2004 1:25:26 AM:005126.70 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.77 ~Receive_From_Panel just got: ZONE STATUS
      12/28/2004 1:25:26 AM:005126.77 ~Received from panel: 5A-3-16-10-0-EC-40
      12/28/2004 1:25:26 AM:005126.77 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.78 ~Exiting Receive_Specific with: ZONE STATUS the stack is 0
      12/28/2004 1:25:26 AM:005126.78 ~Executing HAI_Process_Zone_Status for Zone 194
      12/28/2004 1:25:26 AM:005126.80 ~Exiting HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.80 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.80 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.81 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.81 ~Sending to panel: 5A-3-15-CA-CA
      12/28/2004 1:25:26 AM:005126.84 ~Exiting Send_To_Panel
      12/28/2004 1:25:26 AM:005126.86 ~Exiting Send_Command
      12/28/2004 1:25:26 AM:005126.86 ~Entered Receive_Specific looking for: ZONE STATUS the stack is 1
      12/28/2004 1:25:26 AM:005126.86 ~Entered Receive_From_Panel
      12/28/2004 1:25:26 AM:005126.91 ~Receive_From_Panel just got: ZONE STATUS
      12/28/2004 1:25:26 AM:005126.91 ~Received from panel: 5A-3-16-10-0-EC-40
      12/28/2004 1:25:26 AM:005126.91 ~Exiting Receive_From_Panel (4)
      12/28/2004 1:25:26 AM:005126.92 ~Exiting Receive_Specific with: ZONE STATUS the stack is 0
      12/28/2004 1:25:26 AM:005126.92 ~Executing HAI_Process_Zone_Status for Zone 202
      12/28/2004 1:25:26 AM:005126.94 ~Exiting HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.94 ~Entered HAI_Get_Zone_Status
      12/28/2004 1:25:26 AM:005126.94 ~Entered Send_Command to send type ZONE STATUS, length of 5
      12/28/2004 1:25:26 AM:005126.95 ~Entered Send_To_Panel
      12/28/2004 1:25:26 AM:005126.95 ~Sending to panel: 5A-3-15-D2-D2
      Last edited by Pete; December 28, 2004, 02:51 PM. Reason: Update
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
      HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

      HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
      HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

      Comment


        #4
        Ok. I have no idea what the plugin is doing here.

        Reason I says this is:
        12/28/2004 1:25:26 AM:005126.00 ~Sending to panel: 5A-1-13 <- Give me system status
        This should return a message: 5a-24-14-xxxxxx But it doesn't send any answer this to request.

        12/28/2004 1:25:26 AM:005126.05 ~Polling item 1 which is type z and unit 1
        Type Z huh? Unit 1? Things have already gone wrong here.

        Now without waiting for the system status response, it's sending:
        12/28/2004 1:25:26 AM:005126.09 ~Sending to panel: 5A-3-15-B1-B1 <- Give me zone status of zone 177 (You have 17 zones!!)

        We then get back :
        5A-8-1F-0-78-71-81-1-0-0-29-3 <- This is a response to a request thermostat status request ( Which is 5a-03-1E-xx-xx command), which is a response to a command we haven't seen in this trace!

        Now we get your error message:
        12/28/2004 1:25:26 AM:005126.23 ~Received from panel with CHECKSUM ERROR: 5A-1-27-40-49

        This is a response to the system status request at the very start of this log.

        It seems the plugin isn't waiting long enough for the response to the requests system status call. Or maybe it's getting ahead of itself as we should have seen the thermostat status request but we don't, we only see the answer.

        The problem I think is this: 12/28/2004 1:25:26 AM:005126.05 ~Polling item 1 which is type z and unit 1. This shows up before the Omni can respond to the system status request.

        There is this strange type z unit 1 "thing" that's showing up out of nowhere and not letting the plugin continue with it's message passing: send-wait-receieve. etc.

        Rick.. This make any sense? It seems the plugins getting ahead of itself.

        Ross.

        Edit: 12/28/2004 1:25:26 AM:005126.92 ~Executing HAI_Process_Zone_Status for Zone 202
        Not even an OmniProII can have 202 zones. Rick, something seriously wrong going on here!
        Last edited by rirvine; December 29, 2004, 03:17 AM. Reason: Update

        Comment


          #5
          I just upgraded to the latest HAI beta and seem to have started getting these errors as well:

          1/2/2005 9:36:03 AM~!~HAI System~!~Checksum calc error: 262C and message has 202A for message type 1F

          1/2/2005 9:44:53 AM~!~HAI System~!~Checksum calc error: 474D and message has FD9 for message type 18
          The time stamp on these doesn't seem to be occuring when anything else is occuring, and these only started showing up when I upgraded to the newest beta. The "checksum error," "message," and "message type" all appear random. Message type is sometimes 18, or 16, but I've also seen 23 and 1B.

          I should note that I also have an event triggered by a HAI status change, but it doesn't seem to trigger incorrectly. (I'm adding in more logging.) I have checking in place, so multiple triggers of this event don't cause problems.

          Comment


            #6
            Obiviously I'm guessing here, but I don't think there is actually a checksum error. I think the problem is that the plug-in is getting out of sync sending commands to the panel. It's sending commands but getting response to previous requests causing it to get confused. It also seems to loose the plot as to how many zones you have (given pcalleros' log file).
            I'm still using 1.1.0.30 which seems to work ok and I'm definitely staying here until the new plug-in's fixed.

            Ross.

            Comment


              #7
              rirvine

              That would seem to make sense from what I'm seeing. These errors for me seem to occur maybe several times per day, but generally it looks like most interactions are working. I also notice that I'm getting an occasional thermostat error. My script sets each thermostat to a value, then reads the settings back to verify. If they don't match, thats an error. I need to do a bit more research here to see if this is a script problem or plugin problem.

              One other problem that I am having with the plugin is the unit names and their access. I imported my names from the panel, but when I use web access and display "units," the first 48 displayed are actually zones, and the web page gives me the option to set each "zone" to a level or turn it on or off? The zones also appear correctly under the security page. What's this all about?

              Comment


                #8
                most of my unit names and zones are now out of whack also.

                especially temp sensors.

                example:
                i have temp sensors on zones 9 and 10
                the windows interface shows them on zones 9 and 10, 15 and 16, 18 and 19, and then every pair of zones from 21/22 to 31/32.
                no biggy except that about once every 3 days it decides to update the temps on zones 9/10 BUT seems to keep the temps current on zones 15/16.

                ... but i thought my thermostat was connected to zone 16 ???

                Comment


                  #9
                  This is a little hard to explain although I have tried a few times. The end result is that the HAI system is a polling protocol (must be asked for everything) AND it cannot handle a request for a lot of data at once.

                  OK, so first of all, when a zone changes state, a messages goes into the event log and the plug-in polls that for information very rapidly - every 1/2 second - so that as much information as I can get from the event log as possible can be reacted to very quickly - near realtime if I could, but with a polling protocol that is impossible.

                  Some aspects of the zone status, much of the X-10 unit changes (e.g. dim/bright) and NOTHING having to do with thermostats comes through the event log - it must be polled separately. Also, even if I get messages on zones from the event log, the full status of a zone has to be polled every once in a while just to make sure things do not go out of whack (HAI's recommendation). Thus, there is a secondary polling that not only picks up the status of things that do not hit the event log, but it gets the status of literally everything in the system.

                  With all of this polling, the little PIC chip in the panel has a LOT of work to do, and there are two things that further complicate this... 1. I cannot say "give me the status of zone 1" and get back a message that says "zone 1's status is..." - all I get back is "zone status is" without anything confirming that it is for the zone that I asked for. So now I cannot send out the requests and respond to the replies in a near realtime or interrupt driven manner - I have to send out the request and WAIT for that specific type of response, and I have to continue to do this so that I do not lose synchronization with the panel (e.g. it sends the response for zone 5 when I just asked for 7). The OTHER more serious complication is that while they give me the ability to ask for the status of say 20 zones at once, it will return a message with a bad checksum if the panel got busy and could not take the time to put the whole message response together. Yes, I have seen this happen a great deal!

                  So, to try to take care of the fact that I have to ask for everything in the system as fast as possible and the fact that asking for too much gets me into trouble as well.... Hopefully you get the idea.

                  My recent implementation of it A) asking for several zones/units status at once and B) using an interrupt driven processing system for the messages that I do not have an identity crisis with has gotten me the best performance for the buck thus far. What I have to do now (after CES) is come up with a way for you to adjust how many zones or units are retrieved at once during the updates. Asking for more at a time gets you better overall system performance and speed for the plug-in to react to things, but asking for too much gets you a lot of checksum errors. (A checksum error would NOT result if the wrong message type was received than what was expected either.)

                  After hearing a bit about how the panel processes things, I can tell you that the more programming you have in the panel itself, the longer and worse performing the HomeSeer plug-in will be with it as program lines get tested in each "loop" of the system, and that eats into the precious few CPU cycles the system has.
                  Regards,

                  Rick Tinker (a.k.a. "Tink")

                  Comment


                    #10
                    I just did some checking. If I "Download Names" from the panel, they download correctly to that dialog box, in that units are units, zones are zones, etc. Its the save part that doesn't work. The names aren't saved correctly into the HAI ini file. In fact, I got different results each time I saved. In the ini files, many times the zones got labeled as units and buttons were usually units as well. This may be the reason that my HAI_Set_Temp started failing, because the thermostat is not at the correct "zone."

                    One great thing I learned, is that you can use the XP "System Restore" to go back to a previous plugin (pre-beta), and that is what I did until this plugin can get fixed.

                    Comment


                      #11
                      The names aren't saved correctly into the HAI ini file.
                      anogee,

                      This is a known problem. See this thread: http://forums.homeseer.com/showthread.php?t=91532

                      Since people encounter the problem infrequently (how often do you download names from the panel), I know it's low on the priority list for Rick.

                      Rick,

                      You probably should put a mention of this bug into the beta release notes. You know, the note that threatens eternal damnation if you don't read it.
                      My system is described in my profile.

                      Comment


                        #12
                        Hey Rick,

                        I think we understand the limits of a polling protocol. But the plugin is totally loosing the plot at some stage. Eg from pcalleros' previous example :

                        12/28/2004 1:25:26 AM:005126.09 ~Sending to panel: 5A-3-15-B1-B1 <- Give me zone status of zone 177 (You have 17 zones!!)
                        and
                        2/28/2004 1:25:26 AM:005126.95 ~Sending to panel: 5A-3-15-D2-D2
                        (Which is give me zone status 210 which is impossible as no model omni can have 210 zones).

                        I don't think it's as bad as it looks in a way. I think things are going down hill as the plugin is loosing it's mind as to the config of your panel. The checksum errors I think are just a side effect of this. The plugin should never be querying for zones that you don't have.

                        Regards,

                        Ross.

                        Comment


                          #13
                          I don't claim to be an expert on the internal workings of the panel, but why does the new "beta" software need to poll differently than the previous stable plug-in? (ver. 1.0) Is the new beta designed to reduce some of the latency complaints of the older plugin?

                          I have tried the ver. 1.1 plug-in on several occasions, and I always get some communication and/or sumcheck problems, which range from minor to bad. I then go back to the latest ver. 1.0 plugin, and that one always seems very stable and works great. I know the beta has some nice new features, but if the basic panel commincations doesn't work, VERY RELIABLY, then its not worth it for me.

                          Also, I only have about 75 lines of code on the panel, and I'd probably take more off and put it on HomeSeer if I knew it would be reliable.

                          Comment


                            #14
                            HS and CPU

                            Moving HS to a 3.2Ghz MT Intel box shortly.

                            I do not believe this will affect frequency and volume of errors that I am seeing.

                            Earlier in another thread a mention was made regarding the use of the same protocal for the ethernet interface. I understand that it is the same protcol. Has the speed of the conversation changed at all between the serial connection and the ethernet connection?
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                            Comment


                              #15
                              Anogee,

                              Give 1.1.0.30 a try. That's what I'm running and I haven't had 1 problem with it. Seems to have gone down hill from there..

                              I honestly don't think the major problem is with panel comms or checksum errors. It's clear from some of the logs here that the plugin has lost any idea as to how many zones etc a panel has. Regardless of the panel comms, the plugin shouldn't suddenly think a panel has 200 zones when it has 17. The only way I could see this happen is if the plugin tries to re-read the panel config (maybe due to a comms timeout error?) and when re-reading get's it all wrong, but then again you manually set the number of zones in the INI (or maybe that's just used when reading zone names???)

                              However, I can speculate all I like about this, but I didn't write it.

                              Ross.

                              Comment

                              Working...
                              X