pimatic support

[eric12]

Hi there,

first of all: awesome work you did! I really like the idea of bundling multiple supported sensors into this project. And it works like a charm.
Currently I'm pushing my sensor data to thingsspeak, but I'm wondering if there are plans for pimatic support.

[rtenklooster]

Hi there,
.. if there are plans for pimatic support.

At the moment, not as far as I know. I never heard of it so i did take a look at the demo. I think there are more grown-up alternatives like domoticz / openhab with a larger user base, so more potential. Correct me if i'm wrong about that. But if you can write some code to get it supported, we can always (try to) adopt it..

[chrille]

At the moment, not as far as I know. I never heard of it so i did take a look at the demo. I think there are more grown-up alternatives like domoticz / openhab with a larger user base, so more potential. Correct me if i'm wrong about that. But if you can write some code to get it supported, we can always (try to) adopt it..

Personally I don't think it's the job of a small embedded device (like the ESP8266) to implement a whole bunch of API's towards different systems. Instead it should focus on one or two (like MQTT and a customizable HTTP interface). Then users can use external software like NodeRED or MQTTwarn to adopt towards their specific application. Development resources would be much better spend on adding support for new sensors and improved stability.

- Jan

[rtenklooster]

At the moment, not as far as I know. I never heard of it so i did take a look at the demo. I think there are more grown-up alternatives like domoticz / openhab with a larger user base, so more potential. Correct me if i'm wrong about that. But if you can write some code to get it supported, we can always (try to) adopt it..

Personally I don't think it's the job of a small embedded device (like the ESP8266) to implement a whole bunch of API's towards different systems. Instead it should focus on one or two (like MQTT and a customizable HTTP interface). Then users can use external software like NodeRED or MQTTwarn to adopt towards their specific application. Development resources would be much better spend on adding support for new sensors and improved stability.

- Jan

Amen to that

[wutu]

ESPEasy working with Pimatic. http://forum.pimatic.org/topic/1367/esp ... on-esp8266.

[tozett]

maybe helpful to define ESPeasy primary as a "sensor-node" for a lot of possible "backends".
right in front of the wiki? with a diagram?

than there can maybe room with plugins (pimatic)
to send specific data in specific formats _from_ the sensor _to_ backends,

plugins could also expand the collector-only-"node" basic functions
to an extended node with extended functions _on_ the node (RFID...)

so maybe the devs have to take out / divide CORE-OS functions (sensor-node-functions) clearly from PLUGIN/"extended-node"-functions?

jelabs has another idea for an backend, where everthing gets into this via mqtt (like node-red?)
http://www.esp8266.nu/forum/viewtopic.p ... t=10#p3736
one of a lot ideas ..

[tozett]

cool graphs,
fast demo-website (on a raspberry?)
rule engine looks good.

[wutu]

fast demo-website (on a raspberry?)

I do not know, but I do not run slower on my rpi.

Because ESP Easy caught me, I wrote MQTT module for Pimatic https://forum.pimatic.org/topic/1444/ne ... matic-mqtt or https://github.com/wutu/pimatic-mqtt/tree/master

[tozett]

+1