search

nobl / ioBroker.senec

ioBroker adapter for Senec Home
Other
27 stars 7 forks source link

Senec changed to https #164

Closed MaBernO closed 10 months ago

MaBernO commented 10 months ago

Since 17.8. i have no access with the standard port 80 to my senec V2.1 I noticed some software update from senec. The web interface is now accessible via the https port (443). Nothing else seems to have changed.

Can you support this variant in the adapter?

REVISION MCU: 3825

REVISION MCU-BL: 2307

REVISION NPU-REGS: 10

REVISION NPU-IMAGE: 2307

REVISION GUI: 2966

REVISION INV: 660

REVISION NSP: 243 / 243

nobl commented 10 months ago

Currently preparing release 1.4.2. This will have an option to switch to https in settings.

This is currently considered "experimental" because I have no ways to test it. So feedback is appreciated!

This change should not cause issues with systems not supporting https (yet).

MaBernO commented 10 months ago

I tried it with 1.4.2 with enabled https option:

senec.0 2023-08-21 22:39:41.763 error Error: Error connecting to Senec (IP: https://192.168.178.247). Exiting! (unable to verify the first certificate). Try to toggle https-mode in settings and check FQDN of SENEC appliance.
senec.0 2023-08-21 22:39:41.761 info unable to verify the first certificate
senec.0 2023-08-21 22:39:41.005 info connecting to Senec: https://192.168.178.247/lala.cgi
MaBernO commented 10 months ago

seems to be a problem with senec's certificate. Maybe the option NODE_TLS_REJECT_UNAUTHORIZED=0 needs to be passed.

nobl commented 10 months ago

can you try to update from github? I made some changes in main.js - hoping that works :)

Or just modify main.js like: https://github.com/nobl/ioBroker.senec/commit/81cc4279512d4d5facdf18c15d95cf3c39f2855c

MaBernO commented 10 months ago

same error again. I added process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; in the adapter init (with 1.4.2) communication with senec was working.

nobl commented 10 months ago

yeah - just that pretty much is "kill them all" :) I would prefer solving that via user-agent settings

MaBernO commented 10 months ago

Ok, if you have another proposal i will try it out.

nobl commented 10 months ago

Just pushed another update to github - while I cannot test with a senec on https I tried with another machine and it looks promising :)

MaBernO commented 10 months ago

1.4.3 is working with https. Thank you very much.

nobl commented 10 months ago

Thanks for reporting of course testing :)