Announcement

Collapse
No announcement yet.

Plugin no longer polling TCP master

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • warren@wcnjsmith.com
    replied
    Greetings,

    Any thoughts on how I can get this plugin working again. Really need some assistance.

    Thank you

    Leave a comment:

  • warren@wcnjsmith.com
    replied
    In an attempt to capture the communications between HS4 and the plugin, I ran a wireshark capture. Here is what is going on on that port. No polling or activity seems to be going on even though polling set to 2 seconds. I am seeing keepalives between the HS4 server and my modbus master device - so its up and running. Confirmed with a poll by Chipkin Modbus analyser

    I had been running version 1.0.0.3 and it was working. Upgraded to 2.0.0.2 when I received a full license - I think that is when it stopped working however not totally sure as I did not check it fully until last week.
    ---------------------------

    From the log:
    Plugin modbusSeer with instance modbusSeer has connected. IP:127.0.0.1:58971

    ------------------------
    Wireshark on 127.0.0.1 port 58971 ( ACK and TCP control messages removed, only the packets with data )

    EàQð@( æ[³@kUZDPtÿÿÿÿ ;HSCF, Version=1.0.0.2, Culture=neutral, PublicKeyToken=nullLHSCF.Communication.ScsServices.Communica tion.Messages.ScsRemoteInvokeMessage!<ServiceClassName>k__Ba ckingField<MethodName>k__BackingField<Parameters>k__BackingF ield%ScsMessage+<MessageId>k__BackingField,ScsMessage+<Repli edMessageId>k__BackingFieldIPlugin
    OnStatusCheck $e9b75ecc-0752-435e-b554-af750d8e8f19


    E"-é@æ[( UÀa³Pù°ÿÿÿÿ ;HSCF, Version=1.0.0.2, Culture=neutral, PublicKeyToken=nullRHSCF.Communication.ScsServices.Communica tion.Messages.ScsRemoteInvokeReturnMessage<ReturnValue>k__Ba ckingField <RemoteException>k__BackingField%ScsMessage+<MessageId>k__ Ba ckingField,ScsMessage+<RepliedMessageId>k__BackingFieldHHSCF .Communication.ScsServices.Communication.Messages.ScsRemoteE xception
    modbusSeer
    $9588f079-106b-432d-a381-d1a09f93fa7c$4257bf9c-ab89-4cb4-b604-c52dff8c22b4

    Eà-ï@( æ[³UÂ[P{ÿÿÿÿ ;HSCF, Version=1.0.0.2, Culture=neutral, PublicKeyToken=nullLHSCF.Communication.ScsServices.Communica tion.Messages.ScsRemoteInvokeMessage!<ServiceClassName>k__Ba ckingField<MethodName>k__BackingField<Parameters>k__BackingF ield%ScsMessage+<MessageId>k__BackingField,ScsMessage+<Repli edMessageId>k__BackingFieldIPlugin
    OnStatusCheck $e900cfe8-911d-46d0-9b15-e8731e4a8dab


    EA-õ@æ[( UÂa³GPÿ>ÿÿÿÿ ;HSCF, Version=1.0.0.2, Culture=neutral, PublicKeyToken=null @PluginSdk, Version=1.4.1.0, Culture=neutral, PublicKeyToken=nullRHSCF.Communication.ScsServices.Communica tion.Messages.ScsRemoteInvokeReturnMessage<ReturnValue>k__Ba ckingField <RemoteException>k__BackingField%ScsMessage+<MessageId>k__ Ba ckingField,ScsMessage+<RepliedMessageId>k__BackingFieldHHSCF .Communication.ScsServices.Communication.Messages.ScsRemoteE xception
    $bdb3a66e-23a3-4868-8aec-aba84f76ee9b$e900cfe8-911d-46d0-9b15-e8731e4a8dabHomeSeer.PluginSdk.PluginStatus<Status>k__Backin gField<StatusText>k__BackingField-HomeSeer.PluginSdk.PluginStatus+EPluginStatusùÿÿÿ-HomeSeer.PluginSdk.PluginStatus+EPluginStatusvalue__

    EìY÷@( æ[³¦vUÜrPi:ÿÿÿÿ ;HSCF, Version=1.0.0.2, Culture=neutral, PublicKeyToken=nullLHSCF.Communication.ScsServices.Communica tion.Messages.ScsRemoteInvokeMessage!<ServiceClassName>k__Ba ckingField<MethodName>k__BackingField<Parameters>k__BackingF ield%ScsMessage+<MessageId>k__BackingField,ScsMessage+<Repli edMessageId>k__BackingFieldIPluginget_SupportsConfigFeature $3ed1abb7-4674-4403-a317-e9677acbbc9c

    Leave a comment:

  • warren@wcnjsmith.com
    replied
    Has the plugin been tested with Pro - 4.2.12.8

    I think the polling may have stopped when i applied the HS update. Any recommendations on how to get this running again.

    Many thanks
    Warren


    BLTED 1.0.17.0,HS MyQ 4.0.9.0,LG ThinQ 4.0.22.1,mcsMQTT 5.24.3.5,MNS Insteon 4.0.3.10,modbusSeer 2.0.0.2,ScreenLogic 0.4.4.0,Yamaha 3.3.6389.22764,Zigbee 4.0.11.0,Z-Wave 3.0.11.0,Z-Wave Parameters 4.0.46.0,Z-Wave UI 1.0.0.0

    Leave a comment:

  • warren@wcnjsmith.com
    replied
    should the "master" device show a value of "1" It is at 0


    D 387
    Device Version 4
    Value 0
    Status
    Interface modbusSeer
    Device Type Api Feature
    Priority Order 1
    Relationship Feature (Child)
    Associated Devices
    modbusSeer modbusSeer Master device: Kohler Generator master (386)

    Leave a comment:

  • warren@wcnjsmith.com
    replied
    restarted tcp modbus master and I can poll it with other Modbus tools and applications such as Chipkin and OAS.

    The polling seemed to stop about the time i fully licensed the plug-in. Its showing fully licensed.

    Any additional logging that perhaps can be turned on other than log debug that really shows very little.

    Leave a comment:

  • salvesen
    replied
    Originally posted by warren@wcnjsmith.com View Post
    Still having the issue - I have reinstalled the plugin, deleted and reinstalled devices and master. No change. Only messages between server running the plugin and the TCP master are TCP keepalive messages. Any help is greatly appreciated.
    Have you tried to restart your modbus adapter? Mine keeps stopping sometimes and then I just restart it.

    Leave a comment:

  • warren@wcnjsmith.com
    replied
    Still having the issue - I have reinstalled the plugin, deleted and reinstalled devices and master. No change. Only messages between server running the plugin and the TCP master are TCP keepalive messages. Any help is greatly appreciated.

    Leave a comment:

  • warren@wcnjsmith.com
    started a topic Plugin no longer polling TCP master

    Plugin no longer polling TCP master

    Set up initially and all was working - 15 discrete input devices on a Modbus TCP master. After a few days however Plugin stopped polling - no longer sending or receiving modbus messages.

    Polltime in the .config file - 5 seconds

    <add key="pollTime" value="5000" />
    </appSettings>

    Confirmed this looking at a wireshark trace - only activity at all from the HS4 server to the modbus master are TCP keepalives - which are no showing any errors

    Set up Chipkin Modbus diagnostics on the same server and its communicating and reading the discrete inputs OK from the tcp master, so its up and healthy. Looks like the Plugin is not communicating to the remote device with any modbus messages

    Nothing in the log seems to be odd either. IS there a way to turn on additional logging - its in debug now, however that does not show the TCP modbus messages


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Current slaveObjects list consist of: device name: Alarm 0001, device name: Device 10009, device name: Device 10010, device name: Device 10008,


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Current masterObjects list consist of: Master name: Kohler Generator master,


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Current foundDevicesNamesList consist of: device Name: Kohler Generator master, device Name: Alarm 0001, device Name: Device 10009, device Name: Device 10010, device Name: Device 10008,


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Current foundDevicesRefNumList consist of: device ref: 387, device ref: 389, device ref: 391, device ref: 393, device ref: 395,


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Updated the plugin devices to lists given by homeseer.


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Got our saved master devices from masterDevices.txt


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Got our saved devices from devices.txt


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Creating a discrete lite device


    5/27/2022 10:15:03
    modbusSeer
    Debug
    Postback!!!!!!!!!!!!!!!!!!


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Checking device: Device 10010


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Checking device: Device 10009


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Checking device: Alarm 0001


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Found master device: Kohler Generator master


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Checking device: Kohler Generator master


    5/27/2022 10:14:46
    modbusSeer
    Debug
    Running: getCurrentMasterDevicesForHtml


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Current slaveObjects list consist of: device name: Alarm 0001, device name: Device 10009, device name: Device 10010,


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Current masterObjects list consist of: Master name: Kohler Generator master,


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Current foundDevicesNamesList consist of: device Name: Kohler Generator master, device Name: Alarm 0001, device Name: Device 10009, device Name: Device 10010,


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Current foundDevicesRefNumList consist of: device ref: 387, device ref: 389, device ref: 391, device ref: 393,


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Updated the plugin devices to lists given by homeseer.


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Got our saved master devices from masterDevices.txt


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Got our saved devices from devices.txt


    5/27/2022 10:14:36
    modbusSeer
    Debug
    Creating a discrete lite device

    Tags: None
Previous template Next
Working...
X