yup, I'll definitively be there.

Yes, I'm using the persistence & pickle file. The PR fixes the problem. Just tested with latest HA dev branch. Thanks for the quick answer Martin.

After the upgrade to 0.42.2 all my sensors are being rejected by HA because of the error:

File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/mysensors.py", line 391, in device_state_attributes
    ATTR_BATTERY_LEVEL: node.battery_level,
  File "/home/homeassistant/.homeassistant/deps/mysensors/__init__.py", line 420, in battery_level
    return self._battery_level
AttributeError: 'Sensor' object has no attribute '_battery_level'` 

I haven't tried rolling back to 0.41 or debugging the code yet. Wanted to throw it out there to see if anyone else has experienced similar behaviour?

and building it is 99% of the fun !

I built all my sensors on NodeMCUs only because I had a large batch of them. My sensors use HLK to step down from AC mains current to 5V into Vin which I've had no problems with so far. Comms is via MQTT to Mosquito running on a Raspberry Pi alongside Home Assistant.

I'm experimenting now with a 600mAH 3,7V Lipo battery, charger and boost converter with deep-sleep just to see how far I can go.

Having said that if I would do it all over again I would go the Wemos/NRF way!

@martinhjelmare I made a PR. https://github.com/theolind/pymysensors/pull/80

@martinhjelmare is this something I can help contribute too?

I'm not sure if this is a MySensors or Home Assistant issue, but using the example at https://www.mysensors.org/build/display to read the time from my HA controller, it always pulls the UTC time where in the MySensors library documentation here it states that void receiveTime(unsigned long ts); returns ts "Adjusted for timezone by controller."

I have the time_zone parameter correctly configured in my Home Assistant's configuration.yaml file.

As a workaround I have the sensor node convert the time using this piece of code:

#include <Timezone.h>
#include <TimeLib.h>
TimeChangeRule CEST = { "CEST", Last, Sun, Mar, 12, 120 }; // Central European Summer Time, 2 hrs offset
TimeChangeRule CET = { "CET ", Last, Sun, Nov, 5, 60 };   // Central European Standard Time, 1 hr offset
Timezone CE(CEST, CET);
: 
:     
TimeChangeRule * tcr;
time_t t = CE.toLocal(controllerTime, &tcr);
RTC.set(t);

But it would good to know if its a bug or I'm just doing something incorrect?

I have a similar setup: MySensor nodes running on NodeMcu/ESP8266 and each using an MQTT client gateway to send sensor status directly to my MQTT broker running on a Raspberry pi alongside Home Assistant. And I also had to replace sleep() with counters in the loop() code. Those error codes are described here.

I spent many hours learning and configuring HA so sticking to that for now. Their community, like MySensors are very helpful.

Not sure if this helps but for debugging I use MQTT spy (https://github.com/eclipse/paho.mqtt-spy/wiki) for tracking the comms

I believe the node id will always be 0 for gateways so the examples are a little misleading. For example the output shows connections with a node id of 2 (e.g. mygateway1-out/2/1/1/0/49 55.722519;13.018121;13)

Glad I found this post. I couldn't work out why my ESP8266 which is an MQTT gateway and sensor in one was always ignoring the MY_NODE_ID. Perhaps good to mention in the doc that if you have MY_GATEWAY_MQTT_CLIENT defined the node will always be 0 ?

MY_LEDS_BLINKING_FEATURE is now obsolete in the latest 2.1

@sundberg84 said:

It must depend on what you are planning to connect to the relay

It would use it to switch on and off an external mounted lamp - so with a fixed Watt & Voltage. Probably an LED 220V Lamp. Should I avoid zero-crossover as I've read somewhere that zero-crossover can cause a surge current of perhaps 10 to 40 times the steady state current when switched on.

Thanks for this. One question about the SSR. Does it matter if its a zero crossing relay or not if just switching lamps with fixed amps? That the difference between the G3MB-202P and G3MB-202PL. I'm not sure which to get.

@sundberg84 Thanks for sharing this. I'm gathering the components and plan to build it soon when the PCB v7.1 is available.

I do have a few questions if I may

• with the Relay, is it important to have one that has zero crossover? E.g the difference between getting the G3MC-202PL over a G3MC-202P
• what were you planning to use the 16Mhz oscillator for eventually?
• do you see any issues if I build the first prototype using an ESP-12 (ESP8266 with onboard Serial WiFi running at 3.3v)?