Had earlier upgrade my Rasp Pi 4 to Buster and upgraded Z2M and Domoticz - these are working OK but Z2MA sometimes lists all devices and sometimes just 2 or 3 and they all say "NO COMPONENTS Maybe this device is not (yet) supported by Zigbee2Mqtt?"
Currently on Z2MA version Build Docker 3.0.11+azure on linux, arm Created 2020-04-18 15:27:02
So I thought I would upgrade to the latest image. Tried 2 ways:
setting compose file to image: carldebilly/zigbee2mqttassistant:latest and then run the compose
in Portainer / Images / zigbee2mqttassistant / details / clicking Pull from Registry - popup says downloaded
but in both cases Docker says still at 3.0.11
BUT just seen the Z2MA log says v0.3.157 and the log also says
Disconnected from MQTT server 192.168.1.42.
.....
"Now listening on: http://[::]:80" - see below
Accessing Z2MA on http://192.168.1.42:8880/ is just showing 2 devices: bridge/info and bridge/logging. Both flagged "NO COMPONENTS"
Expected behavior
Latest version to install and devices to be found.
Installation
Version of Zigbee2Mqtt: 1.22.0
Version of Zigbee2MqttAssistant: Docker says 3.0.11+azure on linux, arm BUT Docker Z2MA log says v0.3.157
Installation type (HASS.IO, Docker...): Docker
Docker version + CPU type (amd64, arm arm64...): Standalone 19.03.5 [Correction] 32-bit ARM 71
OS: Rasp Pi Buster Linux 5.4.79-v7l+ #1373 SMP armv7l
Pertinent logs
`Starting Zigbee2MqttAssistant v0.3.157+Branch.master.Sha.ea388c3bbc2d43c4c9c62f27bb6764911ba4acc9...
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
No XML encryptor configured. Key {469d15b3-8d70-49b5-8e6d-6b495c4612c3} may be persisted to storage in unencrypted form.
Hosting environment: Production
Content root path: /app
Now listening on: http://[::]:80
Application started. Press Ctrl+C to shut down.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Disconnected from MQTT server 192.168.1.42.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at MQTTnet.Client.MqttClient.TrySendKeepAliveMessagesAsync(CancellationToken cancellationToken)
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Another network scan request already in progress.
Application is shutting down...
warn: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Disconnected from MQTT server 192.168.1.42.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at MQTTnet.Client.MqttClient.TrySendKeepAliveMessagesAsync(CancellationToken cancellationToken)
Starting Zigbee2MqttAssistant v0.3.157+Branch.master.Sha.ea388c3bbc2d43c4c9c62f27bb6764911ba4acc9...
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
Hosting environment: Production
Content root path: /app
Now listening on: http://[::]:80
Application started. Press Ctrl+C to shut down.
Describe the bug
Had earlier upgrade my Rasp Pi 4 to Buster and upgraded Z2M and Domoticz - these are working OK but Z2MA sometimes lists all devices and sometimes just 2 or 3 and they all say "NO COMPONENTS Maybe this device is not (yet) supported by Zigbee2Mqtt?"
Currently on Z2MA version Build Docker 3.0.11+azure on linux, arm Created 2020-04-18 15:27:02
So I thought I would upgrade to the latest image. Tried 2 ways:
BUT just seen the Z2MA log says v0.3.157 and the log also says
Accessing Z2MA on http://192.168.1.42:8880/ is just showing 2 devices: bridge/info and bridge/logging. Both flagged "NO COMPONENTS"
Expected behavior Latest version to install and devices to be found.
Installation
Pertinent logs
Additional context
Compose file
Accessing Z2MA on http://192.168.1.42:8880/
Many thanks for reading. Hope this can be resolved and I can once again use this very useful utility. Alan