I have seen that, only some times, the names of the Drivers are not updated correctly in the Web view channel, and if they are correct updated in the CLI.
Which can lead to confusion, I think Driver was published fine and users of the Channel see the incorrect name.
It is assumed that the two information, CLI and Web channel, come from the same source.
Thanks
? Select a channel for the driver. 2
┌────┬────────────────────────────────────────────┬──────────────────────────────────────┐
│ # │ Name │ Driver Id │
├────┼────────────────────────────────────────────┼──────────────────────────────────────┤
│ 1 │ SmartThings Multipurpose Sensor Mc │ 6a11b350-2cfd-45e1-afd8-676cf83aa4b1 │
│ 2 │ ST-Zigbee Motion Sensor Mc │ 59cae0e2-63e8-4f85-baeb-d64f431d4232 │
│ 3 │ Zigbee Contact Mc │ a01bd113-efa3-45f1-8b56-a7ed0dbd1689 │
│ 4 │ Zigbee Contact Sonoff Test │ 5493481f-7905-4516-b81d-ce7165365911 │
│ 5 │ Zigbee Level ColorTemp Bulb Mc │ ab8c024e-9134-4940-9c2e-b60b042cb095 │
│ 6 │ Zigbee Level ColorTemperature Light Mc │ 4ff0ceba-8170-4d6f-b177-b34715a436e0 │
│ 7 │***Zigbee Light Multifunction Mc │ efbe7be3-ab36-46eb-86e8-53ac056a1cec │
│ 8 │***Zigbee Light Multifunction Mc-(OLD) │ 87afaf3a-62ee-41fc-8359-d05b34ea84cb │
│ 9 │ Zigbee Motion Sensor Mc │ 0e362494-39f0-4f36-a57b-e62afa81fbb1 │
│ 10 │ Zigbee Multi Switch Mc │ 3e12677e-f9e9-4583-b88f-990c1e1822de │
│ 11 │ Zigbee Multi Switch Zemismart Mc │ 950d769e-5e53-4cb9-aad7-b7b6023f20d2 │
│ 12 │ Zigbee RGB-RGBW Light Mc │ 59259997-a263-431f-ad7b-ddc8d2776e98 │
│ 13 │ Zigbee Smoke Detector Mc │ a2f7ec78-14c8-492d-9965-7544b0fc3b68 │
│ 14 │ Zigbee Switch Mc │ b36f1d7a-1144-4a1d-bf8b-f7d69dee8909 │
│ 15 │ Zigbee Switch Power Mc │ badb32f7-ecd7-43d6-8963-db739afdb219 │
│ 16 │ Zigbee Temp Sensor with Thermostat Mc │ dd80873e-052c-4935-b265-e97a92aebe9d │
│ 17 │ Zigbee Temp Sensor with Thermostat Mc(OLD) │ ed2401c6-ea9a-4d5c-a4e6-5e53c190293d │
│ 18 │ Zigbee Valve Mc │ ec933073-b1aa-47ac-b886-0b4c561afcc8 │
└────┴────────────────────────────────────────────┴──────────────────────────────────────┘
I made the version package changing the name to Zigbee Light Multifunction Mc- (OLD)
I published in the shared channel and I republish in my Mariano-test channel and then I installed in my hub the version from the Mariano-test channel.
I checked with the CLI, that in the shared channel, in the Mariano-test and in the Hub it was correct with the name Zigbee Light Multifunction Mc- (OLD).
The next day @milandjurovic71, told me that the shared channel had the same Zigbee Light Multifunction Mc driver twice and the Zigbee Light Multifunction Mc- (OLD) was not there. It is the screenshot posted.
I checked with the CLI, with the “unpublish” command, the relation of all the drivers of the shared channel, and a Zigbee Light Multifunction Mc- (OLD) driver and another Zigbee Light Multifunction Mc, as I published and cheked the previous day. It is the attached relationship.
Without re-packaging, I republish the Zigbee Light Multifunction Mc- (OLD) version to the shared channel and it already appeared fine in the shared channel, webview, and CLI.
Yesterday something strange also happened with a driver zigbee Switch Mc that I modified and shared on the channel. I sent them the date of the version so that they would not test it until that date appeared in the driver of their Hub. Today they have written to me because the version did not appear.
I have republished it and will be attentive to see if it is repeated.
In this case, I cannot assure you that I was not wrong when I published it. https://community.smartthings.com/t/beta-zigbee-edge-driver-compatible-with-lidl-ecosmart-osram-smartthings-others/231689/660?u=mariano_colmenarejo
Does it happen randomly? I haven’t been able to replicate the issue with the channel invitation not refreshing the driver’s name.
When this happened, @milandjurovic71, did you try to clear the browser’s cache?
I haven’t been able to replicate this either, I’ll keep trying but regarding your doubt about publishing the driver correctly, are you using the one-line command to perform the three steps at once?
I find it simpler when I update the driver as I run one command instead of three.
@nayelyz I have cleared cache, rebooted the hub, and channel was still showing driver twice. As soon as I deleted one, both drivers disappeared. But I had to remove device, to be able to delete driver. Device was always showing driver with older date, not the updated one.
I find it more comfortable to use command by command.
Especially when I’m testing with different versions, I like to see that the driver ID and name are correct before publishing and especially installing.
When you already have 30 drivers and 6 channels running, you have to be careful what you package, publish and install. For me it is better step by step.
With the terminal memory, down arrow or up arrow, the last commands used will appear without having to type anything. Only type the number of driver or channel
