[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

@dlandon I think I've discovered a bug with the plugin. I'll give details below. Let me know if I should report it on GitHub and I will.

 

I am running UD 2019.06.18 and unRAID 6.7.0.

 

Steps:

• Mount a partition in the drive, but change the name of the mount (by clicking on the name, changing it, and pressing enter)
• Create a script for the mounted partition or drive
• Save the script
• Edit the script (which now appears as a code icon)
• Make some change and save it
• Observe that the entire configuration appears to be wiped out, and is gone from the \flash\config\plugins\unassigned.devices\unassigned.devices.cfg file as well.

Let me know if you need more details to reproduce this.

 

EDIT: It looks like it's even simpler to reproduce than I initially thought. I am updating the steps. You do not need to make the script on the mounted partition. Editing a script that corresponds with any renamed partition is apparently enough to cause this behavior.

 

 

 

[New notification providers: Join & Telegram]

@Sn3akyP3t3 I've also decided to wait until 6.7 is stable and released.

[New notification providers: Join & Telegram]

@piratx Unfortunately, while my fix above does cause Telegram to show up in the list of providers for notifications, I don't actually get any notifications. I'm not sure what's wrong.

[New notification providers: Join & Telegram]

I realize this is an old post, but this is the first Google result for "unRAID Telegram", and I found @Bokonon's post above remarkably helpful, and I'd like to contribute a bit more. As noted above, upon restart, the changes made to NotificationAgents.xml are erased. To get around that, we can use a brittle, but functioning shell script:

# Rename current NotificationAgents.xml.
mv /usr/local/emhttp/webGui/include/NotificationAgents.xml /usr/local/emhttp/webGui/include/NotificationAgents.old

# Insert Telegram chunk and redirect out to new NotificationAgents.xml file.

sed '/<\/Agents>/{ 
    r /boot/customAgents/telegram.xml
    a \</Agents>
    d 
}' /usr/local/emhttp/webGui/include/NotificationAgents.old > /usr/local/emhttp/webGui/include/NotificationAgents.xml

Instructions:

• Add the above script to the bottom of your /boot/config/go file.
• Create a directory called "customAgents" in the /boot folder (flash drive).
• Create a file in customAgents called "telegram.xml" and put the contents of @Bokonon's post into that new file.

Then, upon restart, the Telegram agent xml stuff should get shoved into the NotificationAgents.xml. It's not the best solution, but it does work for now.