Hi all, I successfully used the HTTP_GET cards in my first ESP8266 project and then discovered the Homeyduino app. For Homeyduino just put something like Homey.trigger(“TuinSensor”,Sensor); in the ESP code and it runs fine. The HTTP_GET method is using http.begin(address+URI); with http.GET(); to call the Homey API. It returns the http code, normaly 200. However approximately 15% of the transfers return 404 or -5. If that happens I repeat the call. Not nice, but this seems to work fine. No data loss. So now my question: If so many transfers fail when using the GET card app, I am afraid Homeyduino also has no 100% of success. But how does Homeyduino deal with failing transfers? Can Homeyduino notify me when a transfer fails? I have read all I could find about the Homeyduino app, but still need your help here. Thanks.

Hi Jan, I am using Homeyduino without any issues. Of course that might be different in your case. I however think the app works just fine. Not sure how it handles failed transfers. I assume it just skips failed transmissions.

Homeyduino is indeed running fine in several other ESP projects. I don’t think it skips failed transmissions as that would be quite unreliable. I still hope someone can explain us the algorithm.

The code is available. But from looking at it, I don’t get the impression that there’s any mitigation for failed transmissions. For sending data back to Homey, it makes an HTTP connection to Homey (so I assume that the Homeyduino app on Homey creates an HTTP server to receive these messages). If the connection fails, nothing is done about it. If the Homeyduino app returns an error as response to the transmission, nothing is done about it either. So any error mitigation has to be done in your own code.

Thanks Robert for pointing me to the lines that matter. I’ll have a try in understanding what it means for my project.

[image] [App][Pro] ESP Easy (Firmware for ESP32, NodeMCU, Wemos...) Apps I created an app for communicating with ESP Easy firmware for development boards like the NodeMCU v3 and Wemos D1. You can use this combination to easily build your own sensors, switches and actuators and interface then with Homey. The app should support the latest release 2.* version of the firmware, you can find those on their Github page. I currently run release mega-20200608. You can install the app from the Homey app store I maintain a Github Wiki page that contains a lot of information …

Is anyone interested in developing this code for the RP2040 so that is could use the same app? I could be wrong but I was thinking that the code might be simular but with a few adjustments. I was looking at writing my own in micropython but I could not find detailed documentation of the json formatting for each use case to work it out. If anyone has more details on this I can give it a try?

[image] Gary_Russell: but I could not find detailed documentation of the json formatting for each use case to work it out athombv/homey-arduino-library/blob/master/docs/protocol.md # The Homeyduino network protocol Communication between Homey and Homeyduino devices happens using TCP and UDP packets on port ```46639```. UDP is used for device discovery while general communication is done using ```JSON``` data sent and received using ```HTTP``` over ```TCP```. # Device discovery Devices can be discovered by sending an empty UDP broadcast packet on port ```46639```. Available devices will answer with a ```JSON``` object describing the device. This is the same ```JSON``` object returned when accessing the device index ```/``` using ```HTTP``` over ```TCP``` on port ```46639```. If ```UDP``` broadcasting is not available devices can still be manually added by querying the device information over ```TCP``` by manually entering the IP address of the device into the Homey application. ## The device information JSON object Example: ``` { "id": "example", "version": "0.0.0", "type": "homeyduino", "class": "sensor", "master": { "host": "0.0.0.0", This file has been truncated. show original

Thanks, I found that article but it only really shows the discovery payload. It does also mention the URL for the GET and POST but wanted to undertand what should be returned to Homey Pro when requested and also what does Homey send when registering a trigger event? I’m guessing its sending me information to posibly a webhook but was not fully sure. i.e. If Homey Pro sens a GET to the URL “/cap/measure_humidity” do I just send raw data back or shoudl be be json formatted?

Homeyduino versus HTTP_GET

Apps

JPe4619 June 10, 2020, 9:07am 7

Topic		Replies	Views
Homeyduino @ V2.0 Apps	48	6203	March 7, 2019
Werkt homeyduino nog? 🇳🇱 Nederlands (Dutch) homey-pro	1	378	June 12, 2022
Http GET funktioniert nicht mehr Fragen & Hilfe	4	417	January 2, 2023
Homeyduino ontvangt de commando's niet Vragen & hulp	4	709	February 26, 2021
HTTP GET commandos naar Homey versturen Questions & Help	5	1505	February 11, 2019

Homeyduino versus HTTP_GET

Related topics