After FW update to #6c2b710b - it doesn't work anymore - cause `webserver-force_enable` is gone

td007 commented 2 months ago

Checklist

[X] I have installed the latest release (or BETA) version of the integration and home assistant.
[X] I have prepared DEBUG log output (for technical issues) | In most of the cases of a technical error/issue I would have the need to ask for DEBUG log output of the integration. There is a short tutorial/guide 'How to provide DEBUG log' here
[X] I am aware that rotating the tibber pulse reading head anti clockwise can improve data quality | See this user comment and the next comment as well
[X] I confirm it's really an issue | In the case that you want to understand the functionality of a certain feature/sensor Please be so kind and make use if the discussion feature of this repo (and do not create an issue) - TIA

Add a description

Since today it hasn't worked anymore, maybe there was an update? No problems so far. I have reconnected to the AP. There is no longer any "webserver-force_enable" under PARMS. version: #6c2b710b shows it, maybe that will help

Add your DEBUG log output

no logs

td007 commented 2 months ago

Model: TJH01

marq24 commented 2 months ago

well... if there is a new firmware without the option to request the internal webserver... But then I still would expect some output in the HA logs from the integration!

So here 'version: #90a20be3' is running - you might find a way to downgrade the Pulse/Bridge firmware to this version (no clue how this can be done)?! and disable the ota_enabled flag...

There is nothing I could do from my side here...

td007 commented 2 months ago

I was afraid of that. Thank you very much for your support and the quick response :-)

marq24 commented 2 months ago

Please find below the "current" DL links of the #90a20be3 firmware as they are listed on my bridge (use everything on your own risk) - but IF you have success - please share what you did!

Model	Version	Current	url	size	checksum	filename	verified	running
tibber-pulse-ir-hub-esp32	1362-90a20be3	1362-90a20be3	https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin	1441780	c305c8217600a77979404fe92c2e65d8f42502a5	/spiffs/hub-esp32_1362-9.ota	No	No
tibber-pulse-ir-hub-css	1362-90a20be3	1362-90a20be3	https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.css.gz	8286	ce62706530e7193cda035d2dc8ea3fd04b182282	/spiffs/hub-css_1362-9.ota	No	No
tibber-pulse-ir-hub-js	1362-90a20be3	1362-90a20be3	https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.js.gz	19730	98244559752f84264efc582b7c0be7c0af148721	/spiffs/hub-js_1362-9.ota	No	No
tibber-pulse-ir-hub-efr32-fg23	587-3b4e4388	587-3b4e4388	https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg23-587-3b4e4388-654.gbl	174216	3bb21b705b68bb8c88a1ef33134242db2975a8df	/spiffs/hub-efr32-_587-3b.ota	No	No
tibber-pulse-ir-hub-efr32-fg1	587-3b4e4388	587-3b4e4388	https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg1-587-3b4e4388-654.gbl	154304	46a324faa2de708e0dd65b9462b694b0543653c6	/spiffs/hub-efr32-_587-3b.ota	No	No
tibber-pulse-ir-node-efr32	1007-56bd9fb9		https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-node-1007-56bd9fb9-697.gbl	180260	ef645bb40b724909398a3882ab428231f9a75a91	/spiffs/node-efr32_1007-5.ota	No	No
tibber-pulse-clamp-node-efr32-fg23	1007-56bd9fb9		https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-clamp-1007-56bd9fb9-697.gbl	175120	86120192f62de7beb522cc1352759a2f58317700	/spiffs/mp-node-ef_1007-5.ota	No	No

marq24 commented 2 months ago

again all here "try it on your own risk"...

there is a console http://[YOUR-IP]/console

When I type ota_manifest I'll get the following output:

tibber-bridge> ota_manifest
esp32> ota_manifest
manifest version 2310.1
1: model: 'tibber-pulse-ir-hub-esp32' manifest_version: '1362-90a20be3' state: 'up2date' current_version: '1362-90a20be3' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin' manifest_size: 1441780 manifest_checksum: 'c305c8217600a77979404fe92c2e65d8f42502a5' manifest_product_id: 0x0 manifest_ota_tag: 0 filename: '/spiffs/hub-esp32_1362-9.ota'
100: model: 'tibber-pulse-ir-hub-css' manifest_version: '1362-90a20be3' state: 'up2date' current_version: '1362-90a20be3' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.css.gz' manifest_size: 8286 manifest_checksum: 'ce62706530e7193cda035d2dc8ea3fd04b182282' manifest_product_id: 0x0 manifest_ota_tag: 0 filename: '/spiffs/hub-css_1362-9.ota'
101: model: 'tibber-pulse-ir-hub-js' manifest_version: '1362-90a20be3' state: 'up2date' current_version: '1362-90a20be3' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.js.gz' manifest_size: 19730 manifest_checksum: '98244559752f84264efc582b7c0be7c0af148721' manifest_product_id: 0x0 manifest_ota_tag: 0 filename: '/spiffs/hub-js_1362-9.ota'
200: model: 'tibber-pulse-ir-hub-efr32-fg23' manifest_version: '587-3b4e4388' state: 'up2date' current_version: '587-3b4e4388' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg23-587-3b4e4388-654.gbl' manifest_size: 174216 manifest_checksum: '3bb21b705b68bb8c88a1ef33134242db2975a8df' manifest_product_id: 0xe0e0 manifest_ota_tag: 0 filename: '/spiffs/hub-efr32-_587-3b.ota'
202: model: 'tibber-pulse-ir-hub-efr32-fg1' manifest_version: '587-3b4e4388' state: 'up2date' current_version: '587-3b4e4388' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg1-587-3b4e4388-654.gbl' manifest_size: 154304 manifest_checksum: '46a324faa2de708e0dd65b9462b694b0543653c6' manifest_product_id: 0xbabe manifest_ota_tag: 0 filename: '/spiffs/hub-efr32-_587-3b.ota'
300: model: 'tibber-pulse-ir-node-efr32' manifest_version: '1007-56bd9fb9' state: 'up2date' current_version: '' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-node-1007-56bd9fb9-697.gbl' manifest_size: 180260 manifest_checksum: 'ef645bb40b724909398a3882ab428231f9a75a91' manifest_product_id: 0xc0c0 manifest_ota_tag: 123 filename: '/spiffs/node-efr32_1007-5.ota'
301: model: 'tibber-pulse-clamp-node-efr32-fg23' manifest_version: '1007-56bd9fb9' state: 'up2date' current_version: '' manifest_url: 'https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-clamp-1007-56bd9fb9-697.gbl' manifest_size: 175120 manifest_checksum: '86120192f62de7beb522cc1352759a2f58317700' manifest_product_id: 0xd0d0 manifest_ota_tag: 223 filename: '/spiffs/mp-node-ef_1007-5.ota'

ota_manifest_set

So according to the console help there is:

ota_manifest_set  <model> <version> <url> <size> <checksum> <product_id> <ota_tag>
  Flash ota file from source.
       <model>  Model to flash
     <version>  Version to flash
         <url>  Url to flash
        <size>  Filesize of file to flash
    <checksum>  Checksum to flash
  <product_id>  product_id
     <ota_tag>  ota_tag

taking the information from my bridge, then the commands:

ota_manifest_set tibber-pulse-ir-hub-esp32 1362-90a20be3 https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin 1441780 c305c8217600a77979404fe92c2e65d8f42502a5 0x0 0

ota_manifest_set tibber-pulse-ir-hub-css 1362-90a20be3 https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.css.gz 8286 ce62706530e7193cda035d2dc8ea3fd04b182282 0x0 0

ota_manifest_set tibber-pulse-ir-hub-js 1362-90a20be3 https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.js.gz 19730 98244559752f84264efc582b7c0be7c0af148721 0x0 0

should be the once that will flash the "old" FW again...

ota_esp32_flash

could be that it's might be even simply via the ota_esp32_flash command?!

ota_esp32_flash https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin

ota_esp32_flash https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin

ota_esp32_flash https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.js.gz

and then after a reboot a ota_clean

V4n1X commented 2 months ago

Because of a maybe auto OTA update I also backuped those OTA files localy. If you still can visit the OTA page, can you check what the exact firmware version is?

We have the firmware version: 1362-90a20be3

You told us you got the firmware version XXXX-6c2b710b

Maybe you can fill that XXXX ?

If possible post your OTA manifest output.

marq24 commented 2 months ago

Maybe you can fill that XXXX ?

IMHO 1390

you can get the details from: https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/fallback.manifest

{
    "version": "2408.3",
    "group": "",
    "manifest": [
        {
            "model": "tibber-pulse-ir-hub-esp32",
            "version": "1390-6c2b710b",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1390-6c2b710b-6028.bin",
            "checksum": "4adaf5835727de5a272a91ad97b2912b47523ccd",
            "size": 1507316
        },
        {
            "model": "tibber-pulse-ir-node-efr32",
            "product_id": 49344,
            "version": "1169-b31fd4c9",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-node-1169-b31fd4c9-1047.gbl",
            "checksum": "9e7b59df76f7c8d7fa19ce318f622063d14e1277",
            "size": 180464,
            "ota_tag": 123
        },
        {
            "model": "tibber-pulse-ir-hub-css",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1390-6c2b710b-6028.css.gz",
            "size": 8286,
            "checksum": "ce62706530e7193cda035d2dc8ea3fd04b182282",
            "version": "1390-6c2b710b"
        },
        {
            "model": "tibber-pulse-ir-hub-js",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1390-6c2b710b-6028.js.gz",
            "size": 19873,
            "checksum": "df023c47c9c7e4992cb9a5ce42b85ff1c8407ebc",
            "version": "1390-6c2b710b"
        },
        {
            "model": "tibber-pulse-ir-hub-efr32-fg1",
            "product_id": 47806,
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg1-720-25ea36a5-2739.gbl",
            "size": 161496,
            "checksum": "e2d95e97f4c217b6639f037d598ae119f757ae81",
            "version": "720-25ea36a5"
        },
        {
            "model": "tibber-pulse-clamp-node-efr32-fg23",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-clamp-1169-b31fd4c9-1047.gbl",
            "size": 183176,
            "checksum": "7e9c92ae8baf944ed6a04790bc6000234fc88d71",
            "version": "1169-b31fd4c9",
            "product_id": 53456,
            "ota_tag": 223
        },
        {
            "model": "tibber-pulse-ir-hub-efr32-fg23",
            "url": "https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg23-720-25ea36a5-2739.gbl",
            "size": 181712,
            "checksum": "6688e91e8d638313e8498eadda8599ec2f096a12",
            "version": "720-25ea36a5",
            "product_id": 57568
        }
    ],
    "ts": "1723553531-0985317"
}

marq24 commented 2 months ago

@td007 - bitte einmal das "hier" versuchen?! wenn Du magst -> https://github.com/marq24/ha-tibber-pulse-local/discussions/38

ckarrie commented 2 months ago

"Leider" war meine Bridge die letzten 2 Tage ungewollt offline, daher habe ich noch Version 1362-90a20be3 drauf. Daten kommen sowohl bei Tibber als auch in der Integration an. Kann ich euch hier helfen?

tibber-bridge Update manifest:

Model                   Version     URL                                                             Filename
tibber-pulse-ir-hub-esp32       1362-90a20be3   https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-ir-hub-esp32-1362-90a20be3-5396.bin   /spiffs/hub-esp32_1362-9.ota
tibber-pulse-ir-hub-css         1362-90a20be3   https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.css.gz          /spiffs/hub-css_1362-9.ota
tibber-pulse-ir-hub-js          1362-90a20be3   https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/main-1362-90a20be3-5396.js.gz           /spiffs/hub-js_1362-9.ota
tibber-pulse-ir-hub-efr32-fg23      587-3b4e4388    https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg23-587-3b4e4388-654.gbl           /spiffs/hub-efr32-_587-3b.ota
tibber-pulse-ir-hub-efr32-fg1       587-3b4e4388    https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/hub-fg1-587-3b4e4388-654.gbl            /spiffs/hub-efr32-_587-3b.ota
tibber-pulse-ir-node-efr32      1007-56bd9fb9   https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-node-1007-56bd9fb9-697.gbl        /spiffs/node-efr32_1007-5.ota
tibber-pulse-clamp-node-efr32-fg23  1007-56bd9fb9   https://tibber-firmware.s3.eu-west-1.amazonaws.com/tibber+bridge/TJH01/binaries/pulse-clamp-1007-56bd9fb9-697.gbl       /spiffs/mp-node-ef_1007-5.ota

marq24 commented 2 months ago

@ckarrie - eigentlich gar nicht [ich bin auch noch auf der '1362-90a20be3'] - und da gibt es diese neue Herausforderung noch nicht... es sei denn Du magst "Versuchskaninchen spielen" und läßt den hub auf die neue FW via "auto ota" (wann auch immer das passieren mag) updaten... und dann kannst Du checken, ob #38 die Lösung für die neu FW darstellt...

td007 commented 2 months ago

Bei mir hat es funktioniert. Vielen Dank für Ihre Hilfe. Ihr seid einfach großartig 🙏🎉❤️

td007 commented 2 months ago

Hallo Matthias, es hat funktioniert.

Vielen Dank für Deine tolle Arbeit 😀 LG Tiemo

Matthias Marquardt @.***> schrieb am Do. 12. Sept. 2024 um 10:50:

@td007 https://github.com/td007 - bitte einmal das "hier" versuchen?! wenn Du magst -> #38 https://github.com/marq24/ha-tibber-pulse-local/discussions/38

— Reply to this email directly, view it on GitHub https://github.com/marq24/ha-tibber-pulse-local/issues/36#issuecomment-2345663057, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA666UWSV3JOGS6INPUBASLZWFIWRAVCNFSM6AAAAABN6MJXEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBVGY3DGMBVG4 . You are receiving this because you were mentioned.Message ID: @.***>

td007 commented 2 months ago

Noch zur Vollständigkeit hier die Infos des nun wieder funktionierenden Webservers:

Note: Default username is 'admin' and the password is the QR-CODE Status: pairing_status: idle up_time: 148102 poll_time: 0 firmware: esp: 1390-6c2b710b efr: 720-25ea36a5 wifi_status: ip: xxxxxxxxxx ssid: xxxxxxxxxx bssid: xxxxxxxxxxxx rssi: -17 connected: true wifi_err_buff: mqtt_status: connected: true subscribed: true last_error: esp_tls_last_esp_err: 0 esp_tls_stack_err: 0 esp_tls_cert_verify_flags: 0 error_type: 0 connect_return_code: 0 esp_transport_sock_errno: 0 ota_update_running: false version: #6c2b710b

td007 commented 2 months ago

Jetzt stellt sich mir noch die Frage: OTA-Update ausschalten? Oder ist es nun schon deaktiviert? „ota_update_running: false“

marq24 commented 2 months ago

wenn, dann wäre das m.E. nach das Flag ota_enable - aber da das jetzt nach dem update kein Thema mehr ist, kannst Du erstmal weiter AUTO-UPDATES beziehen :-)

thoughtgap commented 2 months ago

Mein Pulse hat sich heute Nacht geupdatet und dabei einen neuen Hostnamen bekommen BridgeXXXXX, vorher Tibber-Host. Habe die Home Assistant Integration nun auf IP umgestellt.

Der Webserver-Parameter fehlt jetzt wie erwartet in der /params Übersicht, ich musste jedoch nichts ändern, er scheint weiterhin zu laufen.

marq24 commented 2 months ago

Der Webserver-Parameter fehlt jetzt wie erwartet in der /params Übersicht, ich musste jedoch nichts ändern, er scheint weiterhin zu laufen.

kannst Du so gut sein und "trotzdem" mal die console anwerfen und param_get 39 anwerfen ?! [und bestätigen, das die Ausgabe wie in #38 beschrieben ist] - danke

thoughtgap commented 2 months ago

tibber-bridge> param_get 39
esp32> param_get 39
webserver_force_enable (39):
true
Command 'param_get 39' executed successfully

Ich update auch das andere Issue, zur Dokumentation.

marq24 commented 2 months ago

daaanke!

malloy139 commented 1 month ago

Hat auch jemand das Problem, dass seit dem OTA Update oft keine Daten mehr kommen? Screenshot_20240927-193623_1

marq24 commented 1 month ago

Hat auch jemand das Problem, dass seit dem OTA Update oft keine Daten mehr kommen?

Was sagt denn der Batteriezustand des Lesekopfs?

marq24 / ha-tibber-pulse-local