Not as elegant as @ThomDietrich sollution and not even as part of my home automation system but I already have a time controlled plug attached to my coffee machine so when I get up I find my coffee ready.
Preparation is done before I go to sleep.
Very very useful if you run on “automated mode” when you wake up!!!
How did you put the check mark and the X mark after status?
Did you “map” the status and in the “map” text you include the image (as html <img> element)?
Looks good! InfluxDB + Grafana is also (still) a great choice.
Regarding persistence: This is an ongoing debate. There are basically two points of few and here’s mine: Read here to learn about the idea of physical and logical groups. If you do it right you’ll create two hierarchies spanning all your items. One hierarchy going top-down through your whole house on a physical perspective, one hierarchy slicing vertically through all items covering them on a logical perspective.
If you do that right, your e.g. Livingroom_Temperature sensor will be part of the Livingroom group and the Temperatures group.
You’ve now reached a point where similar items are covered by logical groups. These groups can now be added to the persistence config.
In my personal opinion defining gPersistence1d doesn’t make much sense as you would need to modify an item each time you want to add or remove or change something related to persistence. You’ve successfully mixed two worlds that ideally should (and very easily can, see above) stay separate…
Thanks @ThomDietrich for reading and trying to explain things to a new openhaber
If I’m not wrong I understand that it’s not useful to manage groups only related to persistence but I have to link persistence strategy to “logical” groups of items. It is correct?
I have a garden lamp controlled by a sonoff basic, through MQTT and OpenHAB (item called Garden_Light_1Lamp).
I would add to this item a new group called gLightSwitchGarden which belongs to gLightSwitch and gGarden groups. Now I understand that this seems to be not the best thing to do…Maybe I would add directly gLightSwitch and gGarden to Garden_Light_1Lamp to keep separated the logical and physical grouping.
Then, I will add persistence strategy to gLightSwitch group. In this way all items which belong to gLightSwitch group will use the same persistence strategy. But what if I have a new gLightSwitch item with a different persistence strategy? I could add directly this item to a new persistence strategy? It will override the group one?
Hello everybody, just a step forward in my configuration. I built my first sensor device using an ESP8266 board (NodeMCU) as MCU, a DHT11 for humidity, a ds18b20 for temperature and a MQ-4 for gas detection…
The firmware I wrote send sensor data as json formatted string to MQTT broker…Then I setup OpenHAB with new items linked to MQTT using the same topic used by the device.
So, my sitemap now shows these values.
then I built a new grafana dashboard to graphs these values
Hi all, I have an Openhab architecture including 433 mhz and zwave devices, MQTT, and so on. Now I discovered Sonoff but I’d like to avoid to delete the original firmware since the eWeLink app presents interesting features. I guess a new ad hoc binding would be a good solution for a standard use of the Sonoff devices. Does anyone know if there is anything cooking on this topic? Thanks