MAXLAN_Parse: Command was discarded

[emnagel]

I am getting the discarded lines in the log file from my MAX cube. And it also seems the weekprofile is not working recently.

Code Auswählen Erweitern

ml device opened
2013.11.23 13:03:27 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:27 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:28 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:28 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:28 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:28 2: MAXLAN_Parse: Command was discarded
2013.11.23 13:03:28 2: MAXLAN_Parse: Command was discarded

The code in the configuration file looks like:

Code Auswählen Erweitern

#
## -- Week profielen --
#
set wt_badkamer weekProfile Mon 14,06:30,23,8:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Tue 14,06:30,23,8:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Wed 14,06:30,23,8:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Thu 14,06:30,23,8:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Fri 14,06:30,23,8:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Sat 14,06:45,23,9:00,14,18:30,22,21:00,14
set wt_badkamer weekProfile Sun 14,06:45,23,9:00,14,18:30,22,21:00,14

[pet22]

Hi,

just try a one-liner, it simply aborbs less credits:

Code Auswählen Erweitern

set wt_badkamer weekProfile Mon 14,06:30,23,8:00,14,18:30,22,21:00,14 Tue 14,06:30,23,8:00,14,18:30,22,21:00,14 Wed 14,06:30,23,8:00,14,18:30,22,21:00,14 Thu 14,06:30,23,8:00,14,18:30,22,21:00,14 Fri 14,06:30,23,8:00,14,18:30,22,21:00,14 Sat 14,06:45,23,9:00,14,18:30,22,21:00,14 Sun 14,06:45,23,9:00,14,18:30,22,21:00,14

HIH

Pet22

[emnagel]

Thx Pey, but that is not the issue.

logs still tells me discarded even after update code and reboot today.

Code Auswählen Erweitern

2013.11.24 19:17:08 3: ml device opened
2013.11.24 19:17:09 2: MAXLAN_Parse: Command was discarded

Line of config code is simple

Code Auswählen Erweitern

set wt_badkamer weekProfile Mon 14,06:30,23,8:00,14,18:30,22,21:00,14

[pet22]

ugh -- don't really understand what do you mean with 'reboot'

Let me do a wild guess: once you updated FHEM you did a reboot of your FritzBox/ NAS/ Raspberry/ etc. or a restart of FHEM. However, unless you un-power the Cube for a few mins in addition, the last no. of credits are stored in the Cube memory. So the misery is the same as before.
Also a few more details about your configuration would be helpful: e.g. no. of WT/ HTs, etc.

Kind regards

Pet22

[emnagel]

I did both.

1) I powered down the Cube and checked for new firmware. No update and running fine under the default software
2) I updated FHEM and did a shutdown reboot.

No results. Just setting the desired tempature manual works fine.

[pet22]

Sorry - running out of ideas. Maybe you need to dump your config file and Matthias Gehre or John are able to support you further.

Thx

Pet22

[John]

Hi emnagel

I think fhem.cfg is not an appropriate place for these commands
since the initialization at the time of execution is not yet completed.

Moreover, it is not necessary to perform the commands every time you start FHEM.

It is sufficient to manually perform this commands, since the information is stored in the thermostats.

John

[emnagel]

Thx John for your response. But where to store this type of information then if fhem.cfg is not the correct place?

Furthermore by manually you mean via the default MAX Cube portal interface? If yes I do not like this idea, because I am looking for a solution to do configuration at one place / tool and not to many places even if it is a one time of exercise.

cheers, Erik