Webserver does not come up anymore

[Magnumandy]

Checklist

• I have followed the install preparation procedure - including the verification part I, II & III.
• I have installed the latest release (or BETA) version of the integration and home assistant.
• 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
• 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
• 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

The procedure to set the Webserver variable into active mode (param_set 39 TRUE) still works, but no Webserver is accessible in standard operating mode. What a shame.

Add your DEBUG log output

No response

[marq24]

can you please be so kind and explain a bit more, what's the "new" situation?

Is there just no GUI - or is the complete webserver gone?! Does requests like this still return a result?

http://admin:[BRIDGE_PASSWORD]@[YOUR_IP]/metrics.json?node_id=1

[Magnumandy]

Hi, thanks for asking. I went into the console like described and set the parameter 39 to TRUE. Then I saved the parameters and left the "Admin mode". After that I unplugged the device, put it back in and it connected to the Tibber Pulse, transferring data to Tibber again. But there is no way to log into the Webserver, even though the parameter for forcing the Webserver to ON is still set to TRUE.
I tried several times, also with the IP the Fritzbox gave to the Tibber Bridge. Nothing there...

[Magnumandy]

So no GUI, yes. I did not try your request, because I assumed that it does not make sense if I cannot access the Webserver...

[marq24]

If there was not firmware update @ tibber site I assume it's "just" a local issue - you might like to try a different browers (and make sure that you pass the basic auth)...

[droloff]

same here - received a new pulse just a few days ago.
followed this instruction (very well documented - thx for that)
No gui, nmap shows no open tcp ports (80 and 443 are connection refused)
name of the bridge via dhcp is 'Bridged5800ee80'

looks like the webserver_force_enable is no longer supported or better no longer evaluated.
i could get / set value 39 in access point mode

[marq24]

would be cool, if you can share the firmware version numbers...

[alexanderniebuhr]

I contacted tibber support in September about this, and got the information that the webserver was disabled by their devs. They are planning to add a new way to access pulse locally but haven’t released it yet.

[bauerj]

I've tried the procedure just now and it seems to have worked on my device:

[alexanderniebuhr]

It looks like based on firmware version and device age, there different settings