Decoding of unsupported ARC codes (Lighting4)

Begonnen von oliv06, 05 Januar 2013, 00:00:41

Vorheriges Thema - Nächstes Thema

HarryT

Zitat von: Willi schrieb am Fr, 05 April 2013 20:59For the web interface: How did you do the set exactly? Doing the set with 1 or with on?

I tried all the 4 ways available in the web interface.

ZitatI am not sure how the webinterface does this. Maybe we need the state to set on or off?

Could you do a list DEVICENAME after the set?
A few exapmpe outputs would be nice.

Regards

Willi


list PIR1 before setting:

Internals:
   DEF        PT2262 13030010100 light 0:off,1:on
   IODev      TRX_0
   LASTInputDev TRX_0
   MSGCNT     1
   NAME       PIR1
   NR         169
   STATE      Beweging
   TRIGGERTIME 2013-04-05 21:02:21
   TRX_0_MSGCNT 1
   TRX_0_RAWMSG 09130000710441015e60
   TRX_0_TIME 2013-04-05 21:02:21
   TRX_LIGHT_commandcodes 0:off,1:on
   TRX_LIGHT_deviceid 13030010100
   TRX_LIGHT_devicelog light
   TRX_LIGHT_type PT2262
   TYPE       TRX_LIGHT
   Readings:
     2013-04-05 21:02:21   light           on
     2013-04-05 21:02:21   state           on
Attributes:
   eventMap   off:Stil on:Beweging
   room       Aanwezig


list PIR1 after the setting:

Internals:
   DEF        PT2262 13030010100 light 0:off,1:on
   IODev      TRX_0
   LASTInputDev TRX_0
   MSGCNT     1
   NAME       PIR1
   NR         169
   STATE      1
   TRIGGERTIME 2013-04-05 21:05:11
   TRX_0_MSGCNT 1
   TRX_0_RAWMSG 09130000710441015e60
   TRX_0_TIME 2013-04-05 21:02:21
   TRX_LIGHT_commandcodes 0:off,1:on
   TRX_LIGHT_deviceid 13030010100
   TRX_LIGHT_devicelog light
   TRX_LIGHT_type PT2262
   TYPE       TRX_LIGHT
   Readings:
     2013-04-05 21:02:21   light           on
     2013-04-05 21:05:11   state           1
Attributes:
   eventMap   off:Stil on:Beweging
   room       Aanwezig

The difference is "state".

Can I help more?

{HT}
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Could you try to change the lines 384 from
"
  $hash->{CHANGED}[0] = $command;
  $hash->{STATE} = $command;
  $hash->{READINGS}{state}{TIME} = $tn;
  $hash->{READINGS}{state}{VAL} = $command;
"

to

"
  $hash->{CHANGED}[0] = $a[1];
  $hash->{STATE} = $a[1];
  $hash->{READINGS}{state}{TIME} = $tn;
  $hash->{READINGS}{state}{VAL} = $a[1];
"

and try a "set PIR1 on"

The state should be "on" after this and the webinterface should look better?

-- Willi
FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

ext23

ZitatMy understanding was that PT2262 just supports Tristate values 0,1,2 but not 3.
--> That's right, PT2262/HX2262 can only handle TreState.

I got also this values sometimes (normally if I release a Button of my PT2262 RC...)

2013-04-03_23:04:22 TRX_PT2262 010101111133
2013-04-03_23:04:23 TRX_PT2262 hex: 11155f
2013-04-03_23:04:23 TRX_PT2262 bin: 000100010001010101011111
2013-04-03_23:04:23 TRX_PT2262 codes: up middle up middle up middle middle middle middle middle down down

But eveything is ok as we have only "three states":
00 = 0 = up = GND
01 = 1 = middle = float
11 = 3 = down = VCC
10 = 2 = not allowed/not used

BR
Daniel
HM, KNX, FS20, 1-Wire, PanStamp, AVR-NET-IO, EM1000EM, PCA301, EC3000, HM-LAN, CUL868, RFXtrx433, LGW, DMX @Ubuntu-Server (Hauptsystem) & Raspberry Pi (Satellit)

HarryT

FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Zitat von: HarryT schrieb am Fr, 05 April 2013 22:03That is just perfect.

Thanks.

{HT}

Ok. Fixes for the state are now in SVN and should be in update tomorrow.

Also I have reduced the number of lines logged for each set. There is now just a single line for each set in the log. We may remove this later.

-- Willi
FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

HarryT

[quote title=HarryT schrieb am Fr, 05 April 2013 15:45]
Zitat von: Willi schrieb am Di, 02 April 2013 12:55
Zitat von: HarryT schrieb am Mo, 01 April 2013 22:37Keep us informed it seems I have also problems with set on my cheap pir sensors. BTW I guess the PT2622 thing should work for cheap smokedetectors (10 euro) too.
{HT}
I would be also very interested to know which devices work with the PT2262 code that would not work with other protocols supported by RFXtrx433.


Surprise! I got my new Chinees PIR sensors today. They looked 100% identical and are bought from the same supplier. But they have another print and have a smaller SC2262 chip inside. The lucky news is they work too with your PT2262 solution.

I now have MW-HW3 and XY-HW8 sensors according to the print.

BTW when using: you need to select 3,3 Mhz (be careful to buy a device which supports 3,3 Mhz). Further leave the 9e place of the settings open and remove the 9e digit from the sequence reported by the PT2262 module. That should be enough to get it to work. At least for me.  
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Zitat von: HarryT schrieb am Sa, 06 April 2013 18:34Surprise! I got my new Chinees PIR sensors today. They looked 100% identical and are bought from the same supplier. But they have another print and have a smaller SC2262 chip inside. The lucky news is they work too with your PT2262 solution.
 
Very good news. Do you have a pointer (URL) to the items you bought? Or is it the same URL you have already posted?

-- Willi
FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

HarryT

Zitat von: Willi schrieb am Sa, 06 April 2013 21:25Very good news. Do you have a pointer (URL) to the items you bought? Or is it the same URL you have already posted?

-- Willi

Yes it is the same URL.

{HT}
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

HarryT

Zitat von: HarryT schrieb am Sa, 06 April 2013 18:34Further leave the 9e place of the settings open and remove the 9e digit from the sequence reported by the PT2262 module.  
 

:-( for my latest PIR sensors it is position 12. So you have to play with the last 4 jumpers to find the correct one which have to be left out. I found position 9 and 12 as the correct place for my types of sensors.

{HT}
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Zitat von: HarryT schrieb am So, 07 April 2013 19:21
Zitat von: HarryT schrieb am Sa, 06 April 2013 18:34Further leave the 9e place of the settings open and remove the 9e digit from the sequence reported by the PT2262 module.  
 

:-( for my latest PIR sensors it is position 12. So you have to play with the last 4 jumpers to find the correct one which have to be left out. I found position 9 and 12 as the correct place for my types of sensors.

{HT}
How do the sensors work? Is there any Keepalive signal (signal when there is no movement) or just a signal when PIR reports alarm. How many packets are send when alarm is reported?

I would be very interested to see parts of a log of one of the PIR sensors.

FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

HarryT

Zitat von: Willi schrieb am So, 07 April 2013 19:32
How do the sensors work? Is there any Keepalive signal (signal when there is no movement) or just a signal when PIR reports alarm. How many packets are send when alarm is reported?

I would be very interested to see parts of a log of one of the PIR sensors.

[/quote]

They just detect movement. There is no keepalive I arrange this with a watchdog definition.

How can I found out the number of packets send? Just with the rfxmngr?

A small part of a logfile:
2013-04-01_01:01:27 PIR1 light: Beweging
2013-04-01_01:01:27 PIR1 Beweging
2013-04-01_01:01:48 PIR1 light: Beweging
2013-04-01_01:01:48 PIR1 Beweging
2013-04-01_09:26:32 PIR1 light: Beweging
2013-04-01_09:26:32 PIR1 Beweging
2013-04-01_09:37:41 PIR1 light: Beweging
2013-04-01_09:37:41 PIR1 Beweging
2013-04-01_09:38:40 PIR1 light: Beweging
2013-04-01_09:38:40 PIR1 Beweging
2013-04-01_09:38:53 PIR1 light: Beweging
2013-04-01_09:38:53 PIR1 Beweging
2013-04-01_09:39:12 PIR1 light: Beweging
2013-04-01_09:39:12 PIR1 Beweging
2013-04-01_09:39:24 PIR1 light: Beweging
2013-04-01_09:39:24 PIR1 Beweging
2013-04-01_09:39:36 PIR1 light: Beweging
2013-04-01_09:39:36 PIR1 Beweging
2013-04-01_09:39:49 PIR1 light: Beweging
2013-04-01_09:39:49 PIR1 Beweging
2013-04-01_09:40:52 PIR1 light: Beweging
2013-04-01_09:40:52 PIR1 Beweging

{HT}
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Zitat von: HarryT schrieb am So, 07 April 2013 21:49
Zitat von: Willi schrieb am So, 07 April 2013 19:32
How do the sensors work? Is there any Keepalive signal (signal when there is no movement) or just a signal when PIR reports alarm. How many packets are send when alarm is reported?

I would be very interested to see parts of a log of one of the PIR sensors.


They just detect movement. There is no keepalive I arrange this with a watchdog definition.

How can I found out the number of packets send? Just with the rfxmngr?
{HT}[/quote]

Thanks for the information.

Yes, the only simple way would be using RFXmngr.

On my FHEM drivers I do discard multiple packets if they occur within 2 seconds. Thus you will not see multiple packets. I do this because many Oregon sensors and also X10 send multiple packets. I would be bad if you will see them as separate notify on FHEM.

-- Willi
FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

HarryT

Zitat von: Willi schrieb am So, 07 April 2013 22:06
Zitat von: HarryT schrieb am So, 07 April 2013 21:49How can I found out the number of packets send? Just with the rfxmngr?
{HT}

Thanks for the information.

Yes, the only simple way would be using RFXmngr.

-- Willi

They only send 1 packet for a movement.

{HT}
FHEM 6.3 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz) and Raspberry Pi4 for testing
German reading skills are good.

Willi

Zitat von: oliv06 schrieb am Mi, 03 April 2013 13:23The WD18 transmits a keep alive code with battery and alarm status.

I have ordered two WD18 and have installed one of these today.

The WD18 shows up as a X10 security remote (KR18).

When I press the test button, I get messages telling me alert and also battery status ok.
After this the device seem not to send directly a normal status.

After 1 hour I got the normal status and the battery status was low.

How does it work for you?

-- Willi
FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

oliv06

Zitat von: Willi schrieb am Mo, 08 April 2013 21:21
Zitat von: oliv06 schrieb am Mi, 03 April 2013 13:23The WD18 transmits a keep alive code with battery and alarm status.

I have ordered two WD18 and have installed one of these today.

The WD18 shows up as a X10 security remote (KR18).

When I press the test button, I get messages telling me alert and also battery status ok.
After this the device seem not to send directly a normal status.

After 1 hour I got the normal status and the battery status was low.

How does it work for you?

-- Willi
I have to check this evening. By the way battery status has always been low with my battery. I did not change it yet, and WD18 beeps regularly to complain...