General Discussion

DHT - Yes, Using 2xAA to VCC will also work untill it reaches somewhere around 2.6-2.8V where the arduino will stop working. I use booster and have nodes almost hitting a year now, still running and reporting good health.

@tbowmo I'm using a Harmony Companion, it's only the hub and a simple remote. Before I used a Harmony One and for me it's no problem not having a display anymore. By default I can setup 3 different activities (can be too limited for some) and I integrated the Harmony Hub in a Vera Edge. The Edge can be triggered on activities which you activate. No it does not yet do what you demand ,but for me the Hub is a great addition to HA.

@dark-nico Now I get your nick :clap:

Yes this is a good explanation why not to pursue exchange in the forum.

@Erik-Forsberg I think one should be a bit careful about making too many special rules for different cases, between device and controller. I think there should be set ways of communicating between the controller and device. There should also be ways for the user to make rules to create the automations, but this should not change the set ways for communication. In this case, when we need an initial value from the user, which should be automated somehow, I think the user should be able to make rules, and somehow be able to set an initial state, by controller API or other means. But I think that should be detached from the specific device - controller communication. You can have a look at my handle_req branch here: https://github.com/MartinHjelmare/pymysensors/tree/handle_req I would say your implementation looks fine, although I have some comments. We can continue at github.

@TheoL said: offtopic: Conrad is vast blij met jou Tabs open hebben staan is een, werkelijk bestellen iets anders :stuck_out_tongue_closed_eyes:

@candylion I believe so, old-fashioned style LED vintage bulbs with conventional exposed filament look for decorative lighting. You can utilize "vintage style" bulbs for as long as the light fixture and wattage match. I am acutally using one of my vintage bulbs (which I bought from Codale) in our living like an accent light in the corner of the room.

Great and clear explanation @tbowmo . Thanks a lot. Thanks @scalz for the link. I read it and it was useful.

@Chakkie If you are concerned about security, and the neighbor being able to control your lights / locks, then you should look into the security thread located here

If you use at least a half decent search function and search the example tree for "eeprom" the example will show no matter the order of the keywords, so is a renaming really necessary?

@Yveaux Yes I have checked the nordic website regarding the power consumption and they are nearly the same in deep sleep. Anyway, thanks a lot for the discussion :)

@moskovskiy82 said: Invalid protocol "MQTT" Please search the forum first before you post an issue.

i Know it's in repeater mode. I couldn't find any downsides in turning it on except that the sleep function had to be disabled. It still acts as a sensor node

If you use Set to send your temp/hum you can define how many decimals you want: MyMessage& set(float value, uint8_t decimals); For example: gw.send(msgTemp.set(temperature, 1)); will send you the value with 1 decimal. Reference: here

If you still want the delay you can use gw.wait instead. That will process incoming radio messages.

@martinhjelmare Great! I'll try it tomorrow. Thanks a lot

For instance, with "orange" internet provider, i know how to redirect the port :1234 from internet to :80 intranet... but only once. This is cool for 1 non editable port. Sadly I don't think we can close the :80 port. It is (was) used by all the chat software. For the rest: never keep the box-user, never keep the box-software, try to never keep the box-ports. The bad guys KNOW this things. For a old but still used automation-device (witch can control big companies) it still the box-parameters. So... easy to enter into the programs. It was the same for Americans money distributor !!! (now, the have a random password when send to the client)

Now the RPi based on a new install of Raspbian Jessie, OpenHab 1.8.0 and Mosquitto is up and running and the ESP8266 MQTT client does connect without any problems. I have not changed anything in the code but Mosquitto is now based on the RPi repository for Jessie and not the mosquito_wheezy one. That seems to have fixed it so those versions are likely different but I have not put any time into checking this.