Hi All,
Should I expect to see a Device Rebirth option available somewhere? or is it limited to Node Rebirths?
Cheers, Eric
In MQTT Engine, you can see it here:
Note in order for this to appear it must be published in the DBIRTH by the Edge Node. MQTT Transmission supports it but I’m sure there are other Edge Node implementations that don’t.
I am using MQTT Transmission, but didn’t previously have much luck with the Device Control / Rebirth Tag. However, I now realise that I didn’t have write commands enabled on Engine. 
.
Using Engines Device Control / Rebirth, I can now see it rebirthing when looking at Engine’s Device Info / Birth Count and also on the Chariot client watching the DBIRTH message. But now I have found the next issue..
If I create a new tag on transmitter device, I can see the transmitter ‘Refresh Required’ on the device’s node. But when I use the Engine Device Control / Rebirth tag, the new tag doesn’t come through. Is there a difference between refresh and rebirth?
Edit: Using 4.0.25 for both Transmitter and Engine
Yes - Rebirth is not the same as Refresh. A Rebirth will send a new BIRTH with current values, but it will only contain the same metrics/tags that were in the original previous BIRTH. A Refresh does a full scan of the tag tree and will include any new tags that may have been added since the last BIRTH. We’ve had an issue in our backlog for a while to support both, but we haven’t been able to prioritize it yet.
With that being said, you could create an additional Transmitter at the Edge to publish your Transmission Control tags to Engine. This will allow you to remotely ‘click’ those controls. You could also use your own tag in your existing Transmitter with a tag change script that writes to the tag(s) you want to write to at the Edge.
Perfect, thanks for clarifying Wes!
I did try and find the difference, but couldn’t find it documented.
Yea, the plan was to monitor the transmitter tags and refresh when required. I only realised today that the device refresh wasn’t also available currently. In the backlog, was it to do a device refresh from transmitter? or from engine? or both?
Cheers,
The backlog issue as it is now is to support Edge Node level refreshes and rebirths from both the Transmission side and the Engine side. As it functions now, we support only Refreshes from the Edge and Rebirths from the Engine side. I think it makes sense to add support for Device level support for both of these as well. I’ll make a note of this.
1 Like
I hadn’t thought of this (transmitter of the Transmission tags). May look into it. I created a custom UDT that I birth to engine that does this. Of course, I do a lot of other maintenance activities using this UDT a well.