I tested both devices, the only equiment’s that work are the card’s, the gateways does not work.
Hi,
I’ve been using this Integration for a few months without issue. Just recently, all the sensors have quit reporting. I can still use the Open & Stop Buttons (The Close Button was always greyed out which didn’t bother me) but the sensors were useful because I wrote an automation to check on the position and now its obviously doesn’t work.
Any Idea’s why the sensor data has stopped updating?
P.S.
The screenshot below shows the out of date sensor data from last HA reboot.
The gate is actually “Open” and in a “Stopped” state at the time of taking that screenshot as waiting on a Pizza delivery LOL.
I ran into exactly the same thing and it turned out not to be a Home Assistant bug, but a limitation of the CAME Connect cloud API.
CAME Connect only publishes real status updates (VarcoStatusUpdate) while the gate is physically moving. When the gate is idle for a while, the WebSocket goes quiet and the REST /devicestatus endpoint often returns cached or incomplete data. When the integration relied on that, sensors like phase, moving and position would either freeze or drop to unknown, even though commands like Open, Close and Stop still worked.
What I changed locally was to store (latch) the last known good state that arrived via a real push update. Phase and position are only updated when a valid motion event comes in. When the gate is idle and no new events arrive, the integration keeps the last known values instead of overwriting them with unknown. That immediately stopped the sensors “dying” after idle periods.
There is one important caveat though. After a Home Assistant restart, the integration starts cold. If the CAME cloud does not provide a valid current phase and position in the initial REST snapshot, there is nothing trustworthy to latch yet. In that case the sensors can still show unknown or 0% until the gate is moved once. Triggering a single open or close forces the cloud to emit fresh motion updates, after which the state is correct again and remains stable while idle.
So in short:
• Commands still work because they are command endpoints, not state driven
• Sensor data goes stale because CAME does not push idle state
• Latching the last known state fixes it during normal operation
• A restart still needs one real movement unless state is persisted across reboots
If CAME ever add a proper “status refresh” or heartbeat endpoint, the integration could be improved further, but with the current API this is about as reliable as it gets
@UKICS Thank you for the information, very informative and I do appreciate it but I’m afraid I don’t understand this enough to make the “latch” change you suggested.
Hi everyone.
I’m in the process of retrofitting my CAME sliding gate motor and would like to know if I need to use a CAME key (eg. 806SA-0140) or if a CAME gateway (eg. 806SA-0200) is also sufficient?
What are all of you using?
Key for me
1 Like
I’m in preparation of integrating my gate so I don’t know the correct sensor names and states, but this is how I would deal with it, which is also creating latched sensors:
Eg.
> template:
> - trigger:
> - platform: state
> entity_id: sensor.gate.position
> to:
> - open
> - closed
> - stopped
> sensor:
> - name: "Gate Position Latched"
> unique_id: gate_position_latched
> state: "{{ trigger.to_state.state }}"
you need gateway. This is a way for your gate to connect to your WiFi - hence to connect to CAME cloud. The key, according to my findings when i had the same question, is for the installers to configure the controller of your gate.
Thank you for the info. For now I bought a key, following the info from @UKICS
On Friday they will install the gate, so Saturday I’ll be able to test if everything is working.
If you got 806SA-0140 - then it is the gateway, and you are good 
1 Like
I have installed the integration (many thanks!!!) and all works well, except for opening my gate: the button to open the gate is available but the gate doesn’t open. Closing and stopping the gate is no problem - any idea what I can check? (I’ve just started with HA so bear with me ) The log files don’t show an error, but I do get an e-mail from Came Connect itself that it wasn’t able to execute an instruction.
I’ve been testing further, but to no avail. In Came Connect, I have three ID’s - one for my gateway, one for transmitter in the motor housing and one for the actual gate (I think). Whatever ID I enter, the states of the gate are reported correctly as is the position of the gate, but depending on the ID I enter in the integration, I can’t perform any operation or only closing and stopping, but never opening.
try with the dedicated app (CAME automation) - if you can open the gate from there. It will not fix it, but at least you will know whether the issue is with the gate/gateway or the integration itself.
Opening with the Came automation app works without problem. Closing with the HA integration is not a problem, and the status of the gate is reported correctly. For now, I’ve used a workaround via Google Home.
weird… what CAME controller do you have?