Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cartelectronic TIC PULSES 433 V2 module support #67823

Closed
Chilgl0rd opened this issue Mar 7, 2022 · 41 comments · Fixed by #74146
Closed

Cartelectronic TIC PULSES 433 V2 module support #67823

Chilgl0rd opened this issue Mar 7, 2022 · 41 comments · Fixed by #74146

Comments

@Chilgl0rd
Copy link

The problem

The last version solve the RFXCom crash catching the informations but is not working properly.

The main packet is
Packettype = Cartelectronic
subtype = TIC
Sequence nbr = 33
ID = 09B95505C7
Contract/Price= 23
Counter1 = 00C08E7A decimal:12619386
Counter2 = 01C9DF7D decimal:30007165
No change price time warning
TeleInfo = Present
Apparent Power= 03DE decimal:990
Signal level = 5 -80dBm
Battery = OK

with
Counter1 : total usage in Watt (day hours)
Counter2 : total usage in Watt (night hours)
Apparent Power : instant usage in Watt
TeleInfo = Present : link status with the energy meter (Present = receiving data from energy meter)
Battery : module battery level

Counters are not updated and "Apparent Power" and "TeleInfo" are not created

157080382-3c79ff77-72cf-4378-a774-db48106e91cf

Thanks for your support
Chilglord

What version of Home Assistant Core has the issue?

core-2022.3.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

rfxtrx

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@elupus
Copy link
Contributor

elupus commented Mar 8, 2022

Thanks. We need to add support for this in underlying lib. Will try to look at it.

@probot-home-assistant
Copy link

rfxtrx documentation
rfxtrx source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @Danielhiversen, @RobBie1221, mind taking a look at this issue as it has been labeled with an integration (rfxtrx) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@Chilgl0rd
Copy link
Author

Hello @Danielhiversen @RobBie1221 @elupus can I help testing anything ?

@GrinGrin
Copy link

GrinGrin commented Apr 22, 2022

Hi all,
I've previously opened an issue (#56237) for the same device and at that time the support was not yet available in pyRFXtrx lib.

Saw yesterday this issue opened after I updated to 2022.4.6, I then give it another try and connected it again to check if my HASS core setup can view a new device...

First message popped up:

2022-04-22 20:56:42 DEBUG (Thread-3) [RFXtrx] Recv: 0x15 0x60 0x01 0xa2 0x09 0xb9 0x55 0x05 0xc7 0x23 0x00 0xf4 0xf0 0x21 0x02 0x21 0xe3 0x72 0x04 0xc4 0x02 0x79
2022-04-22 20:46:22 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 96, 'sub_type': 1, 'type_string': 'CARTELECTRONIC_TIC', 'id_string': '9b95505c7', 'data': '1560015809b95505c72300f4f0210221e25205000269', 'values': {'Battery numeric': 2, 'Rssi numeric': 5}}

But as the values seems not complete (only battery and Rssi, missing counters and other informations) like @Chilgl0rd , I checked batteries and changed them as they were a bit low...

Few minutes later, I saw 2 "CARTELECTRONIC_*" devices, the "ENCODER" one and a the "TIC" one:

2022-04-22 21:33:15 DEBUG (Thread-3) [RFXtrx] Recv: 0x11 0x60 0x02 0xb7 0x0d 0x47 0x02 0xeb 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x69
2022-04-22 21:33:15 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 96, 'sub_type': 2, 'type_string': 'CARTELECTRONIC_ENCODER', 'id_string': '0d4702eb', 'data': '116002b70d4702eb00000000000000000069', 'values': {'Counter value': 0, 'Count': 0, 'Battery numeric': 9, 'Rssi numeric': 6}}
2022-04-22 21:33:25 DEBUG (Thread-3) [RFXtrx] Recv: 0x15 0x60 0x01 0xb8 0x09 0xb9 0x55 0x05 0xc7 0x23 0x00 0xf4 0xf0 0x21 0x02 0x21 0xe7 0x60 0x04 0x60 0x02 0x69
2022-04-22 21:33:25 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 96, 'sub_type': 1, 'type_string': 'CARTELECTRONIC_TIC', 'id_string': '9b95505c7', 'data': '156001b809b95505c72300f4f0210221e76004600269', 'values': {'Battery numeric': 0, 'Rssi numeric': 6}}

At first I though there was another device like mine nearby, I then removed batteries few minutes to check if it still recieve messages (that was not the case) but I remembered that this device has 2 "personalities":

  • a TIC modem for french energy meters
  • an ENCODER for pulse meters

The only user manual available at this time is a french one but it does not give details about frames, it only state that RFXtrx433 need to have ATI protocol enabled and a minimum firmware revision.

The weird thing here is that both devices does not show the same values for battery and Rssi levels:

  • ENCODER had stable values, battery 100% (new batteries) and Rssi at -72dBm
  • TIC is fool with battery value from 20% to 130% and Rssi from 0dBm to -120dBm, nearly changing at each frame!

As stated in my previous issue, I was using Domoticz before and it can correctly decode frames (but I think it ignored the encoder part as I never seen this before)

If you need more frames captures or someone to do tests, just let me know and I'll happy to help !

Best Regards,
Nicolas.

@nlienard
Copy link

Any progress on this integration? I wish to buy this device but waiting it works on HA as well.
thanks

@elupus
Copy link
Contributor

elupus commented Jun 26, 2022

@GrinGrin i've opened a fix for the RSSI/Battery issue you mentioned here: Danielhiversen/pyRFXtrx#142 it should only affect those data. It will get into HA eventually.

That said, the rest of the data should be there now. Could you verify that you are getting energy counters on recent home assistant?

@GrinGrin
Copy link

Hi @elupus !
Thanks for the update and work!
I'll keep an eye on future releases to see if this issue is fixed and keep you tuned !

@elupus
Copy link
Contributor

elupus commented Jun 28, 2022

@GrinGrin you didn't answer my question thou. Do you get the other sensor data with the current release?

@GrinGrin
Copy link

GrinGrin commented Jun 28, 2022

Sorry, I was not at my place to check if values reported were the same as the power meter. I also done the latest HAss update to check !
Sound pretty good for counters values (count, counter value, energy usage) but battery & rssi values are still weird :-(
Update was done at 7:47 PM
image
image
image

Latest log entries received from the device:

2022-06-28 20:46:25 DEBUG (Thread-3) [RFXtrx] Recv: 0x15 0x60 0x01 0x47 0x09 0xb9 0x55 0x05 0xc7 0x23 0x00 0xfb 0xdf 0xeb 0x02 0x32 0x65 0x6e 0x03 0xc0 0x02 0x69
2022-06-28 20:46:25 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 96, 'sub_type': 1, 'type_string': 'CARTELECTRONIC_TIC', 'id_string': '9b95505c7', 'data': '1560014709b95505c72300fbdfeb0232656e03c00269', 'values': {'Counter value': 16506859, 'Count': 36857198, 'Energy usage': 960, 'Sensor Status': True, 'Contract type': 35, 'Battery numeric': 14, 'Rssi numeric': 6}}

If you need more details, feel free to ask ;-)

@elupus elupus mentioned this issue Jun 28, 2022
22 tasks
@elupus
Copy link
Contributor

elupus commented Jun 28, 2022

Perfect, then it is as expected. Will likely be fixed in point release or next full release.

@nlienard
Copy link

@Chilgl0rd how did you add TIC PULSES 433 V2 in Home Assistant ? In integration menu, i don't see the vendor.
thanks

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

You need the rfxtrx integration (and hardware).

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

Ps. I had to postpone the fixes for rssi and battery, since i have to resolve some unwanted breaking changes.

@nlienard
Copy link

nlienard commented Jun 30, 2022

sure, i got already HW and integration with RFXCom rfxtrx433xl which works for many devices already but autodiscovery is not working for the TIC Pulse 433 V2.

image

image

I was wondering if there are any specific action to do.

in DEBUG log, i got this

Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (SyncWorker_24) [homeassistant.components.rfxtrx] Using modes: ati#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Recv: 0x14 0x01 0x00 0x01 0x02 0x53 0x2c 0x00 0x00 0x40 0x00 0x03 0x00 0x1c 0x10 0x6c 0x46 0x58 0x43 0x4f 0x4d#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Send: 0x0d 0x00 0x00 0x00 0x03 0x53 0x1c 0x00 0x00 0x40 0x00 0x00 0x00 0x00#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Recv: 0x14 0x01 0x00 0x00 0x03 0x53 0x2c 0x00 0x00 0x40 0x00 0x03 0x00 0x1c 0x10 0x6a 0x46 0x58 0x43 0x4f 0x4d#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Send: 0x0d 0x00 0x00 0x01 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Recv: 0x14 0x01 0x00 0x01 0x02 0x53 0x2c 0x00 0x00 0x40 0x00 0x03 0x00 0x1c 0x10 0x6a 0x46 0x58 0x43 0x4f 0x4d#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Status: Status [subtype=433.92MHz, firmware=44, output_power=28, devices=['ati']]#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Send: 0x0d 0x00 0x00 0x03 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00#033[0m
Jun 30 12:28:21 rpi3b-hass hass[4732]: #033[36m2022-06-30 12:28:21 DEBUG (Thread-218) [RFXtrx] Recv: 0x14 0x01 0x07 0x03 0x07 0x43 0x6f 0x70 0x79 0x72 0x69 0x67 0x68 0x74 0x20 0x52 0x46 0x58 0x43 0x4f 0x4d#033[0m

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

That should be enough. Firmware need to be after 20170730

@nlienard
Copy link

got newer firmware, i updated last year for my somfy devices.

What should i do to add the TIC Pulse ?

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

It should be discovered automatically, if you jave auto discovery on. If its on range radio wise.

@nlienard
Copy link

nlienard commented Jun 30, 2022

i just enabled "discovery:" in my configuration.xml (it was commented).
But same result after restarting HA. very weird..
If i unplug the TIC Pulse from Linky and move it close to my RPI having the RFXCom Card, should it discover it (i mean it won't be on linky anymore).
thanks

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

No idea. Dont know how those devices work. Discovery in yaml should not be needed.

@nlienard
Copy link

Firmware is 1044 , it should be fine

Transceiver type = 433.92MHz
Firmware version = 1044
Firmware Type = ProXL1
Noise level = 89
Transmit power = 10dBm
Hardware version = 3.0 RFXtrx433XL

@nlienard
Copy link

with rfxmngr i can see trames coming

------------------------------------------------
30/06/2022 02:06:30:708= 15600103C3FDBCF0E911019D8D2A0000000000000249
Packettype    = Cartelectronic
subtype       = TIC
Sequence nbr  = 3
ID            = C3FDBCF0E9
Contract/Price= 11
Counter1      = 019D8D2A decimal:27102506
Counter2      = 00000000 decimal:0
No change price time warning
TeleInfo      = Present
Apparent Power= 0000 decimal:0
Signal level  = 4  -88dBm
Battery       = OK
------------------------------------------------
30/06/2022 02:09:13:457= 15600104C3FDBCF0E911019D8D2A0000000000000249
Packettype    = Cartelectronic
subtype       = TIC
Sequence nbr  = 4
ID            = C3FDBCF0E9
Contract/Price= 11
Counter1      = 019D8D2A decimal:27102506
Counter2      = 00000000 decimal:0
No change price time warning
TeleInfo      = Present
Apparent Power= 0000 decimal:0
Signal level  = 4  -88dBm
Battery       = OK

sounds good ?

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

I would need to check those codes, but i think those should work. You should be getting device for that in home assistant (with invalid rssi/battery) but otherwise good counters.

@nlienard
Copy link

nlienard commented Jun 30, 2022

well, it is strange, i received these trames when plugging USB RFXCom to my laptop.
Now, i plugged it back to the RPI then running "socat tcp-listen:10001,fork,reuseaddr file:/dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO2VZBCF-if00-port0,raw" and using again rfxmngr, like previously but through RPI IP address and i don't see any trames coming and my RPI is closer to the linky than i was with my laptop

@nlienard
Copy link

nlienard commented Jun 30, 2022

Finally after moving antenna i got some result

image

image

Jun 30 14:53:31 rpi3b-hass hass[12869]: #033[36m2022-06-30 14:53:28 DEBUG (MainThread) [homeassistant.components.rfxtrx] Receive RFXCOM event: {'packet_type': 96, 'sub_type': 2, 'type_string': 'CARTELECTRONIC_ENCODER', 'id_string': '5d8c168f', 'data': '1160020f5d8c168f00000000000000000079', 'values': {'Counter value': 0, 'Count': 0, 'Battery numeric': 9, 'Rssi numeric': 7}}#033[0m

thanks !

@nlienard
Copy link

nlienard commented Jun 30, 2022

on Energy, i can't use these new sensors, do i need some transformation at first ?

there is no Sensor for Energy Wh ? I see only a sensor for Power (W).

HOw can we measure our Consummation in Wh then ?

thanks

@nlienard
Copy link

image

The sensor is named "Energy" but unit of measurement is W. I'm confused totaly.

Energy is Wh.
Power is W

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

That seem like a bug. I dont know the device. Can you figure out which counter is which and whick unit aught to be the correct one?

Ps. Energy is a bit vague term.

@nlienard
Copy link

The sensor is

Apparent Power : instant usage in Watt

@GrinGrin
Copy link

@nlienard I had to customize the entities in my configuration.yaml in order to get them available to the energy dashboard

homeassistant:
  customize:
    sensor.cartelectronic_tic_9b95505c7_count:
      device_class: energy
      unit_of_measurement: Wh
      state_class: total_increasing
    sensor.cartelectronic_tic_9b95505c7_counter_value:
      device_class: energy
      unit_of_measurement: Wh
      state_class: total_increasing
    sensor.cartelectronic_tic_9b95505c7_energy_usage:
      device_class: power
      unit_of_measurement: W
      state_class: measurement

The "counter" entity is for HP (day) and "counter_value" entity is for HC (night) and the "energy_usage" entity for instant usage.
By the way my Linky is configured in historical mode (you can check directly using buttons and find "MODE TIC")

I just applied the customization so my dashboard is still empty... will wait some time to see how it evolve!
image

@nlienard
Copy link

@GrinGrin thanks for these explanation. My linky is also in Historic mode.

For now, with Helpers menu, i did a Riemann convertion using "Energy Usage" as a source (it converts W into Wh).
It is requested because HA Energy Integration needs a sensor in Wh.

I'll try to do a customize on the counter (i've value only on one counter because i don't have any Night/Day subscription).
I didn't know it was directly a measurement in Wh so if i can directly uses these sensor for Energy integration, i'll be happy

Currently i got this graph :

image

image

but i enabled the Tic Pulse in the middle of the day, so i 've to wait a little bit.

Anyway thanks for the help.

@nlienard
Copy link

thanks again for your post, i didn't pay attention the counter was in Wh.

i just did the customize, and checked also the linky and the value coming from linky to HA:

*** ON LINKY : 27103 kWh ***
image

*** on HA: 27103499 Wh ***

image

But now on ENergy, i got a big peak:

image

How do you create a sensor to see the daily consommation in Wh ?

thanks

@elupus
Copy link
Contributor

elupus commented Jun 30, 2022

I don't think it's worth renaming Energy Usage to Power. It would be a breaking change for many.,

The Count and Counter Value sensors can't be given unit, since they depend on what the unit is connected to. So you must do a customize to set it's unit and device class, or template sensor to convert it's value to Wh.

@GrinGrin
Copy link

@nlienard I also had this big bump at nearly 36.000 kWh and had to manually reset the value in HA !

image
To correct this, you need to:

  1. Go to dev tools
  2. Switch to Statistics tab
  3. Search for your sensor
  4. Click the button to adjust sum
  5. Find the date/time where the value was recorded
  6. Click it and update the value accordingly (I've set it to 0)
    image

HA already do the math to get the difference between each measurments and show hourly graph on the dashboard:
image

I'll let it run overnight and see how it look tomorrow. Renaming the entities in HA will make it definitly more readable ;-)

@nlienard
Copy link

nlienard commented Jul 5, 2022

last question: will it still work if we change the mode from "historic" to "Standard" on linky TIC ?
thanks

@nlienard
Copy link

nlienard commented Jul 6, 2022

since I changed the mode of the linky from "historic" to "standard", i don't have the correct value, it is stuck with same values. Any clue ?

image

@elupus
Copy link
Contributor

elupus commented Jul 6, 2022

Your log reports same packet every time, so seems that, that is what the device is reporting.

@nlienard
Copy link

nlienard commented Jul 6, 2022

sure but i went physically on the linky and for instance, i saw the instant power is 0 (because i ve solar panel) so 350W is totaly wrong between 10h and 17h.

Morever, the "standard" mode has different trames.

In standard mode there are 71 fields

ADSC Counter secondary address
VTIC ICT version
DATE Current date and time
NGTF Supplier price schedule name
LTARF Current supplier price description
EAST Total active energy withdrawn
EASF01 Active energy withdrawn Supplier index 01
EASF02 Active energy withdrawn Supplier index 02
EASF03 Active energy withdrawn Supplier index 03
EASF04 Active energy withdrawn Supplier index 04
EASF05 Active energy withdrawn Supplier index 05
EASF06 Active energy withdrawn Supplier index 06
EASF07 Active energy withdrawn Supplier index 07
EASF08 Active energy withdrawn Supplier index 08
EASF09 Active energy withdrawn Supplier index 09
EASF10 Active energy withdrawn Supplier index 10
EASD01 Active energy withdrawn Distributor index 01
EASD02 Active energy withdrawn Distributor index 02
EASD03 Active energy withdrawn Distributor index 03
EASD04 Active energy withdrawn Distributor index 04
EAIT Total injected active energy
ERQ1 Total reactive energy Q1
ERQ2 Total reactive energy Q2
ERQ3 Total reactive energy Q3
ERQ4 Total reactive energy Q4
IRMS1 RMS current phase 1
IRMS2 Phase 2 rms current
IRMS3 Phase 3 rms current
URMS1 Phase 1 rms voltage
URMS2 Phase 2 rms voltage
URMS3 Phase 3 rms voltage
PREF power app. reference
PCOUP power app. of cut
SINSTS power app. Instantaneous withdrawn
SINSTS1 power app. Instantaneous withdrawn phase 1
SINSTS2 power app. Instantaneous withdrawn phase 2
SINSTS3 power app. Instantaneous withdrawn phase 3
SMAXSN power app. max. withdrawn n
SMAXSN1 power app. max. withdrawn n phase 1
SMAXSN2 power app. max. withdrawn n phase 2
SMAXSN3 power app. max. withdrawn n phase 3
SMAXSN-1 Max app power withdrawn n-1
SMAXSN1-1 Max app power withdrawn n-1 phase 1
SMAXSN2-1 Max app power withdrawn n-1 phase 2
SMAXSN3-1 Max app power withdrawn n-1 phase 3
SINSTI power app. Instant injected
SMAXIN power app. max. injected n
SMAXIN-1 Max app power injected n-1
CCASN Point n of the drawn active load curve
CCASN-1 Point n-1 of the drawn active load curve
CCAIN Point n of the injected active load curve
CCAIN-1 Point n-1 of the injected active load curve
UMOY1 Avg voltage ph. 1
UMOY2 Avg voltage ph. 2
UMOY3 Avg voltage ph. 3
STGE Status Register
DPM1 Beginning Mobile Tip 1
FPM1 Mobile Tip End 1
DPM2 Beginning Mobile Tip 2
FPM2 Mobile Tip End 2
DPM3 Beginning Mobile Tip 3
FPM3 Mobile Tip End 3
MSG1 short message
MSG2 super short message
PRM PRM
RELAY Relay
NTARF Current tariff index number
NJOURF Current day number vendor calendar
NJOURF+1 Vendor next calendar day number
PJOURF+1 Profile of the next supplier calendar day
POINTE Profile of the next peak day

Only the consumer fields are available by default if you don't sell your solar production.

In "Historic" mode, here the available fields:

Here is the information available:

ADCO Counter address
OPTARIF Chosen tariff option
ISCOUSC Current subscribed in A
BASE Meter index in Wh
HCHC Off-peak hour index
HCHP full hour index
EJPHN Normal hours index in Wh
EJPHPM Peak hours index in Wh
BBRHCJB Off-peak hour index blue days in Wh
BBRHPJB Full hour index blue days in Wh
BBRHCJW Off-peak hour index white days in Wh
BBRHPJW Full hour index white days in Wh
BBRHCJR Off-peak hour index red days in Wh
BBRHPJR Full hour index red days in Wh
PEJP Notice option in minutes
PTEC Current tariff period
TOMORROW Tomorrow's color
INST Instantaneous intensity in A
ADPS Exceeding warning
IMAX Maximum current in A
PAPP Apparent power in VA
HHPHC HAS
STATUSWORD 000000

How can we see the raw trame to see what's going on ?

@elupus
Copy link
Contributor

elupus commented Jul 6, 2022

In your screenshot, the "data" field is the raw data we get from the rfxtrx device.

@nlienard
Copy link

nlienard commented Jul 6, 2022

ok i just run rfxmgmr and it looks like there is an issue from the source. teleinfo="not present" :(

image

------------------------------------------------
06/07/2022 05:29:25:239= 1401070207436F7079726967687420524658434F4D
------------------------------------------------
06/07/2022 05:32:19:379= 15600100C3FDBCF0E911019E0D9000000000015E0669
Packettype    = Cartelectronic
subtype       = TIC
Sequence nbr  = 0
ID            = C3FDBCF0E9
Contract/Price= 11
Counter1      = 019E0D90 decimal:27135376
Counter2      = 00000000 decimal:0
No change price time warning
TeleInfo      = Not present
Apparent Power= 015E decimal:350
Signal level  = 6  -72dBm
Battery       = OK
------------------------------------------------
06/07/2022 05:34:08:677= 15600101C3FDBCF0E911019E0D9000000000015E0659
Packettype    = Cartelectronic
subtype       = TIC
Sequence nbr  = 1
ID            = C3FDBCF0E9
Contract/Price= 11
Counter1      = 019E0D90 decimal:27135376
Counter2      = 00000000 decimal:0
No change price time warning
TeleInfo      = Not present
Apparent Power= 015E decimal:350
Signal level  = 5  -80dBm
Battery       = OK

@nlienard
Copy link

nlienard commented Jul 6, 2022

I received a reply from cartelectronic support and they said:

Si vous changez le mode TIC il faut alors réinitialiser le modem 433 car il s'est autoconfiguré sur le mode Historique.
Pour cela retirez les piles 10mn.

in english;

If you change the TIC mode, you must then reinitialize the 433 modem because it has autoconfigured itself in History mode.
To do this, remove the batteries for 10 minutes.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants