skunkiechris Posted 20 hours ago Posted 20 hours ago (edited) Hi @Goose66, I have two of these hooked up, but they are not reporting real time status changes. They seem to only update on short poll. Is there something I'm doing wrong? Edit: I set the console teleperiod to 10 again, and now I seem to get changes reported every time we hit the 10 second mark. Is this how it's supposed to work? I thought a device event should trigger a status change? Thanks! Edited 20 hours ago by skunkiechris Quote
EWhite Posted 20 hours ago Posted 20 hours ago (edited) let me look at whats going on better.... Edited 20 hours ago by EWhite Quote
EWhite Posted 20 hours ago Posted 20 hours ago post #2 of my writeup.... Quote You now need to go to Tools again, and go to Console. Down at bottom of screen in the command box type : TelePeriod 10 and hit enter. this sets update time to 10 seconds on MQTT messages. you can change this to whatever you want in seconds for reporting...not sure you will ever get "real time" reporting as i would think it would overwhelm the MQTT server with messages... Quote
skunkiechris Posted 17 hours ago Author Posted 17 hours ago Right, I wouldn't think that should go too low. Yes, I did see and set the teleperiod. I was just under the impression an event would trigger reporting, vs waiting for a time to come around. So that's (obviously?) not true then? Thanks!! 2 hours ago, EWhite said: post #2 of my writeup.... you can change this to whatever you want in seconds for reporting...not sure you will ever get "real time" reporting as i would think it would overwhelm the MQTT server with messages... Quote
Goose66 Posted 16 hours ago Posted 16 hours ago Just to be clear, this is a problem with the sensor device, not the Tasmota plugin, I assume. Quote
EWhite Posted 15 hours ago Posted 15 hours ago 1 hour ago, Goose66 said: Just to be clear, this is a problem with the sensor device, not the Tasmota plugin, I assume. yes.. Quote
EWhite Posted 15 hours ago Posted 15 hours ago 2 hours ago, skunkiechris said: Right, I wouldn't think that should go too low. Yes, I did see and set the teleperiod. I was just under the impression an event would trigger reporting, vs waiting for a time to come around. So that's (obviously?) not true then? Thanks!! I think that since this device uses MQTT you will never get an immediate response. for me it was not a big deal....i dont need to know the EXACT moment something happened...it just had to be close. im not sure what other devices are out there and if the offer the same detail you want, along with working along side EISY. Quote
Goose66 Posted 14 hours ago Posted 14 hours ago The teleperiod should be the periodic telemetry messaging for all tasmota devices, right? In other words, the periodic updates in state sent to the Telemetry "tele/" subtopic. But shouldn't the device send state changes to the State "stat/" subtopic as well when state changes? For example, with switches, you get telemetry messages every 90 seconds or so, but you get state messages instantly. Perhaps we need another MQTT Explorer log output watching one of these things to inventory the messages. And if the device doesn't send state messages on state change by default, it seems like it would be easy to set a Tasmota Rule to send a state message upon state change for each state you want reported right away. Also, there appears to be an "Occupancy Delay" parameter that can be set through the plugin (via Admin Console). What is that set to? Is it possible that is where the 10 second delay is coming from? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.