The integration will connect locally to your system. No dependency on the cloud, and instantaneous updates, but is harder to set up. You will need the panel access code (default 5678) to your system, this access code is NOT the same as the installer/subinstaller code, and with older models, you might need to either disconnect your system from the cloud, or set up a proxy that will allow you to connect both locally and via the cloud.
Still cant connect, not sure how to set it up, theres no doc.
What’s in the logs? Maybe the owner can help? It should work, lots of people are using it…
Maybe you are using the wrong panel code, I know the addon is doing a brute force , I don’t thing the integration does that
Maybe you guys have a board not supported by default, you really need to enable debug and create GitHub issue, the owner is very helpfulll, so it can be fixed!
It’s a very new integration, it could have small bugs…
Ok still got the warning clock.
I looked at my clock on my risco device and it seems its 2/8/2022
So a year back.
Probably thats the cause?
I tried to change it back, but i cant?
Is this cause i’m local now, and not cloud anymore.
I cant change time?
You should be able to change the date/time on the panel.
However my time is wrong as well. The date is correct, but when setting the time, it is off by 10 minutes after a while.
Probably because it can’t connect to an NTP server because the board only allows 1 IP connection (being Home Assistant). So you can set the clock, but it won’t sync automatically. And just like my microwave clock it messes up time after a while. Annoying, but not blocking.
I read in another topic that the clock timeout error can be safely ignored.
just setup a local NTP server on your panel, and make sure you define the correct timezone
if you have old socket , with 1 connection, you can use the NTP on it, so all local connections can do it, cause you disabled cloud, so it can again connect to internet
