Hey good to hear!

I don't know what am I doing wrong, but it seems that the connection is not correctly building up:

Topic: MTConnect/Devices/364a87e1-7814-47b5-b1ec-8cf0a77bacff/Observations/Adapter/adapter_http_037e74ac8a/Events/ConnectionStatus/adapter_http_037e74ac8a_connStatus/adapter_http_037e74ac8a_connStatusQoS: 0

{"dataItemId":"adapter_http_037e74ac8a_connStatus",
"name":"connStatus",
"type":"CONNECTION_STATUS",
"timestamp":"2023-03-03T10:43:00.72546Z",
"result":"ESTABLISHED"}

Topic: MTConnect/Devices/364a87e1-7814-47b5-b1ec-8cf0a77bacff/Observations/Adapter/adapter_http_037e74ac8a/Events/ConnectionStatus/adapter_http_037e74ac8a_connStatus/adapter_http_037e74ac8a_connStatusQoS: 0

{"dataItemId":"adapter_http_037e74ac8a_connStatus",
"name":"connStatus",
"type":"CONNECTION_STATUS",
"timestamp":"2023-03-03T10:43:00.8389373Z",
"result":"CLOSED"}

Topic: MTConnect/Devices/364a87e1-7814-47b5-b1ec-8cf0a77bacff/Observations/Adapter/adapter_http_037e74ac8a/Events/ConnectionStatus/adapter_http_037e74ac8a_connStatus/adapter_http_037e74ac8a_connStatusQoS: 0

{"dataItemId":"adapter_http_037e74ac8a_connStatus",
"name":"connStatus","type":
"CONNECTION_STATUS","timestamp":
"2023-03-03T10:43:00.8390545Z",
"result":"LISTEN"}

I just attached you the probe from the machine.
probe_haas_vf4.txt

My settings as you told:

clients:
- address: http://192.168.22.153/
  port: 8082
  deviceKey: VF-4
  useSSL: false
  heartbeat: 0

Log File from the MQTT Broker Gateway

2023-03-03 11:41:43.8709|0|INFO|agent-logger|Configuration File Read Successfully from: C:\Program Files\TrakHound\MTConnect-MQTT-Broker-Gateway-Agent\agent.config.yaml 
2023-03-03 11:41:43.9441|0|WARN|agent-logger|No Devices Found : Reading from :  
2023-03-03 11:45:34.0559|0|WARN|agent-logger|No Devices Found : Reading from :  

Thanks for information. I will have a new Release published either today or tomorrow that should fix this issue.

Thanks,
-Patrick

Hey nice to hear! i am looking forward to this. How can i send you a little gift for your work? :-)

I published the v5.3.0 Release earlier today that should solve this issue.

Thanks for the support! I do have a donations page if you are interested: PayPal Donations

Please let me know if you run into any other issues.

Thanks,
-Patrick

Thanks for the work! Now it works perfect, I'll collect the data now few days and weeks and will see how i can use them the best :-)

Thank you so much for the support! I'm glad to hear everything is working now and please let me know if you run into anything else.

Thanks,
-Patrick

The main change I made in commit cec7741 was that when I read from the HTTP client adapter and add the Observations to the agent, I'm adding it with the DeviceKey (which can be either the UUID or Name) instead of only by the UUID. The MTConnectAgent class resolves that DeviceKey to the matching device.

The other two commits were to get the MQTT Gateway agents to allow a device file to override the Probe.

Let me know how it works for you as I'm sure you aren't the only one to run into this issue.

yes this worked great.
thank you again.

@PatrickRitchie is the same applicable to embedded mtconnect agent.

@smtpl-iiotian Yes I believe this should work using an embedded agent as well. Let me know if you run into any issues with it though and I will be glad to help.

@PatrickRitchie please share link of sample haas-override.xml

@PatrickRitchie, I have 3 Haas NGC machines which has same id, name and uuid in the Haas MTConnect Agent on port 8082. What makes difference is the serialNumber in the Description. Please see 3 images attached.

Can I add serialNumber in the Gateway Agent Configuration (agent.config.yaml) ?
Kindly guide.

You may be able to use the DeviceMapping configuration in the HTTP Adapter Module as shown below:

- http-adapter:
    address: http://192.168.1.81
    port: 8082
    deviceKey: Machine
    devices:
      Machine:
        name: Machine-01-Name
        uuid: Machine-01-UUID
        id: Machine-01-ID

- http-adapter:
    address: http://192.168.1.82
    port: 8082
    deviceKey: Machine
    devices:
      Machine:
        name: Machine-02-Name
        uuid: Machine-02-UUID
        id: Machine-02-ID

- http-adapter:
    address: http://192.168.1.83
    port: 8082
    deviceKey: Machine
    devices:
      Machine:
        name: Machine-03-Name
        uuid: Machine-03-UUID
        id: Machine-03-ID

This was a configuration option that I added a while ago but did not document yet and should allow you to change the Name, UUID, and ID of each device from the remote agent.

Let me know if this is what you were looking for.

@PatrickRitchie lot of thanks, above configuration worked fine.