I'd like to run Grafana setup with BigClown but unfortunately I'm not able to find the script the documentation is referring to in content/doc/integrations/grafana-for-visualization.md:

Get the Python source for the gateway (mqtt_to_influxdb.py@GitHub) from MQTT (Mosquitto) to InfluxDB. And make it executable.

The link leads to https://github.com/bigclownlabs/bcf-climate-station/blob/master/hub/mqtt_to_influxdb.py. There is https://github.com/bigclownlabs/bcf-kit-wireless-climate-monitor now but it doesn't contain this file anymore.

The cloony pinout drawn here (https://www.bigclown.com/doc/hardware/header-pinout/) is not the same as in the schematics here (https://github.com/bigclownlabs/bc-hardware/blob/master/out/bc-cloony/bc-cloony-rev-1-0.pdf). At least with respect to the SDA0,SCL0 signals.

The pinout in the schematics seems to be the correct one.

Please add spacing of the pin header to the website.
Thanks.

The code here for this flow is a duplicate of the pairing flow

Hi,
the automatic_pairing_start() method sends
usb_talk_send_string("["/pairing-mode", "stop"]\n");
Should be
usb_talk_send_string("["/automatic-pairing", "start"]\n");

regards
Zdenek

Is there any module for the site generator which would pregenerate PDF version of every documentation page or at least provided some 'Print this page' function, which would generate printing friendly version (with JS in user's browser)?

I would really appreciate this as a docs user, because sometimes I want to make notes to tutorials (or simply have a printed document).

In the last chapter "Connect IFTTT in Node-RED" (step 2) there is a code for import which should look like on the picture. But when you use Copy function, the code is different and the result will not work. The manual edits according the picture are needed. And the kit owners have to change it more: flood-detector:0 → kit-flood-detector:0.

Note: The documentation overall may be a bit obsolete/confusing from the kit owners/begginers perspective who do not know all the details yet (messages, firmware flashing etc.). We are navigated to chapters already solved within the kit (firmware updates using older core modules with two buttons etc.), some steps are not explained more for beginners (the difference between setting things done with the USB dongle in PC and RasPi etc.).

But we will try to figure all out and enjoy the way around. ;)

Please add the following info to the About Sensor Module docu page:

1. add image of rev 1.1 board
2. add connection examples
   • at least photo with 1-wire from e-shop page
   • optional typical connection of:
     • button (digital input)
     • LED (digital output)
     • pot (analog input)
     • 1-wire (external power and parasite power)

Please add Shipping page, where buyers can find info about shipping - available methods and (most importantly) shipping cost. Now we have to go through entire "shopping cart" process to check cost of shipping, which is not very pleasant experience.

Thanks

On https://www.bigclown.com/doc/tutorials/mysigfox-com-service/
The https://requestb.in does not respond.
How can I test MySigfox?
Is it possible by https://ifttt.com?
Thx

On https://www.bigclown.com/doc/projects/radio-lcd-thermostat/#integration-with-blynk the QR code of step 8 is different from the image of step 9

https://shop.bigclown.com/radio-dongle/
links to
https://www.bigclown.com/doc/hardware/about-usb-dongle/
which is 404

In the integration documentation for Blynk on the page
https://www.bigclown.com/doc/integrations/blynk-for-mobile-applications/
The QR code for project setup is missing
Thanks :)

Footer of documentation pages says "Byl článek nesrozumitelný nebo nešlo něco udělat?..." and encourages people to discuss problems with particular tutorial over mail. I think we should encourage users to discuss problems here (and not with mail), with the help of Github Issues, because:

• discussion will be public and more users can say their opinion (and "víc hlav víc ví", dont know the english equivalent)
• we can track issues with tutorials that have already been fixed

We can change this to "use github issues" or "use github issus or send a mail".

What do you think?

Use of first level headline ('#' in markdown) should be reserved for page titles only.

• this is common use of first level headlines
• it does not look nice when page title is smaller than subtitles