search

RFD-FHEM / RFFHEM

Counterpart of SIGNALDuino, it's the code for FHEM to work with the data received from the uC
GNU General Public License v3.0
44 stars 33 forks source link

Wrong Firmware downloaded / matched if cc1101 filename contains hardware name without cc1101 #913

Open sidey79 opened 3 years ago

sidey79 commented 3 years ago

Expected Behavior

For hardware esp8266 the firmware SIGNALDuino_ESP8266_test2.hex will be downloaded

Actual Behavior

For hardware esp8266 the wrong firmware is downloaded: SIGNALDuino_ESP8266cc1101_test2.hex

2020.12.16 22:15:18.806 3: sduino: ParseHttpResponse, Error while flashing: Sorry, Flashing your ESP8266 via Module is currently not supported.
2020.12.16 22:15:18.792 3: sduino: Set_flash, filename FHEM/firmware/SIGNALDuino_ESP8266cc1101_test2.hex provided, trying to flash
2020.12.16 22:15:18.766 3: sduino: ParseHttpResponse, Downloaded SIGNALDuino_ESP8266cc1101_test2.hex firmware from github-production-release-asset-2e65be.s3.amazonaws.com
2020.12.16 22:15:18.758 3: sduino: ParseHttpResponse, url https://github-production-release-asset-2e65be.s3.amazonaws.com/27504581/0f7de600-3fe2-11eb-9839-0df27e961824?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201216%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201216T211517Z&X-Amz-Expires=300&X-Amz-Signature=69fa16a11ed34c34197e950db1cbbe7232b611c28766f02909dba0f93d891e66&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=27504581&response-content-disposition=attachment%3B%20filename%3DSIGNALDuino_ESP8266cc1101_test2.hex&response-content-type=application%2Foctet-stream returned: 376192 bytes Data
2020.12.16 22:15:16.281 3: CommandGet: sduino called with HASH(0x54df010)
2020.12.16 22:15:14.689 3: CommandGet: sduino called with HASH(0x5b54430)
2020.12.16 22:15:14.613 3: sduino: Set_flash, test2 try to fetch release https://api.github.com/repos/RFD-FHEM/SIGNALDuino/releases/tags/test2
2020.12.16 22:15:14.612 3: sduino: Set_flash, test2 try to fetch github assets for tag test2

Steps to Reproduce the Problem

  1. attr hardware ESP8266
  2. get availablefirmware
  3. set flash test2

Specifications

elektron-bbs commented 3 years ago

Ich hänge das mal gleich hier mit an, obwohl es das beschriebene Problem nicht direkt trifft. Bei "set sduinoIP flash..." bekomme ich immer timeouts. Ich hatte das schon vor einigen Tagen. Ich dachte erst, es liegt am Server, das ist aber jetzt immer noch so.

2020.12.22 16:40:01 1: sduinoIP: found availableFirmware for ESP32,ESP32cc1101,ESP8266,ESP8266cc1101,MAPLEMINI_F103CB,MAPLEMINI_F103CBcc1101,nano328,nanoCC1101,miniculCC1101,promini,radinoCC1101
2020.12.22 16:40:25 3: sduinoIP: Set_flash, 3.5.0-dev+20201207 try to fetch github assets for tag 3.5.0-dev+20201207
2020.12.22 16:40:25 3: sduinoIP: Set_flash, 3.5.0-dev+20201207 try to fetch release https://api.github.com/repos/RFD-FHEM/SIGNALDuino/releases/tags/3.5.0-dev+20201207
2020.12.22 16:40:31 3: sduinoIP: ParseHttpResponse, error while requesting https://github-production-release-asset-2e65be.s3.amazonaws.com/27504581/2d358180-4181-11eb-91a8-422cf455458d?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201222%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201222T154026Z&X-Amz-Expires=300&X-Amz-Signature=e41d6e202e53a3088fd7eae5f5366aafea69a0297768c9f40c8ba741f01aedc5&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=27504581&response-content-disposition=attachment%3B%20filename%3DSIGNALDuino_ESP8266cc1101_3.5.0-dev%2B20201207.hex&response-content-type=application%2Foctet-stream - read from https://github-production-release-asset-2e65be.s3.amazonaws.com:443 timed out
2020.12.22 16:41:21 3: sduinoIP: Set_flash, 3.4.0 try to fetch github assets for tag 3.4.0
2020.12.22 16:41:21 3: sduinoIP: Set_flash, 3.4.0 try to fetch release https://api.github.com/repos/RFD-FHEM/SIGNALDuino/releases/tags/3.4.0
2020.12.22 16:41:30 3: sduinoIP: ParseHttpResponse, error while requesting https://github-production-release-asset-2e65be.s3.amazonaws.com/27504581/45126f00-c7b7-11ea-95bc-e893b5183a7a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201222%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201222T154123Z&X-Amz-Expires=300&X-Amz-Signature=b79a3e52583c508016ad107f922c1b8b80cbc30c934685c66b36f2af5dfa35cc&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=27504581&response-content-disposition=attachment%3B%20filename%3DSIGNALDuino_ESP8266cc11013.4.0.hex&response-content-type=application%2Foctet-stream - read from https://github-production-release-asset-2e65be.s3.amazonaws.com:443 timed out
2020.12.22 16:42:15 1: sduinoUSB0: SD_WS_Parse UNDEFINED sensor SD_WS_51_TH detected, code SD_WS_51_TH_2
2020.12.22 16:42:17 3: sduinoIP: Set_flash, 3.3.1 try to fetch github assets for tag 3.3.1
2020.12.22 16:42:17 3: sduinoIP: Set_flash, 3.3.1 try to fetch release https://api.github.com/repos/RFD-FHEM/SIGNALDuino/releases/tags/3.3.1
2020.12.22 16:42:23 3: sduinoIP: ParseHttpResponse, error while requesting https://github-production-release-asset-2e65be.s3.amazonaws.com/27504581/a19c9180-160d-11ea-8f22-85210651e4fc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201222%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201222T154217Z&X-Amz-Expires=300&X-Amz-Signature=ade2dfc29f016c147acd6c0429e3150f4c57f5f42ebe1fb7836d9b0c0e455f41&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=27504581&response-content-disposition=attachment%3B%20filename%3DSIGNALDuino_ESP8266cc11013.3.1.hex&response-content-type=application%2Foctet-stream - read from https://github-production-release-asset-2e65be.s3.amazonaws.com:443 timed out
sidey79 commented 3 years ago

@elektron-bbs

Ich habe das gerade eben probiert. Funktioniert alles bestens. Könnte es an irgendwas bei dir liegen oder tritt der Fehler nur sporadisch auf?

elektron-bbs commented 3 years ago

Jetzt funktionierte es hier eben auch wieder. Scheint dann wohl ein temporäres Problem gewesen zu sein.

HomeAutoUser commented 3 years ago

Sind wir hier beim dem Issues durch oder gibt es noch offene Punkte oder Testvarianten?

sidey79 commented 3 years ago

@HomeAutoUser Die Timeouts waren temporär, das eigentliche Issue wurde bisher noch nicht angegangen.