Advertisement
Guest User

Untitled

a guest
Sep 29th, 2016
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.03 KB | None | 0 0
  1. # Synopsis
  2.  
  3. Thng Properties that were created with the `evrythng-extended.js` SDK and ARE NOT
  4. URL encoded are not being published by the MQTT broker at mqtt.evrythng.com
  5.  
  6. # Description
  7.  
  8. In my custom Reactor script, I was creating Thng Properties that look like the following:
  9.  
  10. ```
  11. __rule__efb705593acd44cbb828e4e52befdf30__condition__ambient_light_>_5_@10s
  12. ```
  13.  
  14. Note the `>` and `@` symbols. I was creating these Properties using the
  15. `evrythng-extended.js` SDK with the following command:
  16.  
  17. ```javascript
  18. app.thng(this.thng.id).property($PROPERTY).update(payload).then((response) => {
  19. "..."
  20. })
  21. ```
  22.  
  23. ...where `$PROPERTY` was a string like the above example.
  24.  
  25. When I subscribed to the MQTT topic of the Thng that the above Property was on,
  26. I recieved updates to every Property EXCEPT that one. When I changed the name
  27. to the following:
  28.  
  29. ```
  30. __rule__efb705593acd44cbb828e4e52befdf30__condition__ambient_light_LT_5_10s
  31. ```
  32.  
  33. I recieved those Properties just fine.
  34.  
  35. I tested this out using MqttFx, to be sure it was an issue on your end, and got
  36. the same result.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement