Problems with latest release (10.2.3.26)

128 views
Skip to first unread message

Jedi Tek'Unum

unread,
Apr 18, 2019, 1:37:59 PM4/18/19
to Loxone English
Nothing like a new release breaking stuff that used to work. Beware the latest update.

1 - Pulse for Dusk doesn't always happen. Somewhere between 10-20% of days it doesn't pulse.

2 - UDP Virtual Inputs randomly ignore packets. Maybe 5% of the time. My button hardware/software is logging button actions and UDP packets being sent but not doing anything at Loxone. When it gets in this state they are repeatedly ignored for some random amount of time and then before I can investigate/reboot it clears up. Not a problem with my network (have a separate dumb switch connecting the two; unlikely to coincidently start acting up at the same time as new software is installed).


Jan De Bock

unread,
Apr 19, 2019, 1:05:37 AM4/19/19
to Loxone English
I have observed some similar issues. Sometimes the autoshading is not opening the screens as expected. I have several windows in separate rooms but with the same orientation. Sometimes some screens don't open while others do. And yes, I know that a manual operation stops automatic shading, but this is not the case here. Any similar experiences? I am not 100% sure if this started with 10.2 or shortly before this.

Steven Van Gysel

unread,
Apr 19, 2019, 4:00:22 AM4/19/19
to Jan De Bock, Loxone English
I've the same feeling, my autoshading is indeed not working as I'm expecting. But I had that feeling already last summer but not have the time to investigate it.

Op vr 19 apr. 2019 om 07:05 schreef 'Jan De Bock' via Loxone English <loxone-...@googlegroups.com>:
I have observed some similar issues. Sometimes the autoshading is not opening the screens as expected. I have several windows in separate rooms but with the same orientation. Sometimes some screens don't open while others do. And yes, I know that a manual operation stops automatic shading, but this is not the case here. Any similar experiences?  I am not 100% sure if this started with 10.2 or shortly before this.

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/cec5bfe1-ed7a-43f6-8c01-a58c7838577c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Keith Emerson

unread,
Apr 19, 2019, 3:13:30 PM4/19/19
to Loxone English
Having similar problems but pulse for dawn in my case? I haven't looked into it but hopefully Loxone wil fix it ?

Rob_in

unread,
Apr 20, 2019, 2:53:32 AM4/20/19
to Loxone English
I've just had to mess about with the Modbus extension as some sensors weren't being recorded. Seems OK after tweaking polling period but hardly reassuring.

I wouldn't have updated but that message on the app bugging you about the update was getting annoying :(

Jedi Tek'Unum

unread,
Jun 20, 2019, 2:18:18 PM6/20/19
to Loxone English
Just to update my own observations. Since the original post I removed all my dusk pulses and changed the logic to use Daylight which solved the problem.
Reply all
Reply to author
Forward
0 new messages