mqtt-elements icon indicating copy to clipboard operation
mqtt-elements copied to clipboard

Polymer elements for MQTT

Results 8 mqtt-elements issues
Sort by recently updated
recently updated
newest added

When receiving large messages with mqtt-elements `Websocket connection to 'ws://localhost:8080/' failed: Invalid frame header` error occurs. As per [specification](http://tools.ietf.org/html/rfc6455) large messages have to be encoded differently. I have found javascript...

I am looking to develop on your excellent work - I am looking to update the version of MQTT.js. But I am stuck at the first hurdle whilst trying to...

Current browserified version is outdated and leads to a continuous flapping with `wss://` connections. I tried to use `` with [cloudmqtt.com](https://www.cloudmqtt.com/) and couldn't establish a stable connection. Alternative I tried...

When removing a mqtt-connection element via ``` document.querySelector("mqtt-connection").remove() ``` currently the `detached: function() {)` is not used to properly/ clean disconnect the client from the broker.

bug
feature:necessary
test needed

When creating one `` element and binding to its client property via `` and then injecting it into another mqtt-connection via `` results in the following error when injected into...

bug

This issue will document the process and progress on the properties

feature:essential

For a TDD running (unit) tests after each change is a fundamental step. Therefore a development setup for the `mqtt-elements` would look like this 1. Start Webserver 2. Start MQTT-Broker...

enhancement
feature:necessary

All custom elements that are distributed with `` should have a full code coverage at least when making the _first release_

feature:essential