Pi Zero W service restarting constantly about room-assistant

[adirburke]

I fixed this but setting the StartTimeOut to infinity

From TimeoutStartSec=120 to TimeoutStartSec=0

[kreene1987]

Just to add detail, I set up the service file EXACTLY per the documentation, tested a longer timeout, but it still restarts, just at the longer timeout interval.

I am running the nodejs 16.15.0 and room-assistant 2.20.0.

[kreene1987]

'''

Jun 04 18:52:57 mbedroom room-assistant[5664]: 04/06/2022, 18:52:57 - info - BluetoothLowEnergyService: Discovered n>
Jun 04 18:53:10 mbedroom systemd[1]: room-assistant.service: start operation timed out. Terminating.
Jun 04 18:53:10 mbedroom systemd[1]: room-assistant.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit room-assistant.service has entered the 'failed' state with result 'timeout'.
Jun 04 18:53:10 mbedroom systemd[1]: Failed to start room-assistant service.
░░ Subject: A start job for unit room-assistant.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit room-assistant.service has finished with a failure.
░░
░░ The job identifier is 851 and the job result is failed.
Jun 04 18:53:10 mbedroom systemd[1]: room-assistant.service: Consumed 49.071s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit room-assistant.service completed and consumed the indicated resources.
Jun 04 18:53:11 mbedroom sudo[5661]: pam_unix(sudo:session): session closed for user root
Jun 04 18:53:21 mbedroom systemd[1]: room-assistant.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit room-assistant.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 04 18:53:21 mbedroom systemd[1]: Stopped room-assistant service.
░░ Subject: A stop job for unit room-assistant.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit room-assistant.service has finished.
░░
░░ The job identifier is 916 and the job result is done.
Jun 04 18:53:21 mbedroom systemd[1]: room-assistant.service: Consumed 49.071s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit room-assistant.service completed and consumed the indicated resources.
Jun 04 18:53:21 mbedroom systemd[1]: Starting room-assistant service...
░░ Subject: A start job for unit room-assistant.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit room-assistant.service has begun execution.
░░
░░ The job identifier is 916.
'''

[adirburke]

Did you fix this ?

I have the exact same problem

[kreene1987]

This kind of works (I mean it works, sure) but it's in a "starting" state forever basically.

I'm probably looking to move to ESPresence or a different solution as @mKeRix seems to have moved on to other priorities (no heartburn!)

[adirburke]

Yeah I just dropped a few $$ on six Pis for the house so Im gonna keep trying to get it to work.
My Typescript is not amazing but shouldnt take long to pick up the basics

Its werid that this bug only displayed on 2 out of the 6 devices, the other 4 seem to get through the starting state

[github-actions]

There hasn't been any activity on this issue recently. In an effort to provide a better overview of current issues we automatically clean some of the old ones. Many of them may already be resolved in newer versions of room-assistant.
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.