Sensors immediately become unavailable

[joshmd]

Got the wireless battery powered doorbell to be recognised and added to the MQTT but after 1 second it all the sensors become unavailable.

My MQTT log also looks like this:

1624557936: Socket error on client , disconnecting. 1624558056: New connection from 172.30.32.2 on port 1883. 1624558056: Socket error on client , disconnecting. 1624558176: New connection from 172.30.32.2 on port 1883. 1624558176: Socket error on client , disconnecting. 1624558296: New connection from 172.30.32.2 on port 1883. 1624558296: Socket error on client , disconnecting. 1624558416: New connection from 172.30.32.2 on port 1883. 1624558416: Socket error on client , disconnecting. 1624558536: New connection from 172.30.32.2 on port 1883. 1624558536: Socket error on client , disconnecting.

[matijse]

This looks like the MQTT script keeps crashing, restarting and crashing again, etc...

Can you show the log of the Add-on / or combined.log file in the data directory?

[joshmd]

The addon log was blank so I restarted it and got the following:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Eufy Home Assistant MQTT Bridge
 Publish events as MQTT messages
-----------------------------------------------------------
 Add-on version: 1.18.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 6.1  (amd64 / qemux86-64)
 Home Assistant Core: 2021.6.6
 Home Assistant Supervisor: 2021.06.6
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:53:15] INFO: Exporting log level for nodejs: info
[10:53:15] INFO: Symlinking data dir
[10:53:15] INFO: Running 'eval' commands
[10:53:15] INFO: Generating config.yml from options.json
[10:53:15] INFO: Image build with version 0.2.18
[10:53:15] INFO: starting original stuff...
> eufy-ha-mqtt-bridge@1.0.0 start /app
> NODE_ENV=production node --unhandled-rejections=strict index.js
info: Migrating the database... {"timestamp":"2021-07-05T09:53:17.045Z"}
info: Stored device: Doorbell (T8210P0020240845 - type: T8210) {"timestamp":"2021-07-05T09:53:18.804Z"}

[matijse]

Looks fine to me, are you still getting disconnects?

[joshmd]

Yep it is still unavailable.

[matijse]

Maybe when you run the add-on with log level 'debug' there will be more information? I think this is an option in the add-on config...

[joshmd]

Hmmm, doesn't seem to give much more:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Eufy Home Assistant MQTT Bridge
 Publish events as MQTT messages
-----------------------------------------------------------
 Add-on version: 1.19.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 6.1  (amd64 / qemux86-64)
 Home Assistant Core: 2021.6.6
 Home Assistant Supervisor: 2021.06.8
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:49:08] INFO: Exporting log level for nodejs: debug
[10:49:08] INFO: Symlinking data dir
[10:49:08] INFO: Running 'eval' commands
[10:49:08] INFO: Generating config.yml from options.json
[10:49:08] INFO: Image build with version 0.2.19
[10:49:08] INFO: starting original stuff...
> eufy-ha-mqtt-bridge@1.0.0 start /app
> NODE_ENV=production node --unhandled-rejections=strict index.js
info: Migrating the database... {"timestamp":"2021-07-07T09:49:09.468Z"}
debug: ---- EUFY INITIALIZE START ---- {"timestamp":"2021-07-07T09:49:09.478Z"}
debug: ----  Created classes... {"timestamp":"2021-07-07T09:49:09.478Z"}
debug: Refreshing devices... {"timestamp":"2021-07-07T09:49:09.479Z"}
info: Stored device: Doorbell (T8210P0020240845 - type: T8210) {"timestamp":"2021-07-07T09:49:11.240Z"}
debug: ----  Refreshed devices {"timestamp":"2021-07-07T09:49:11.241Z"}
debug: ----  Set up MQTT handler {"timestamp":"2021-07-07T09:49:11.241Z"}

[matijse]

I think it is an issue with the MQTT broker then... Verify the password, url, etc... Try to get more debug logging on the MQTT broker side... On thing I encountered sometimes is that the HA MQTT add-on does not allow you to use homeassistant and some other names like mqtt as the username...

The add-on seems to run fine up until the point it is trying to connect to the MQTT broker...

[joshmd]

Yeah I did try that already, and I saw the one about using homeassistant as the user name, which I haven't done. I will play around with the MQTT side though and see if I can get it working.

Thanks.