Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Lübbe Onken
    @luebbe
    @kleini Did you also read the heise online article about the ESP VOC sensor? ;) Here's the full url: https://github.com/prampec/IotWebConf
    Chris
    @Christian-Me
    @luebbe very similar to an "old" project of mine https://github.com/Christian-Me/healthy-indoors-project ;) and many other projects out there. But actually I plan to get rid off the hole web interface for my home devices.... let`s see where this end. Great would be to be able to hard code the WiFI credentials inside the firmware with ESP8266-Homie to skip the step to upload the config.json.
    Marcus Klein
    @kleini
    @luebbe I only cross-read it. Looks interesting but my priorities are currently here: https://github.com/kleini/homie-relays-device/
    MCP23017 IO expander works without any problems, will now extend its outputs with A2982 8-channel source driver to drive then relays directly. another option would be to use opto-copplers but they consume more space than a A2982. If all that works on a breadboard, I will extend your RelayNode with an array option to drive 16 relays and build PCBs.
    @Christian-Me Uploading some config.json is not a big deal. I use nodemcu upload_reset_method with these two additional NPN transistors next to ESP12-F and I don't need to press any buttons for programming any more. Works all from the desktop.
    Chris
    @Christian-Me
    @kleini perhaps if I'm a little bit further in my project I can explain my approach better. For now the config.json upload works (even I spend some hours debugging why the config.json in a way "erased" with my firmware after boot. ui_bundle.gz is still there and working - and did not found a real cause. disabling HOMIE_CONFIG 0 is my workaround for now (ram and flash is reported under 50% and without config under 35%)
    Nice project. Are you planning to use solid state relays (the small omron have a nice foodprint) to? I don`t like the klicks of relays. I use the chinees 4 ch modules quite often.
    Chris
    @Christian-Me
    Were you source these nice cases? Would like to find them with a clear top cover to add a display or leds behind without dremeling around
    Marcus Klein
    @kleini
    there will a logic board and a "high voltage & relays board". so replacing the relays board with another one should be simple as long as the coils of the relays can be driven with 12V
    Marcus Klein
    @kleini
    I order my hardware at reichelt.de. They have a lot of stuff, part prices are okay, especially if you buy larger amounts of single parts.
    Lübbe Onken
    @luebbe
    Very nice projects indeed :thumbsup:
    @Christian-Me it should be possible to hardwire WiFi credentials into the firmware which will be used as fallback if the config.json doesn't exist (yet) or the credentials from config.json don't work.
    Chris
    @Christian-Me

    hardwire WiFi credentials into the firmware

    Something like this
    Homie.setParamter(WIFI_SSID, "MyNetwork");

    Lübbe Onken
    @luebbe
    Exactly. And the parameters are read from a non-versioned include file.
    camiloavil
    @camiloavil
    Hi everyone. I don't know if someone already ask this. But this implementation can be connected to mqtt over tls? I am trying but I can't do it maybe is a mistake
    Marcus Klein
    @kleini
    Hi @camiloavil. I use encrypted connections for all of my Homie devices. I don't have the perfect example for you, as I am working on a lot of different libraries for fixes here and there, but you can have a look at the following ones:
    https://github.com/kleini/homie-relays-device/
    https://github.com/kleini/sonoff-4ch
    https://github.com/kleini/sonoff-basic
    https://github.com/kleini/shelly-1
    https://github.com/kleini/esp8266-12e
    I don't utilize actually the md5 sum of the MQTT server certificate. Maybe that is a tricky part.
    camiloavil
    @camiloavil
    @kleini hi. Tks for the information. I had to check the information about it. And it work it's necessary add the build flags and check the config.json and that is it. Finally mqtt is over tls tks
    Igor
    @igrowing
    Hi Marcus. Timer lib is used in your sketch instead of Ticker. What's advantage of Timer over Ticker? Thank you!
    camiloavil
    @camiloavil
    @kleini Hi. do you use ota at the same time whit mqtt over ssl. I already set correctly mqtt ssl and validate fingerprint whit "openssl x509 -in mqttserver.crt -sha1 -noout -fingerprint" on broker certificate. But when i try to update the firmware over OTA the esp disconnect of mqtt and the process stop. I get this "Waiting for device to come online...
    Waiting for device info...
    Publishing new firmware with checksum 3f5fae2195fc08ccc8451c80fdb0e4ad
    Expecting checksum 3f5fae2195fc08ccc8451c80fdb0e4ad, got a8bcb28814ff5429971876586176899f, update failed!
    "
    I only can update over ota whitout ssl connection do you know what's the error ?
    Marcus Klein
    @kleini
    @igrowing Actually I don't really remember, why I chose Timer instead of Ticker. I think, I just wanted to keep dependency footprint small and some other library already used Timer but I can not find this other library any more. So there is no particular reason not to use Ticker instead.
    Marcus Klein
    @kleini
    @camiloavil I want to use OTA with MQTT over TLS but I did not try lately. @nemidiy put several work into OTA, especially with MQTT over TLS: homieiot/homie-esp8266#648 Maybe that issue report has some more information to solve your problem.
    camiloavil
    @camiloavil
    @kleini that information es very usefull. Thanks. But I am not sure. Did you update a homie esp8266 over tls whit the changes for esp32 suscesfully? Because that was for esp32
    Marcus Klein
    @kleini
    I once updated some device successfully using OTA.
    Marcus Klein
    @kleini
    Just made a successful firmware update just now using the latest improvements of @bertmelis in the develop branch of async-mqtt-client.
    Bert Melis
    @bertmelis
    @kleini lovely to hear. I didn't try OTA myself yet.
    torbensp
    @torbensp
    Hi All,
    I am trying to compile one of the examples for the ESP32 but I am getting a ton of compiler errors. I these something you need to be aware when compiling for ESP32 compared to ESP8266?
    Any examples etc. would also be appreciated.
    torbensp
    @torbensp
    In addition to above related to compiler error for ESP32, I have tried both "Development" version as well as version 3.0.1 but no luck. For the example code , I used "DoorSensor" and I am using PlatformIO!
    Marcus Klein
    @kleini
    @torbensp What compile errors do you get? Can you put them please in pastebin? CI of homie-esp8266 is able to successfully build for esp32dev. So there must be something wrong with your setup.
    torbensp
    @torbensp
    @kleini Thanks for taking time to look into this. Regarding compiler errors, please see https://pastebin.com/8P8WGy3s
    @kleini Regarding your comment "CI of homie-esp8266 is able to successfully build for esp32dev". What do you mean by "CI"?
    Lübbe Onken
    @luebbe
    Torben, CI stands for continuous integration. If you look at http://homieiot.github.io/homie-esp8266, you’ll see the “build passing” badge, which means that all demo projects were built successfully.
    torbensp
    @torbensp
    @luebbe Thanks for clarifying the CI term as well as providing the link which have given me good insight into the compiler output for working examples. Based on @kleini advise on issue with system setup and difference in compiler output, I decided to uninstall PlatformIO and completely remove the .platformio folder. After re-installing PlatformIO I am indeed able to compile the "DoorSensor" example with only a few warnings! Thanks for the help :-)
    Lübbe Onken
    @luebbe
    Maybe you overdid it by uninstalling PlatformIO ;) There is always a .pio/libdeps folder in your project directory. This can contain outdated libraries from previous tries. Most of the time it is sufficient to just delete the libdeps.
    Igor
    @igrowing
    Hi guys, Sharing with you another Homie-based project:
    https://github.com/igrowing/esp8266_smart_home_ready/tree/master/modules/petard
    Pet water fountain.
    The documentation is in progress. One more feature isn't implemented yet :)
    Lübbe Onken
    @luebbe
    Now that's cool :)
    camiloavil
    @camiloavil

    Hi Everyone. i am guessing there is a solution for this problem but I dont know it yet, well I hope. I created a property of a node, this property is set like this advertise("tdelay").setName("Delay").setFormat("10:1800").setRetained(true).setDatatype("integer").settable(); and it works. but when my device reboots the value is lost, even when the mqtt broker keeps the info I guess because "setRetained(true)". maybe is necessary load the value from mqtt when the device reboots? is there a way to do that? or maybe save the value in the config file? I hope you can tell me if there is a way ?

    another question I dont get why this "setFormat("10:1800")" is this attribute do something or I can ignore it.

    thanks a lot again

    Lübbe Onken
    @luebbe
    There is an old discussion about this subject: homieiot/homie-esp8266#313
    Right now, if you want to persist something, you should either use the config or store it on the devices fs yourself.
    This "setFormat("10:1800")" is information for other devices that want to talk to your device. You are telling them, that a valid range (accepted by your device or sent by your device) is "10:1800", provided that the other device knows how to parse this information.
    camiloavil
    @camiloavil
    thank you @luebbe for the answers