I'm trying the Roomba plugin. It needed an update and the author did (linked below)

I updated the plugin and now along with the log not appearing it is stuck in disconnected state. If I click restart I never get a notification on the UDI app like I do for all other plugins. The uptime never changes also.

If I click stop I will bet the lower right Nodeserver stopped successfully. but uptime and and status stays Disconnected. If I click start I get Plugin Start: Already running.

I tried deleting and reinstalling the plugin and behavior stays the same. So I cannot get a log (I even SSH'd in there is no logs folder after re-installing the plugin) but it doesn't really even try to start?

Thoughts? Do I have some internal state stuck?

Very rarely, or if PG3x crashes it can fail to kill running plug-ins. From your description it sounds like that's what has happened here. There is a copy of the Roomba plug-in running but PG3x thinks it has stopped that copy. Only one copy of a plug-in for a slot can be running so when you try to start a second copy, it can't and nothing happens (other than the message that it is already running).

Depending on your comfort level with FreeBSD command line, you can either ssh in and kill the running copy or simply reboot the eisy/Polisy. Once that first copy is stopped/killed, you should be able to start it again from PG3x.

Yeah I'm comfortable with CLI (spend most my day on Unix/Linux CLI). there wasn't a python process.

Turns out others found the issue just after and the author released an update that fixed the issue with that plugin. I was just surppised that it didnt' log anything, maybe I needed to find a more central log if the plugin had errors and coudln't start.

Anyway it's fixed now, it just doesn't appear to work with my specific roomba which is sad.

14 hours ago, brockp said:

Yeah I'm comfortable with CLI (spend most my day on Unix/Linux CLI). there wasn't a python process.

Turns out others found the issue just after and the author released an update that fixed the issue with that plugin. I was just surppised that it didnt' log anything, maybe I needed to find a more central log if the plugin had errors and coudln't start.

PG3x has a log file that you can access from the main PG3x menu (just called 'Log'). This log will show any errors when starting a plug-in that occur before the plug-in actually starts.