Managing "In service" state

[poldim]

This might be pretty edge case, but...

I had an alert set to remind me to close the door every hour if the door was open for more than an hour. This has been pretty useful as it's reminded me to shut the door when I otherwise would have forgotten. Since the service center tech had the door open when they entered service mode, HA is "stuck" thinking the door is open.

It seems like Rivian's service process now requires their techs to go put it into service mode which stops the data upload that's visible through the integration. This wasn't the case my first few visits, or at least the data kept flowing. Right now, all of my values are frozen in their state when the car was put into service.

Is there a better way to handle this? Maybe write the values you know wont receive updates to null when it detects service mode is on?

[jrgutier]

Just have a conditional that the service_mode entity is off.

…

-- J.R. Gutierrez

On Mon, Sep 30, 2024 at 5:58 PM DK ***@***.***> wrote: *This might be pretty edge case*, but... I had an alert set to remind me to close the door every hour if the door was open for more than an hour. This has been pretty useful as it's reminded me to shut the door when I otherwise would have forgotten. Since the service center tech had the door open when they entered service mode, HA is "stuck" thinking the door is open. It seems like Rivian's service process now requires their techs to go put it into service mode which stops the data upload that's visible through the integration. This wasn't the case my first few visits, or at least the data kept flowing. Right now, all of my values are frozen in their state when the car was put into service. Is there a better way to handle this? Maybe write the values you know wont receive updates to null when it detects service mode is on? image.png (view on web) <https://github.com/user-attachments/assets/36226b83-0f06-4648-8fed-48bfb94ba315> image.png (view on web) <https://github.com/user-attachments/assets/2e607458-5ee7-4301-b027-d7857e5f99ba> — Reply to this email directly, view it on GitHub <#179>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACTMO7MQYHZYGK6OGQCFZ3ZZHJTDAVCNFSM6AAAAABPELMLAWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TONZZGAZDGNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>