apostolakisl

yes, updated to that from _5 I'll know after sunset tonight for sure if it is fixed.

Did some bells and whistles on the plugin. After you initiate a blind position change, the plugin will poll every 10 seconds until the target is met or it times out at 3 minutes. So it won't real time track the status of your moving blind, but you won't have to wait up to a whole minute for the regular polling. Be aware, if you change the blind position using something other than IoX, it will still poll every 60 seconds (like the Levolor phone app or Alexa via the Levolor Alexa skill). Side note re Alexa, you can expose the IoX Levolor node to Alexa and let Alexa control the blinds using IoX as the path or you can use the Levolor skill. Google Home should be the same. If you choose the IoX node, then it will poll every 10 seconds until target met. I also added different ways to view the blind status. You can set UD mobile to display the one that suits your desire. I find that using the UD mobile slider widget is the most practical control interface, unless you never use a mid position. The com between the blinds and the hub can be flaky. Commands consistently go through, but the blinds don't always manage to update the hub with their current status. Nothing I can do about that. The Levolor phone app will also fail to show the correct position. I have just one hub in my house and positioned it so none of the blinds are more than 40 feet away, yet the ones that are more than 20 tend to have missed info or delayed responses to commands. Currently, if you have two hubs, you would need to install the node server twice (use two slots). I would like to change that, but since I only have one hub I'm not going to try to guess if it works. If you have two or more hubs and would like to work with me, I'd be happy to give it a go. Field Meaning Display Status (ST) Binary state, 0–50% = Open, 51–100% = Closed Position (GV4) Actual blind position (0 and 100 sub word open/closed) 0–100%, exact reported position Blind State (GV5) Human-readable description of position 0% = Open, 1–99% = Partially Open, 100% = Closed

After one day cycle on the latest software released yesterday, it looks like the sunset issue is fixed. My programs ran last night at sunset (which proves nothing by itself because fresh off a reboot, the sunset problem didn't exist), but now today the "next run time" is correctly listed for tonight. This is where it looks like the fix worked. Prior to the update, after running the first sunset it would then list the next run time ~48 hours later.

Yes, I have a ticket running for a few days now about this.

The update UD posted yesterday did not fix the issue for me. After my programs ran at sunset last night and then sunrise this am, they are listed to run next as sunset . . .tomorrow (should be tonight).

Yes, rebooting had the same affect as resaving programs. I updated to the latest firmware drop they did earlier today that Michel says fixes it. We'll know tomorrow after my sunset programs cycle past their shut down trigger.

All my sunset programs are also messed up. They all listing the next run time for sunset tomorrow night, instead of tonight. I made non-change updates to the programs (just hit the "update" button without an actual change so the program would then be savable), then saved them all and now they list the correct run time at sunset tonight. I suspect tomorrow I will need to do that again until such time as the firmware is fixed. Also, programs I have that run at midnight are running twice. Once at midnight and then a second time a few seconds later. I created a test program that does nothing but send me an email at midnight with a timestamp and it also ran double. So no chance of any hidden calls to it or anything, it is a brand new program with nothing else triggering it, just midnight on the clock. I tried changing the midnight program run time to a couple seconds after midnight to see if the issue is running precisely at midnight.

The dark theme could work better if alternate rows were slightly lighter.

I needed to sync a few times today as I'm working on a plugin. After one of these syncs my favorites folder was mostly deleted and many nodes on home page went missing too. I restored a backup and sync'd again and things are OK now. In this thread: https://forum.universal-devices.com/topic/46514-ud-mobile-stopped-working-with-1-of-2-isy-after-sync/ You told me to switch to legacy sync mode. Is there any reason for me to continue using legacy?

No, I started a ticket EDIT: I guess the reboot did fix it, but it took a good 10 minutes after the reboot. Maybe it had to finish the polling of all insteon devices.

But I think eisy is doing fine, it looks like the eisy ui is the only thing not seeing the plm. The java console shows plm connected, and in fact, it is connected. Eisy is able to send/receive instoen commands . . . my lights are all working.

I just went to the eisy ui insteon page. It says no plm connected, but of course there is, and it is working according to the java console (and because my insteon stuff is working). I clicked to turn on insteon support (which I guess means that this enables management of Insteon devices from the eisy ui), it says it will need to reboot, I say Apply, it immediately replies "error, no api found". Also, how do we change the dark mode on eisy ui to something else. I don't find this dark mode to be very easy on the eyes.

I have a Polisy on 6.0.5. My memory may be failing me, but I am pretty sure that upgrade was from the admin console, not ssh. I have not ventured into moving my Polisy to 6.1.x, but I imagine I will be doing that shortly.

It sounds to me like anyone worried about eisy ui not supporting their system should keep and old computer handy with java on it and just never update it. Park it next to your isy994i or polisy (if you choose not to ssh upgrade it) and keep it off the internet. Or keep a bootable image of your current computer and boot from that when you need the old java to work.

What thermostat? I am going to speculate that after you put in the temp value, you aren't hitting the button to set the value.