Indigo Domotics

I posted a link to a fixed version of this plugin in another thread.

https://github.com/FlyingDiver/Indigo-U ... /tag/1.0.5

Thanks for the quick response and the update!

- Maybe it's an idea to post this version into the Plugin Store?
- There is something strange going on with the version numbers and the upgrade message from Indigo.

We have version 1.03. (Installed ~ 2014)
Logical is your number 1.05 a higher number (learned at school )
But the message in Indigo is:

I'll have to talk to Matt and Jay about replacing the store version. It's not my plugin, so I can't just update the existing one.

I also have no idea why you're getting that error. The version number increment seems to be correct.

Just did some different tests: without and with power available.
Works perfect and Triggers are firing smoothly without any errors anymore!
You did a good job and it's definitely plugin store ready!
Thanks!

I'm not sure if this is the right location for this post but it is UPS related.

Currently experiencing a lot of storms (and associated power outages) so have added a UPS that had fallen into disuse to a Mac mini /Indigo server. Running Catalina.

But whereas after a 'dirty' shutdown the Mac will auto restart when power returns; after a 'clean' (UPS-initiated) shutdown, it requires a manual reboot. Obviously it will ultimately return after the daily restart schedule, but thats less than ideal.

Is there a way to overcome this (other than allowing a dirty shutdown?).

Not that I know of. I've done some searching on the topic, and never came up with a solution I thought was reliable.

Get a bigger UPS.

damn!
ha! I actually bought a generator yesterday, that should give a few more hours...

2 options:

1. in system prefs set an auto start - that is a fixed time, but you can also set it to eg 1 hours into the future in command line:
use: where the time is 1 hour into the future, run this every 5 minutes

Code: Select all

pmset schedule wakeorpoweron "09/08/20 20:00:00"

then when shut down it will try to wake up one hour later
also try acwake, womp
2. set dirty bit: shutdown -u, but that requires to have power off within minutes after successful shutdown, then when UPS power comes back it will restart

not perfect but ..

Karl

check out "man pmset" on your mac terminal

But with corona lasting another 6+ months I am not leaving the house any time soon. And we had no long power interruptions in the last year. Only a few secs
==> This is not a priority right now

Joe,

I'm also using this Plug-in, but when I crate a trigger in Indigo, the state comes back as 1000. Do you know what this value represents.

John

Eagleye wrote:

Joe,

I'm also using this Plug-in, but when I crate a trigger in Indigo, the state comes back as 1000. Do you know what this value represents.

John

Which state? This is not a value sensor, so it doesn't have a default state value.

I have done a quick and dirty upgrade to Python 3 for this for my own use, but not sure of the official status and to if I can share (and then how).

Neil

neilk wrote:

I have done a quick and dirty upgrade to Python 3 for this for my own use, but not sure of the official status and to if I can share (and then how).

Neil

I'm the most recent maintainer of this plugin, but not having an APC UPS any longer means that I have no good way of testing its action scripts so I chose to see if others wanted/needed the Python 3 upgrade before diving into it myself.

Since you have done it yourself would tell me that it's desired. Please reach out to me in a private message and we'll work something out to get your efforts into the distribution.

Marty,
I did a little more testing on this and was trying to fix one last issue when I realised @flyingdiver has already done the upgrade and the code is in GitHub, it has just never been pushed as a release. I can confirm his version works fine, but it may be good to get this pushed. Note to self: Check the Github before assuming the upgrade has not been done !
Thanks,
Neil

Yeah, I submitted a PR and the code got merged, but never released. I didn't have permissions to do that.

FlyingDiver wrote:

Yeah, I submitted a PR and the code got merged, but never released. I didn't have permissions to do that.

Not certain where you submitted your PR to, but the most recent version that I know of (0.5.2) was mine.

I'd be happy to work with anyone and everyone to get it updated for Python 3.