jonferreira / vera-mqtt Goto Github PK

Currently the vera mqtt client only publishes variable values whenever a variable's value changes. This satisfies most use cases with an efficient propagation of data however in some cases, the dataset is too sparse for convenient analysis. It would be useful to allow users to specify variables that should be watched and/or polled at some periodicity. For example, polling TemperatureSensor1 or HumiditySensor1 or other variables would allow users to build a continuous dataset for certain sensors. In addition, a new companion mqtt client variable called mqttVariablePollingInterval should be added that allows users to specify the polling interval in seconds.

The existing user interface could be extended to include a second "polling" column that when checked, will add polling for the variable. Another option would be to add a second "Polling" tab.

There is an invalid assumption that client:publish() returns an error if the client fails to publish a message to the mqtt broker. As a result, the vera client never reconnects to the broker because the tests for ~= nil after invoking :publish() never hold true.

It seems the lua mqtt client is not only incomplete, there is no one actively developing it any more therefore a quick and dirty fix that should work is to simply return the result of the client:message_write() from the client:publish() method.

It seems that MIOS/Vera has standardized on dkjson for json decoding and encoding. To reduce the dependencies on UI6+, we should port the plugin to dkjson.

Given the MQTT Client ID is now unique, it should be displayed on the Settings tab even though it is logged.

The connection id should include the controller serial number to guarantee uniqueness.

It would be good to extend the SensorMqtt plugin to include a relatively benign subscription as a "request/response" proof of concept for controlling a Vera remotely over MQTT. Other adventurous souls could expand the set of actions to address more use cases.

Concept

Implement a relatively benign topic action that allows a remote mqtt client to request an update for one or more service variables.

Design

• If a service variable request includes device id, then the variable will only be returned for that device.
• If a service variable request does not specify a device, then the variable will be returned to all devices that provide the requested service variable.
• The service variable requests are encoded as a JSON array allowing the remote client to request one or more variables in a single request

Service Variable Request Topic

/Vera/(SerialNumber)/GETVARIABLE

Payload Example

{
    [
      {"ServiceId: "urn:upnp-org:serviceId:TemperatureSensor1", "Variable": "CurrentTemperature"},
      {"ServiceId: "urn:upnp-org:serviceId:HumiditySensor1", "Variable": "CurrentLevel", "DeviceId": 49}
   ]
}

• The first element requests the current temperature from all TemperatureSensor devices.
• The second element requests the current humidity from device 49

If the client connection is severed by the broker, then the client will not reliably reconnect. This is due to edge cases for the currently implemented connection state machine. For example, in the current implementation, the client will not resume periodic mqtt pings via the MQTT.client.handler() method.

Error: " Error executing function MQTT_showExistingServices(): MQTT_showExistingServices is not a function "
when I open "watchdog" tab.
Controller: Veraplus
Firmware: 1.7.5386 (7.32)

I would appreciate if you can help me

Currently the MQTT client is a publish only client however the underpinnings for a persistent connection model are already in place. Currently, the client will not reconnect to the broker unless it has something to publish. To improve future support for subscription support, the connection model should be extended to reconnect after a user-specified interval elapses. This is a very straight-forward change - check if the reconnect interval has elapsed in the processMQTTevents() method and if so, attempt to reconnect to the broker.