level functionality doesn't work anymore for klikaanklikuit dimmer

[HarryT]

Hi Willi

I use the current developer version of FHEM and since a few days, I can't change the level of my klikaanklikuit dimmer anymore. If I change the level with "set Lamp level 4" the logging just shows "Lamp level" and the level isn't changed.

So to mee it looks as if there is a bug introduced.

Can you have a look at it?

{HT}

My xmllist: (see value="level" instead of "level 1")
      <TRX_LIGHT name="LampStaande" state="level" sets="all_level all_off all_on level:slider,0,1,15 off on on-till on-for-timer" attrs="room group comment alias eventMap userReadings IODev ignore:1,0 do_not_notify:1,0 loglevel:0,1,2,3,4,5,6 event-on-change-reading event-on-update-reading event-min-interval stateFormat devStateIcon icon invertState onOffDevice toggleDevice webCmd">
         <INT key="DEF" value="AC 010A3B0C01 light"/>
         <INT key="NAME" value="LampStaande"/>
         <INT key="NR" value="82"/>
         <INT key="STATE" value="level"/>
         <INT key="TRIGGERTIME" value="2013-04-07 22:23:08"/>
         <INT key="TRX_LIGHT_deviceid" value="010A3B0C01"/>
         <INT key="TRX_LIGHT_devicelog" value="light"/>
         <INT key="TRX_LIGHT_type" value="AC"/>
         <INT key="TYPE" value="TRX_LIGHT"/>
         <INT key="IODev" value="TRX_0"/>
         <ATTR key="room" value="Licht"/>
         <ATTR key="webCmd" value="level:off"/>
         <STATE key="state" value="level" measured="2013-04-07 22:23:08"/>
      </TRX_LIGHT>

[Willi]

Hello Harry,

I have corrected this in SVN.
Is available tomorrow via update.

-- Willi

[HarryT]

Hi willi

I updated and tested, Unfortunately it contains still the same bug.

{HT}

[Willi]

Hi Willi

I use the current developer version of FHEM and since a few days, I can't change the level of my klikaanklikuit dimmer anymore. If I change the level with "set Lamp level 4" the logging just shows "Lamp level" and the level isn't changed.

Hmm. I have looked into it again:

Are you sure you have the newest update version of 46_TRX_LIGHT.pm? The version that I have changed recently is:
"# $Id: 46_TRX_LIGHT.pm 3055 2013-04-08 18:33:01Z wherzig $"

If I do a "set Lamp 4" I do not get any logging at all for default. There is no "Lamp level" in the log.

If I the logging lines in 46_TRX_LIGHT.pm 307-308 from
"
     Log 1,"TRX_LIGHT_Set lighting2 name=$name device_type=$device_type, deviceid=$deviceid command=$command" if ($TRX_LIGHT_debug == 1);
     Log 1,"TRX_LIGHT_Set lighting2 hexline=$hex_prefix$hex_command" if ($TRX_LIGHT_debug == 1);
"

to
"
     Log 1,"TRX_LIGHT_Set lighting2 name=$name device_type=$device_type, deviceid=$deviceid command=$command";
     Log 1,"TRX_LIGHT_Set lighting2 hexline=$hex_prefix$hex_command";
"

I will get the following log:

2013.04.11 21:00:05 1: TRX_LIGHT_Set lighting2 name=Lamp device_type=AC, deviceid=010A3B0C01 command=level 4
2013.04.11 21:00:05 1: TRX_LIGHT_Set lighting2 hexline=0B110000010A3B0C01020400

This looks perfectly to me.

Have you changed the firmware recently?

-- Willi

[HarryT]

Hi Willi

I use the current developer version of FHEM and since a few days, I can't change the level of my klikaanklikuit dimmer anymore. If I change the level with "set Lamp level 4" the logging just shows "Lamp level" and the level isn't changed.

Hmm. I have looked into it again:

Are you sure you have the newest update version of 46_TRX_LIGHT.pm? The version that I have changed recently is:
"# $Id: 46_TRX_LIGHT.pm 3055 2013-04-08 18:33:01Z wherzig $"

I checked again and it is identical. And I did a shutdown restart to use it.

If I do a "set Lamp 4" I do not get any logging at all for default. There is no "Lamp level" in the log.

If I the logging lines in 46_TRX_LIGHT.pm 307-308 from
"
     Log 1,"TRX_LIGHT_Set lighting2 name=$name device_type=$device_type, deviceid=$deviceid command=$command" if ($TRX_LIGHT_debug == 1);
     Log 1,"TRX_LIGHT_Set lighting2 hexline=$hex_prefix$hex_command" if ($TRX_LIGHT_debug == 1);
"

to
"
     Log 1,"TRX_LIGHT_Set lighting2 name=$name device_type=$device_type, deviceid=$deviceid command=$command";
     Log 1,"TRX_LIGHT_Set lighting2 hexline=$hex_prefix$hex_command";
"

I will get the following log:

2013.04.11 21:00:05 1: TRX_LIGHT_Set lighting2 name=Lamp device_type=AC, deviceid=010A3B0C01 command=level 4
2013.04.11 21:00:05 1: TRX_LIGHT_Set lighting2 hexline=0B110000010A3B0C01020400

This looks perfectly to me.

When I try the same:
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 name=LampStaande device_type=AC, deviceid=010A3B0C01 command=level 2
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 hexline=0B110000010A3B0C01020200

And it he logging of the device:
2013-04-11_22:46:33 LampStaande level
and this is the latest line where level is used:
2013-04-05_21:58:33 LampStaande level 0
At that date I think I updated because I was working on the PT2262 issue.

Have you changed the firmware recently?

No I am running version 64 for some time now. But I use the latest (today) development version of FHEM. Maybe.....

-- Willi

Can I provide any more info?

{HT}

[Willi]

When I try the same:
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 name=LampStaande device_type=AC, deviceid=010A3B0C01 command=level 2
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 hexline=0B110000010A3B0C01020200

This looks perfectly for "level 2". I assume that you have tested with level 2 and not with level 4 like I did.

I am still wondering why you get the level logging at all. What is your loglevel?

Just a thought:

- It could be that we look in two different issues and not just one:

  -1- logging fo FHEM for level does no longer show the level#

  -2- There is an problem with firmware 64 and level.

I would ask you to flash again the last firmware of RFXtrx433 that worked with level for sure.
I do not know what version number this is because I have no device that uses level and have never used level except on a test system without a real device.

This way we can find out if it is a firmware problem.

The other issue we have to look is why your logging is different. I have tested this with the latest version of FHEM via update. There is no logging for level.

-- Willi

[HarryT]

[quote title=Willi schrieb am Do, 11 April 2013 23:09]

When I try the same:
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 name=LampStaande device_type=AC, deviceid=010A3B0C01 command=level 2
2013.04.11 22:37:37 1: TRX_LIGHT_Set lighting2 hexline=0B110000010A3B0C01020200

This looks perfectly for "level 2". I assume that you have tested with level 2 and not with level 4 like I did.
/quote]

Right

I am still wondering why you get the level logging at all. What is your loglevel?

Just the default. Where can I find it?
But maybe we are talking about different loggins. The logging I quite was produced by
define FileLog_LampStaande FileLog ./log/%Y-%m-LampStaande.log LampStaande

Just a thought:

- It could be that we look in two different issues and not just one:

  -1- logging fo FHEM for level does no longer show the level#

It is not only the logging, But also on the GUI of the webinterface and andFHEM and the light is burning at a lower level.

-2- There is an problem with firmware 64 and level.

Hardly. I used that version for a month or so without a problem.

I would ask you to flash again the last firmware of RFXtrx433 that worked with level for sure.

I think going back the latest version of 46_light.pm (and maybe the other trx drivers) gives more chance of finding the specific problem. Is there a way I can pull older version from the svn?

The other issue we have to look is why your logging is different. I have tested this with the latest version of FHEM via update. There is no logging for level.

Maybe we are talking about different loggings??

-- Willi

{HT}

[Willi]

For SVN version look at the SVN (see also www.fhem.de):

http://fhem.svn.sourceforge.net/viewvc/fhem/trunk/fhem/FHEM/46_TRX_LIGHT.pm?view=log

Take the appropriate one.

[Willi]

I have put a new version into SVN that should solve the logging issue. However it does not change anything on the bits and bytes send to RFXtrx433.

[HarryT]

Hi Willi

Surprisingly, but this patch doesn't only solve the logging issue, but the complete issue.

The issue it self was introduced with version 3029. 2996 was the last correct one. And 3064 is correct again. (but I just tested this issue)

Hope this helps in understanding the source of the issue.

Thanks for you help/time.
{HT}