jbrodriguez

Hey there, that's certainly a fair request. I'm unable to work on the plugin in the short term, but I'll include this feature in the next minor release.

I did ! A small form factor 1650, and it's working just fine !

Just as a test, did you try setting SSL to no in settings and restart the unbalance plugin ? Does that work ?

Hey, how do you suggest to do that ? What criteria to choose only those 5 instead of only 6 or 3, or 7 ?? About rsync, I don't have its command line in my head, but you can always man rsync on the web browser

v2019.10.26 (5.6.3) is available ! - Support 6.8.x - Add missing isNumber function - Upgrade some libraries - Switch to yarn

I'll look into it in upcoming releases

Hi, I'm able to connect to my server using http, so it should work. Can you try this - Go to Settings > Open Source Libraries - After the react native credits, you’ll find a debug button, hit it once (counter should read 1) - Now try connecting manually via http (you should see a ‘debug initialized ‘ message at the bottom) - It should go back to the main screen - Go to manual add again - It should be displaying some debug message - Take a screenshot and send it over (pm if prefer)

v4.16.0 is available on Apple and Google Stores ! - Initial 6.8.x support Let me know if you find any issues P.D.: still can't figure out the temperature unit issue, but I think it's on the plugin side

I can't put a finger on it.. with your data and preferences set to Farenheit, it returns 73 degrees. What Unraid version are you running (to have an idea when this may have started) and what are your temperature settings ?

Thanks ! I'll work with that.

v4.15.2 is available on Apple App Store ! It fixes an issue that was preventing the execution of some commands on the server. ***NOTE: this completes the fix that was made previously available for Android.

Hi, I'd appreciate your help in fixing this. Can you run /usr/bin/sensors -A on your command line and post back the results (pm if you prefer) ?

I know what the issue is, it's a permissions issue. The plugin creates a log file on /boot/logs/unbalance.log and also writes a config file at /boot/config/unbalance.{conf,cfg} /boot and /boot logs have root:root ownership. By default, the plugin settings page runs the plugin as the nobody user. You can change the user you want unbalance to run as, but you can't choose root (this was a design decision I made) So when run as nobody, unbalance fails to create the log file at /boot/logs and exits. That's why it works when you run it from the command line: you're running it as root. I figure that the new user system in. 6.8.x enforces some permissions, so access to this folder is not allowed for a user that has less privileges than root (nobody in this case). I have to think how to solve this, but for the time being, the workaround is the workaround Some ideas to fix it: - allow unbalance to run as root (from the plugin settings page) - wip If anyone has ideas on how to fix this, I'd be glad to hear them 👍

v4.15.2 is available on Google Play Store ! It fixes an issue that was preventing the execution of some commands on the server. This should fix it ! **** Note that this affects iOS too, but Apple Store is throwing a fit today (actually they have a scheduled maintenance of about 8 hours 😮), so it'll become available for iOS soon.

Well, it's a release candidate, so there may still be changes about (it has happened in the past), that's why I generally support only stable releases. In any case, I'm looking to take a stab at this tomorrow.