@tinman I had lighting4 enabled. After that played with lightning4 and byron/select plus. I enabled them and disabled them to test etc. At the moment both are enabled. So yes I think I made changes after the first auto creation,
When I push the button, I see the yellow led on the rfxcom blinking.
Any idea how to fix this? And how I can use this button/doorbell the way I want. A once tripped for ever sensor is useless of course.
enabled at the moment: AC,BLindsTx, Hideki,Lighting4,Oregon. and NOT x10!
Look at the Advanced → Variables tab of the first of the new devices. Is there an AutoUntrip variable? If so, set its value to 5. This should untrip the device in 5 seconds. I believe that you can just delete the second device.
Changing the device type changes the icon associated with the device. Since they are both sensor type devices there will be no change in the variables associated with the device or with the basic functionality.
It’s not something that can be done reasonably in the current version of the plugin. I’m working on the next version of the plugin. I hope to have a way of creating devices that can transmit Lighting4 commands.
Most device commands are obviously already available and are a result of knowing the device type. Manually created devices (done by selecting the RFXtrx New Device tab) specify the device type. Problems arise sometimes with auto-created devices when the received message protocol may be valid for different types of devices. The current version of the plugin provides some means of converting similar devices e.g sensor type devices. But when a received message may be from any one of dissimilar devices it’s problematic to create one type of device that cannot be easily converted to another.
The other problem here is that the plugin does not yet handle wireless doorbell devices. These will probably be similar to some light switch devices. For these devices the light device is created and a device simulating a remote control may also be created. I’ll be working on this as well.