Azure / azure-iot-protocol-gateway

Azure IoT protocol gateway enables protocol translation for Azure IoT Hub
Other
224 stars 152 forks source link

Provide non MQTT device sample #44

Open JeanBedard opened 8 years ago

JeanBedard commented 8 years ago

Hi guys,

From what I understand, one of the main goal of the protocol gateway is to allow non iot ready devices to communicate with Azure IoT Hub. For instance, a TCP based proprietary protocol GPS tracker could connect to the protocol gateway and reach the Azure IoT Hub though it.

The sample provided in this project is demonstrating a device that already support MQTT. I think you should provide a sample where the iot device don't support any of MQTT/AMQP/HTTP/TLS but plain old TCP with some basic protocol.

What do you think ? Thanks! Jean

59985 commented 8 years ago

Hi, Any news? Regards Kasper

mtuchkov commented 8 years ago

Hi @JeanBedard, You have a very valid statement. The main goal of protocol gateway is to enable users to customize the way devices are communicating with IoT Hub, for instance in еру MQTT scenario it supports QoS 2, retransmission, etc.

Regarding the plain TCP example, I think this is a good idea, just obviously is not a high priority. Meantime, everybody is always welcome to contribute. It must be relatively simple to do and if there are any questions feel free to ask in the Gitter.

59985 commented 8 years ago

I have a simple http post from a device that I want to send to the Iot Hub. I have looked into the endtoendtest to get some experience , but I an doing something wrong. Every time I run it I get following error "System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain. This can happen if the test(s) started a thread but did not stop it. Make sure that all the threads started by the test(s) are stopped before completion."

Patrik-Berglund commented 7 years ago

Hi,

I'm also interrested in a plain TCP example. Setting up the netty pipeline shouldn't be any problem, but there seems to be MQTT specific code in the ProtocolGateway.Core and ProtocolGateway.IotHubClient that needs to be modified?

And are there any plans on adding support for Direct methods and Device twin functionality?

mikeasharp commented 6 years ago

I am interested in a bespoke binary and text based TCP protocol handler, for interfacing legacy GPS trackers into IoT hub. Many of these use bidirectional TCP persistent connections.

ewinkiser commented 6 years ago

I am also interested in TCP Protocol handler for our devices to communicate with IoT Hubs. Has anyone had any luck in doing this? Thanks, Mike

oacsed commented 6 years ago

Still nothing? Almost 2 years later, the Azure Protocol Gateway is still a pain to use.

A simple basic TCP example would be much more useful than an example to "customize MQTT". There are still plenty of MQTT-related code in ProtocolGateway.Core, which make it hard for people to use for something not related to MQTT.

Please provide a more structured code, and something agnostic to MQTT.

navedmir commented 6 years ago

any update on this?

VK-Wipro commented 6 years ago

Any update on this?

amerzafar commented 6 years ago

I am also interested in TCP Protocol example

oacsed commented 5 years ago

Bump.

brandonavant commented 5 years ago

Update. There are some details on a Stack Overflow conversation here. I've not yet attempted any of the suggestions, but that's at least something I guess.

ravitol commented 5 years ago

I am also interested in getting raw TCP data from the IoT device to IoT Hub. Has anyone had success implementing the SO suggestion. Any feedback would be appreciated

ghost commented 3 years ago

Any update on this?