What to do when there is no webserver_force_enable on the param tab of your Tibber Pulse IR Bridge

[marq24]

Seams to work 'rock' solid

Nevertheless - what every you do, you do it on your own risk

Situation

With the new hardware revision TJH02 and with the new firmware '1390-6c2b710b' rolled out via OTA for the TJH01 the webserver_force_enable parameter is no longer shown on the http://[YOUR-IP]/params/ page.

Working Solution

1. Go to http://[YOUR-IP]/console/

2. type param_get 39 (just to ensure, that the system still know the webserver_force_enable parameter) - you can also try to type param_get webserver_force_enable [and press the send button afterwards] - this should give you some output like this:

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

3. So if 39 (= webserver_force_enable) is still present, then and only then you can continue!

4. type param_set 39 TRUE (the upper case of TRUE is important here) [and press the send button afterwards]

5. type param_store [and press the send button afterwards]

6. for confirmation you can type again param_get 39 [and press the send button afterwards]

Now continue with the default instructions

• 4. Bring your Pulse & Bridge back to normal operation
• 5. Final testing [do not continue if you did not completed this final step]

Please let me know, if this will work for you - TIA!

Credits

• Joachim

[td007]

It worked for me.
Thank you very much for your help.
You guys are just great
🎉🙏

[mager33]

Is the firmware update enforced? Seems I'd rather not install it if it makes problems.

[thoughtgap]

My Pulse's firmware was auto-updated to #6c2b710b last night at 2am CEST. The hostname changed from tibber-host to bridgeXXXXXXXXX, so the Home Assistant integration went offline. I changed to a fixed IP via router and it worked again.

Webserver-Parameter is not visible on /params page anymore, but the webserver_force_enable is still true:

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

[iwbl-eu]

The param-39 procedure on the console worked for me after having initialized and fully updated both bridge and pulse. The param had not been part of the params list in the params tab of course. I could login with the local IP address afterwards. So, still working as of today.
Many thanks!

[typxxi]

I am still wondering how to migrate without loosing my sensors I have gotten from the tibber integration.
I would have to do a lot of work to fix that or match the sensors by renaming maybe.

But I would like to go ahead with a local solution I can rely on cause I had connection errors most likely caused by tibber due to the fact that the tibber app was still working at home.

Thanks

[marq24]

your question seams to be unrelated to the topic - so you might simply start a new one (might be also in German - since I do not understand much of your question)...