-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Senec changed to https #164
Comments
Currently preparing release 1.4.2. 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). |
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. |
seems to be a problem with senec's certificate. |
can you try to update from github? Or just modify main.js like: |
same error again. |
yeah - just that pretty much is "kill them all" :) |
Ok, if you have another proposal i will try it out. |
Just pushed another update to github - while I cannot test with a senec on https I tried with another machine and it looks promising :) |
1.4.3 is working with https. |
Thanks for reporting of course testing :) |
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
The text was updated successfully, but these errors were encountered: