[Reactor] Variables not updating correctly in latest-25201-2aa18550

[cw-kid]

@toggledbits

Its connected now and has imported the devices and scenes from the Atom in to entities area.

I see this though in alerts:

x_ezlo_sys.hardware="rev2"

So what's rev2 ?

sys_system.state=true
x_ezlo_sys.anonymous_access_enabled=null
x_ezlo_sys.architecture="esp32"
x_ezlo_sys.firmware="0.8.539"
x_ezlo_sys.hardware="rev2"
x_ezlo_sys.kernel="v4.1-rc-4-gbd72a9ab2"
x_ezlo_sys.model="ATOM32"
x_ezlo_sys.reconnects=1
x_ezlo_sys.restarts=1
x_ezlo_sys.serial="70060304"
x_ezlo_sys.support_enabled=null
x_ezlo_sys.support_status=null
x_ezlo_sys.temperature_scale="fahrenheit"
x_ezlo_sys.temperature_unit="F"
x_ezlo_sys.upsince=1624528447000
x_ezlo_sys.using_cloud_auth=true
x_ezlo_sys.using_cloud_relay=true
x_ezlo_sys.uuid=null
Capabilities: sys_system, x_ezlo_sys
Actions: sys_system.restart, x_ezlo_sys.runlua, x_ezlo_sys.set_setting

Thanks

[toggledbits]

That's gen2, so you may have local access. If you want to use local access, your Atom needs a stable IP address (static or DHCP reserved). You can put that into the source field (uncomment now), and also set disable_ecc_ciphers to true. Then restart Reactor.

  config:
    source: "wss://your-atom-ip:17000"
    serial: "7006nnnn"
    username: "whatever"
    password: "whatever"
    disable_ecc_ciphers: true

This may or may not work for you. My rev2 Atom is on firmware 0.8.798, and it allows remote access. I don't have an Atom with 0.8.539 that is at rev2, so I don't know if rev2 will work at that firmware level. I do have a rev3 Atom at 0.8.539, and it does allow remote access, so I think it should, but we'll see...

[cw-kid]

@toggledbits said in Support for Ezlo Atom controllers?:

You can put that into the source field (uncomment now), and also set disable_ecc_ciphers to true. Then restart Reactor.

Done that.

I cleared the alert and restarted MSR. It hasn't come back again as yet.

And I can still see the Ezlo Atom items in entities.

[toggledbits]

@cw-kid said in Support for Ezlo Atom controllers?:

It hasn't come back again as yet.

I'm not sure what you mean by this. What "it" are you referring to?

[cw-kid]

@toggledbits

The yellow warning alert hasn't come back again since adding disable_ecc_ciphers: true to the reactor.yaml flie.

And I uncommented the source line. The Atom already has a DHCP reserved LAN IP.

[cw-kid]

@toggledbits

I didn't comment the username and password lines however.

I should do that if it is really only local access to the hub APi via the source line?

[toggledbits]

Don't uncomment the username and password. That only works for Plus/Secure hubs with anonymous access enabled. Atoms do not support anonymous access, so it is still necessary to get the access tokens from the cloud, even when connecting to the Atom locally.

[cw-kid]

@toggledbits

OK. Do you know how long the tokens last and will MSR automatically request a new one when it does expire?

Thanks.

[toggledbits]

Supposedly 24 hours from what I can see. An expiration is given when the token is acquired. I haven't observed that there is any consequence to the expiration being met, though... it appears that access continues even after the token's expiration time/date. My presumption would be that access terminates when the token expires. Looks like more unfinished work there at eZLO to me.

Any disconnect will cause a reconnect retry.

[cw-kid]

@toggledbits

I'm inclined to agree with you.

I have a token obtained by using Renes python script for my Ezlo Plus for use with curl commands and I bet that same token still works today I will have to try it again.

Token was probably obtained 12 months ago maybe.

[toggledbits]

Yup, that's definitely a security issue, and not the only one I'm concerned about, which is another reason I'm unlikely to be using an eZLO hub in my home for anything more than development of this tool.