wmcneil

UD asked me to upgrade packages and try again. I did so and then tested with three users defined (user 2 and 1, as well as the default user 0 which is reserved for manual turns of the deadbolt) Everything seems to be working correctly now. These are the updates that were applied: IoX 6.0.3_3 -> 6.0.4_1 UDX 4.2.0 -> 4.2.0_2 PG3x 3.4.6 -> 3.4.9

I have opened a ticket. Michel responded and reported that myself and another user reported the problem. UD is investigating root cause.

Yes, the update to 6.0.3 happens on any reboot, without having pressed the update button. More info about that here: https://forum.universal-devices.com/topic/46113-reboot-automagically-causes-update-to-iox-603_3/#findComment-400793 There are additional upgrades available(to UDX 4.2.0, PG3x 3.4.6, and easyui 0.8.5), I have applied them, and the problem with my kwikset deadbolt user number reporting remains.

Thanks, yes, I have now fixed the version number in my post.

I have an eisy running IoX 6.0.3_3, and the zmatter dongle. I have a kwikset zwave 620 deadbolt. The deadbolt has been in my zwave network for over 1 year. The following behavior has started recently: When the deadbolt is unlocked by a human entering any valid user code on the keypad, the User Number reported in the Access Control Alarm entry in the AC is a 10-digit number. It is a constant value, regardless of which user code is entered. Previously, the User Number would be the correct user number corresponding to the code that was entered. Since the 620 supports only 250 users, a 10-digit number should not be possible. Before I start trying to chase this further, I thought I would see If anyone else has seen this behavior. If so, please post. Thanks.

@mmb, I also had the same problem with Firefox. Completely clearing the cache solved the problem for me.

@bmercier, since your statement above that "There are no cases where updates would be done automatically" is not correct (per Michel's response above), if possible, please remove the Solution tag from your post further above.

Explanation from Michel in response to the ticket I opened as to why 6.0.3 installs automatically upon reboot (without update button having been pressed): "...the reason is that 6.0.0 had an issue with libxml-2 library. So, once the packages were upgraded, it would no longer start and thus would not even give you the ability to login to the Admin Console to do the upgrade. Since we removed the capability for upgrade using the front power button (it had its own issues), our only choice was to reinstall it upon reboot. "

I have opened a ticket. Will post back with update once it is resolved.

It seems likely that the update to 6.0.3 is happening "automagically" on reboot without the update button having been pressed. If anyone else has experienced this, please post and let me know, so I can be absolutely certain before I open a ticket.

Hmmm, this happened on two different boxes, an eisy, and a polisy. In both cases, prior to the reboot, they were running IoX 6.0.0_4 . I could see that maybe I accidentally clicked on update on one of the boxes without realizing it, but seems less likely that it happened on two different boxes. The only package that actually "automagically" updated was IoX, so if your theory is correct, I would have had to accidentally done the update on both boxes before about 12/1, otherwise other packages would have updated too....Anyway, thanks for the pointer, good to know.

Rebooting either an eisy or a polisy (yes, I have both) that is running IOX 6.0.0_4 causes an update to 6.0.3_3 , WITHOUT any update being requested. Why is the update occurring when no update was requested? After the reboot and automagic update to IOX 6.0.3_3, eisy-ui / settings / system shows the following additional updates now available: UDX available update from 4.0.4 to 4.2.0 PG3X available update from 3.3.23 to 3.4.6 eisy-ui available update from 0.7.2 to 0.8.5 There is no release announcement for IOX 6.0.3 . Will there no longer be release announcements?, or was the one for 6.0.3 an accidental "miss"?

I was able to update my polisy to IoX 6 without any issue. It does take a while for the update to complete, maybe 15ish minutes.

So if I change local connection settings to use port 8080 and the "IoX" credentials (instead of the ISY Portal credentials), the problem goes away. @Javi , I assume UD Mobile will eventually fix this and support ISY Portal credentials on port 80, since not doing so would make UD Mobile inconsistent with all the other interfaces?

In UD Mobile (android, version 1.4.6) when I attempt to access Settings / Plugins I am getting this error message: "could not get pg3 auth Invalid Credential. Please check username and password. 401" This is an eisy running IoX 6.0.0_4 and eisyui 0.7.2 UD Mobile Local Connection Settings: Local IP Address: http://Numeric_IP_address Local Port: 80 Local Username: ISY Portal Username Local Password: ISY Portal Password