totalconnect error when arming and no sensor state

[fwedler]

The problem

1. When arming (both Away and Home) I get the error listed below in the log. Arming works while all sensors are closed. It fails with no feedback if a sensor is open (even though I can't see state, Added LuciDeviceScanner to scan OpenWrt Luci-RPC enabled router's state. #2 below).

2. While all the available sensors appear as entities, their state is always Closed. I never get state updates when the sensor changes state. My provider tells me I have the Smart Security Package which includes monitoring for up to 50 sensors so, it should be providing the sensor state.

Environment

Clean install of Hass.io 107.5 with only SSH and totalconnect configured.

• Home Assistant release with the issue: 107.5
• Last working Home Assistant release (if known): unknown
• Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
• Integration causing this issue: totalconnect
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/totalconnect

Problem-relevant configuration.yaml

totalconnect:
    username: YOUR_USERNAME
    password: YOUR_PASSWORD

Traceback/Error logs

http://homeassistant.local:8123/frontend_latest/chunk.968b1309403fc4a99a5b.js:142:705 TypeError: t is null

Additional information

[fwedler]

Arming works as long as all sensors are ready at the panel. If a sensor is not ready, then arming fails with no feedback in Hass.io interface or logs. Since I can't see sensor state in Hass.io, I can't test if arming would be disabled when sensors are open but that is what I would expect for behavior.

[austinmroczek]

I will need to investigate the first problem and get back with you.

For the second problem of sensors always showing as Closed, have you enabled "Sensor Events"? At least using Total Connect IOS app you go to More > Settings > Notifications > Sensor Events.

[fwedler]

Ah, yes, enabling sensor events addresses part 2. Thanks! Perhaps that can be added to the documentation.

[austinmroczek]

@fwedler I think we need to split problem 1 into two pieces, A and B.

1.A) The UI error in your log. I'll need to ask for some help on that from the front end folks. I haven't touched front end stuff at all, just the totalconnect component which is all back end.

1.B) Why there is no feedback when arming fails. Right now that's how it is coded - a request to arm is sent to Total Connect but no feedback is given to Home Assistant on if it worked or not. I need to confer with the core team, but likely I'll split this out as a new Issue/Feature Request. I'd be the one to work it.

2. Documentation. I wrote the documentation at https://www.home-assistant.io/integrations/totalconnect/ which obviously wasn't clear enough. I'll get that updated if you could post recommended changes.

[fwedler]

For the documentation, in the Binary Sensor section, I would add the following to the end of the first paragraph:

If available, these can be found in the Total Connect 2 web portal at Notifications>Sensor Events. Alternately, they can be found in the Total Connect iOS app at More>Settings>Notifications>Sensor Events.
Enable each sensor you want to monitor.

[austinmroczek]

I installed 0.107.5 with only Total Connect enabled and got a similar (but slightly different) error in the frontend javascript file. I then removed Total Connect from the configuration and restarted, and the javascript error remained.

Logger: frontend.js.latest.202003181
Source: components/system_log/__init__.py:209
First occurred: 3:09:44 PM (5 occurrences) 
Last logged: 3:09:44 PM

http://192.168.1.241:8123/frontend_latest/chunk.d2a7f931de0365b3d7b0.js:1987:2093 TypeError: e is undefined

@fwedler Please disable Total Connect in your configuration.yaml and see if you still get the error message you originally posted

[fwedler]

@austinmroczek I only get the error when triggering arm or disarm from Lovelace. If I remove Total Connect from the config, then the arm/disarm buttons are unavailable to trigger the event that causes the logged error in home-assistant.log.

[austinmroczek]

Regarding 1.B above:

We're close to putting out total-connect-client v0.55 with craigjmidwinter/total-connect-client#79, which will return true if an attempt to arm is successful. Once that's in place I'll submit a new PR here that will account for that and if it doesn't arm for some reason, I plan to use https://www.home-assistant.io/integrations/persistent_notification/ to tell the user.

[austinmroczek]

@fwedler sorry it's taken a bit longer than I thought. You'd think being stuck at home would make things go faster, but working at my computer all day makes it less fun to spend the evening there as well. I submitted a pull request that will give you a notification if arming or disarming the system fails for some reason.

Next I'll finally get to the javascript error in the UI. Since it's running in the browser, please give me your browser name and version number.

[fwedler]

Yeah, I hear ya. I'm usually running HA in Firefox. Current version says 76.0.1 but Firefox updates itself all the time.

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[austinmroczek]

Sorry @fwedler I never got back to this. I'm hoping maybe you've upgraded and don't have the UI javascript problem anymore.

[fwedler]

I've been keeping up with updates and haven't seen the error. Everything's been working fine. Thanks!