-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
For ProgrammableSwitchEvent the nocache=1 dosent work #95
Comments
what kind of device is this in fhem? |
It is a MQTT2_DEVICE. The message from MQTT is WISER/SCENE/ACTION/74:{`click‘:‘single‘} I'll give you the whole fhem definition: defmod MQTT2_WISER_SCENE_74 MQTT2_DEVICE WISER_SCENE_74 |
nocache at the moment only influences the active retrieval of values from the homekit side and not the pushing of events from fhem. please try with default=XX. this should reset the internal value after a while so that the new event will be used. |
default=XX has no effect. How long is a while? |
sorry for the late answer... i know what the problem is, but i have at the moment no idea how to fix it without a mayor rewrite of the event interface. i have to think some more... and no, it is not the caching. |
Running into this issue too, I want my on/off switches to also emit Edit: For now I did it with a workaround using a dummy and a watchdog, heres an
|
This is my definition in FHEM:
attr mydevicehomebridgeMapping clear ProgrammableSwitchEvent=click,nocache=true,values=single:SINGLE_PRESS;;;;double:DOUBLE_PRESS
But Homebridge only sends when the status has changed. However, this is rather pointless with ProgrammableSwitchEvent.
This is also adressed in #62 and #70
Thanks for suggestions and have a nice day.
Daniel
The text was updated successfully, but these errors were encountered: