# Basics: Reading Documentation - Message structure

**URL:** <https://discourse.nodered.org/t/basics-reading-documentation-message-structure/39430>\
**Category:** General\
**Created:** [20 January 2021 11:33 UTC](https://discourse.nodered.org/t/basics-reading-documentation-message-structure/39430 "2021-01-20T11:33:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [20 January 2021 11:49 UTC](https://discourse.nodered.org/t/basics-reading-documentation-message-structure/39430/2 "2021-01-20T11:49:09Z")

</div>

Your message structure looks correct in your example.  
the node is 3 years old and last comment in the github issue was december 2019.  
there is some talk on this forum here

> [@WS2801 on Raspberry Pi not working](https://discourse.nodered.org/t/ws2801-on-raspberry-pi-not-working/19084):
>
> I can't imagine there might be many people using these (string of 50 water proof RGB LEDS that use 2-wire SPI for data/clock) I used to have them working in Node-RED last christmas but they only work this year if I say there is only 1 in the string - I can control that one fine Once I say I have more (say 10) I just get a couple of them lighting up with random colour) To prove they weren't broken, I installed an old Adafruit python lib and they worked fine The only hint I'm getting is this e…

---

_[View the full topic](https://discourse.nodered.org/t/basics-reading-documentation-message-structure/39430)._