-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
value polling interval #6
Comments
Hm .... would not be the homebridge plugin needs to make sure it handles that? When you open a „room“ in the iOS home app also homebridge requests all Infos for all devices in this room. So a „mass“ request also happens there. |
Probably you are right... I didn't use homebridge, so can't say exactly. But it would be a good upgrade of homebridge from iobroker side ;) |
Which homebridge-plugins do you use to integrate those 433MHz devices? |
it is homebridge-noolite . |
found in forum :-) Please see there. open an isue with tem and we see what they say :) |
thanks ;) |
just a question. When we use global-homebridge-mode is there a way to initiate device status update from iobroker? |
Did you open an issue with noolite plugin? For the global mode question: I also thought about it but then checked things and decided to wait till someone asks because a bit more difficult there ;-) |
No, I didn't raise any issues to homebridge noolite yet because I faced another problem. When not in global-mode, after some time MTRF-64 stops responding to status updates (even from plugin web interface). I see that request for update is sent to MTRF, but nothing received back to plugin. I currently can't understand where the problem is (USB-TTL, linux settings, plugin itself or wrapper mode) and moved to global-mode to see. Will check tomorrow if it still receives messages back from MTRF or not.... Currently it is more important than "mass attack" to 433 MHz :) |
Update: Stopping status updates is the issue of homebridge-noolite module itself, developer is aware and working on update. |
In addition to value polling interval is it possible to add a polling interval delay setting ( in milliseconds), so the device states are checked with "polling interval" but with "delay" between requests? It will be useful for some 433 MHz devices when a lot of channels being requested at once makes difficult to use the same frequency by other devices.
The text was updated successfully, but these errors were encountered: