elad-bar / DahuaVTO2MQTT

Listens to events from Dahua VTO unit and publishes them via MQTT Message
103 stars 39 forks source link

Cannot get Docker version working #15

Closed mmnpkf closed 3 years ago

mmnpkf commented 3 years ago

Hi, I was having issues installing the add-on so I have had a go at installing the docker version using Portainer but I cannot get it to work. Clearly I’ve done something wrong but I cannot figure out what. The mqtt broker seems to report that the connection keeps timing out and no messages are actually published. Can you tell me what I’ve done wrong?

This is what the container log says:

2020-10-31 04:09:22 < Dahua VTO Event Listener START >, 2020-10-31 04:09:22 DahuaVTOAPI::SetDeviceDetails Device Type: VTO2000A, 2020-10-31 04:09:22 DahuaVTOAPI::SetDeviceDetails Serial Number: 5D049E4PAZ36C28, 2020-10-31 04:09:22 DahuaVTOEventListener::Login Started, 2020-10-31 04:09:22 DahuaVTOEventListener::Login Completed successfully, 2020-10-31 04:09:22 DahuaVTOEventListener::KeepAlive Started keepAlive thread, 2020-10-31 04:09:22 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:09:23 MQTTManager::connect Connecting, 2020-10-31 04:09:23 MQTTManager::publish Published topic 'DahuaVTO/RtspSessionDisconnect/Event', message: {"Action":"Start","Data":{"Device":"::ffff:192.168.86.254","LocaleTime":"2020-10-31 14:09:22","StreamType":"Main","UTC":1604117362,"UserAgent":" Rtsp Client\/3.0"},"deviceType":"VTO2000A","serialNumber":"5D049E4PAZ36C28"}, 2020-10-31 04:10:23 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:11:04 MQTTManager::connect Connecting, 2020-10-31 04:11:04 MQTTManager::publish Published topic 'DahuaVTO/TimeChange/Event', message: {"Action":"Pulse","Data":{"BeforeModifyTime":"31-10-2020 14:11:04","LocaleTime":"2020-10-31 14:11:04","ModifiedTime":"31-10-2020 14:11:04","UTC":1604117464},"deviceType":"VTO2000A","serialNumber":"5D049E4PAZ36C28"}, 2020-10-31 04:11:04 MQTTManager::connect Connecting, 2020-10-31 04:11:04 MQTTManager::publish Published topic 'DahuaVTO/NTPAdjustTime/Event', message: {"Action":"Pulse","Data":{"Address":"time.google.com","Before":"31-10-2020 14:11:02","LocaleTime":"2020-10-31 14:11:04","UTC":1604117464,"result":true},"deviceType":"VTO2000A","serialNumber":"5D049E4PAZ36C28"}, 2020-10-31 04:11:25 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:12:25 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:13:25 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:14:25 DahuaVTOEventListener::KeepAlive keepAlive back, 2020-10-31 04:15:25 DahuaVTOEventListener::KeepAlive keepAlive back,

And the log from the mqtt broker says:

1604117363: New connection from 172.30.33.10 on port 1883. [INFO] found mqtt_user on Home Assistant 1604117363: New client connected from 172.30.33.10 as dahua-vto-dahuavto (p1, c1, k10, u'mqtt_user'). 1604117379: Client dahua-vto-dahuavto has exceeded timeout, disconnecting. 1604117435: Saving in-memory database to /data/mosquitto.db. 1604117464: New connection from 172.30.33.10 on port 1883. 1604117464: New client connected from 172.30.33.10 as dahua-vto-dahuavto (p1, c1, k10, u'mqtt_user'). 1604117464: Client dahua-vto-dahuavto disconnected. 1604117464: New connection from 172.30.33.10 on port 1883. 1604117464: New client connected from 172.30.33.10 as dahua-vto-dahuavto (p1, c1, k10, u'mqtt_user'). 1604117480: Client dahua-vto-dahuavto has exceeded timeout, disconnecting. 1604117764: New connection from 172.30.33.10 on port 1883. [INFO] found mqtt_user on Home Assistant 1604117765: New client connected from 172.30.33.10 as dahua-vto-dahuavto (p1, c1, k10, u'mqtt_user'). 1604117765: Client dahua-vto-dahuavto disconnected. 1604117765: New connection from 172.30.33.10 on port 1883. 1604117765: New client connected from 172.30.33.10 as dahua-vto-dahuavto (p1, c1, k10, u'mqtt_user'). 1604117781: Client dahua-vto-dahuavto has exceeded timeout, disconnecting.

mmnpkf commented 3 years ago

Actually, I spoke too soon. Despite the timeout message it does seem to working.