RFXtrx

[husa550]

Thank's!

I'm going to buy more temp sensors and will make a dedicated page just for temperature in different room's.

Sorry to say but i don't have a clue how websockets work or what can be done whit it.
If you can/want, please explain websockets to me
Is websockets anyting that i can have use of?

The lamp feedback is fake made by a loopbacksystem in CommandFusion/iViewer.

Then i have real feedback from my Dreambox Satbox and from some other system showing if iViewer have contact or not with them.

[krambriw]

I understand that you are swedish so I think the discussion in the link below could be a good start. There are sample codes inside as well that can be re-used or as ideas.

http://www.switchking.se/forum/viewtopi ... =websocket

[husa550]

Thank's, i will take a look!

[krambriw]

New version with new features published in the first post

[stefcola]

hi Walter!
thanks for your great work on the RFXtrx plugin.
I have a x10 digimax 210 who is not recognized (Unknown message: ['09', '40', '00', 'de', '06', '7f', '15', '13', '4a', '73'])

With the RFXmngr.exe i have :
------------------------------------------------
0940002A387C13140171
Packettype = Thermostat1
subtype = Digimax
Sequence nbr = 42
ID = 14460
Temperature = 19 ┬░C
Set = 20 ┬░C
Mode = heating
Status = demand
Signal level = 7
------------------------------------------------

Can you support this device in your plugin ?

Many thanks
Stef

[krambriw]

Hello Stef,
So far I haven't implemented support for Thermostats but I will look into it, it doesn't look too complicated

BestR

[stefcola]

I thank you in advance for taking the time to work for add this device.
I want to use it for my home automation system in order to control my electric heaters.

[Mastiff]

Hi, Krambriw! Would it be much bother to change the "duplicated events" to a timer? I have to use a range extender (Nexa LEST-701) for my system because I have problems getting Nexa wall switches reliably, and that means that there will sometimes be first the event from the switch and then the event from the extender within a couple of seconds. So would it be possible to have something like "allow duplicated events if separated by more than..."? The best would be if it could be put in on a per trigger basis, but I'm guessing that's a lot more complicated!

[krambriw]

@Mastiff

Have you tried this setting for the plugin?

[Mastiff]

Yeah, I have. If I turn it on I get some double triggers. If I turn it off I have the problem that if no other signal has been registerered in the meantime it will not register a second, intended signal maybe 10 seconds later.

[krambriw]

That's true, if it is the same status for the signal, it will not be forwarded. Introducing a timer reset is of course possible but I am worried if some other users rely on the existing function. So it has most likely to be a solution that keeps the backward compatibility.

If on trigger basis, is it the self learning (AC) protocol that you use together with the extender?

BR

[krambriw]

There is a little trick that might do what you need...

You can 'from outside' set the condition if duplicated events are allowed or not. To allow duplicated events, the typical python command looks like this

Code: Select all

eg.plugins.RFXtrx.plugin.bDupEvents = True

To block duplicated events would then be

Code: Select all

eg.plugins.RFXtrx.plugin.bDupEvents = False

If you would use these python commands in macros and make use of the SchedulGhost plugin as well, you could actually make the blocking of duplicated events dynamically timer controlled.

Assuming you are running your system by default allowing duplicated events. If you create two macros as the example below, you can trigger the second macro with your specific signal when you need to block duplicates. The egg timer can be set to any value, in my tests I set it to 5 seconds.

When the second macro starts execution, it blocks duplicated events in RFXtrx until the egg timer triggers an event that starts the first macro. The first macro then inhibits the blocking.

All events that you would like to trigger this feature with, you just drag them to the second macro folder.

This design is working globally for the RFXtrx plugin, i.e. the blocking/unblocking is active for all type of events.

BR

[Mastiff]

Tack s├Ñ mycket, du vise man i ├Âstern! I will do that!

[krambriw]

@ Stef,

Could you try the attached version below, it is supposed to support your Digimax thermostats. Both ways, you should receive events and there is a new action where you should be able to set it.

BR

__init__.py

(608.51 KiB) Downloaded 141 times

[stefcola]

Thanks for the help

This does not work all the time, see below ;

19:32:00 Debug Info: 09400007067f170e0380
19:32:00 RFXtrx.Type: Digimax, TLX7506 id: 1663 ' temperature: 23.0 setpoint: 14.0 status: initializing mode: heating signal: 8'

19:32:08 Debug Info: 09400009067f170e7b70
19:32:08 Decoding of message failed: ['09', '40', '00', '09', '06', '7f', '17', '0e', '7b', '70']

with Debug mode off :
19:34:07 RFXtrx.Type: Digimax, TLX7506 id: 1663 ' temperature: 24.0 setpoint: 22.0 status: no demand mode: heating signal: 7'
19:34:33 Decoding of message failed: ['09', '40', '00', '19', '06', '7f', '18', '17', '52', '83']

hope this helps