Not getting entities

[philder]

Hello.

I've installed the integration from HACS, then I added the configuration.yaml. Restarted the HA. When HA started I configured the new integration. Everything went well unitl I restarted. HA have "discovered" again the "new" integration. I tried a different method: Installed by HACS, left the configuration.yaml part and added Securitas Direct in the Integrations by clicking in the Plus button. Restarted. Everything went well but I didn't get any entities.

I'm in Portugal by the way.

Thank you!

[guerrerotook]

Thanks, do you have any other logs in the homeassistant.log in your installation. Something that I can work with?

[TheGui01]

Hello,

Same issue here :

The only log found at the restart is : 2022-09-17 09:57:26.952 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration securitas which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-09-17 09:58:03.840 WARNING (SyncWorker_9) [homeassistant.helpers.service] Unable to find services.yaml for the securitas integration

The integration with my user is the functional one. The one named Securitas direct keeps appearing as a new device that can't be ignored and it pops at every restart in HA notification.

[josecarre]

Hi,

This this you mention @TheGui01 : The one named Securitas direct keeps appearing as a new device that can't be ignored and it pops at every restart in HA notification.

Is also happening to me. I have my alarm configured right, working fine... but it always detects a new/second installation in which sms code never work... so I just can ignore this new devices detected and live with the pain of the notification on every HA restart 😆

[alnavasa]

Had this issue, remove everything form the cofiguration yaml solved the issue

Edit: Remove, restart, reconfigure via user interface, not Yaml, and done.

[TheGui01]

Hello,

Thanks for this tips, it works on my side as well.

Nevertheless, I'm wondering if it's exactly the expected behavior because at the reinstall, I took off everything for the configuration.yaml, and I had to add it again to have the intégration appearing.

Regards, Guillaume Sourd

Le lun. 19 sept. 2022 à 23:40, alnavasa @.***> a écrit :

Had this issue, remove everything form the cofiguration yaml solved the issue

— Reply to this email directly, view it on GitHub https://github.com/guerrerotook/securitas-direct-new-api/issues/81#issuecomment-1251590962, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXUJD2GPLMDPAEPITZN7MR3V7DMTLANCNFSM6AAAAAAQOP2DQM . You are receiving this because you were mentioned.Message ID: @.***>

[josecarre]

Had this issue, remove everything form the cofiguration yaml solved the issue

This fixed my notification issue, thanks! :)

[philder]

I solved the notification issue in my first post. I'm sorry if I wasn't clear enough. This is another problem: "Not getting entities".

I get this logs:

`Este erro teve origem numa integração personalizada.

Logger: custom_components.securitas.securitas_direct_new_api.apimanager Source: custom_components/securitas/securitas_direct_new_api/apimanager.py:297 Integration: Securitas Direct (documentation, issues) First occurred: 12:31:19 (1 occurrences) Last logged: 12:31:19

Unauthorized`

`Logger: homeassistant.helpers.service Source: helpers/service.py:439 First occurred: 12:31:36 (1 occurrences) Last logged: 12:31:36

Unable to find services.yaml for the securitas integration`

Thank you