-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Adding support for SilverCrest 3 gang with USB from LIDL (SPSZ 3 A1) #1741
Conversation
I can change the state of a single outlet with this command: But the states reported back are all in the form of /state_l as seen below, i.e. "/state_l3 OFF" Also, when changing an outlet, it seems as the other 2 outlets feels an urge to report the very same states as well, resulting in every state to be reported three times. While I can easily live with that, it feels a bit annoying. zigbee2mqtt/0xec1bbdfffea96bd4/state ON |
This is expected behaviour indeed and cannot be changed
Looks like strange behaviour off the switch itself (firmware), we probably have to live with it. |
…le to have two profiles with same zigbeeModel.
Like I also wrote in the commit message, I had to combine my addidtion with an existing profile, as they otherwise would share the same zigbeeModel, which is illegal. When the code is loaded, I can control the device both with and without setting the endpoints, i.e. the following two commands does the same, so I'm not that worried :-) I have attached an image of the product. |
Oh and also - looks like it doesn't spam the MQTT queue any more. Only one message is submitted per state now, instead of multiple. |
The existing TS110F also needs to be identified via a fingerprint, we cannot share the definitions since the current TS110F only has one endpoint (and this one 3). Asked for the fingerprint in #1705 and will update your PR once I have a response. |
My LoraTap socket module record (only one endpoint): |
…t possible to have two profiles with same zigbeeModel." This reverts commit ef93c2c.
I will revert my change that combined the two and push an updated TS011F and SilverCrest with the above information applied. |
…ead of zigbeeModel Fixed small typos in SilverCrest/SPSZ_3_A1
I have now changed the definition of TS011F according to the info given by @kirovilya - Can you verify that your device still works? |
I think it will work, only I have to change the name of the model. |
The name of the model was changed, only to make it more specific. I can revert it back to TS011F if it is a problem regarding backwards compatibility, i.e. other users unable to use their devices due to a name change? |
I think no need to revert name - 'TS011F_socket_module' is normal for me :) |
Then I think it would make sense, to also consolidate the SilverCrest definition, so it is altso a TuYa device with a whiteLabel of SilverCrest etc. |
…ame configuration, but different branding
Looks good, thanks! |
I want to ask for this features: Do you know if can be possible to send an command to "shutdown one switch for 1 minute" so the switch could power up automatically without another command? This is very very useful for i,e. a watchdog to shutdown raspberry pi, conected to this switch. Its a not very common functionality, that supposes the harware has some kind of timer inside. Thanks for support. |
As far as I can tell, there's no support for anything like that, directly on the device. If you want timers, automation, etc., you will have to program it with HomeAssistant, OpenHAB or similar. As long as you don't boot your zigbee2mqtt or HA/OH machine, you will also be able to use your "watchdog" feature. It's just a matter of timers. The device is just a "dumb" power switch, where you can turn on/off 3 sockets individually. |
No description provided.