Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. UweK
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by UweK

    • UweK

      ESP8266 Gateway with AP mode instead of hardcoded ssid etc
      Development • • UweK  

      7
      0
      Votes
      7
      Posts
      518
      Views

      kimot

      But if you move ( or sold ) your gateway to different network, what seems as reason for selecting SSID and password, you still need recompile your code due to different IP of your controller.
    • UweK

      Update Issues from Master request(...)
      Troubleshooting • • UweK  

      19
      0
      Votes
      19
      Posts
      1093
      Views

      UweK

      Hi all I solved this issue, this is the solution: I am using wait with additional parameter to wait 1000ms OR for a specific data packet from fhem. This works well! Now i don't need to write into EEPROM, after reboot the node is requesting actual status of the relays from fhem. //request status of Relais 1 request(CHILD_ID_Rel1, V_WATT,0); wait(1000,1,2); //request status of Relais 2 request(CHILD_ID_Rel2, V_WATT,0); wait(1000,1,2); Another "enhancement": I am using the Power readings to set/reset relays and i use the status reading to get the actual status back. I guess this was the initial logic of the fhem modul, but as power only produce a "1" as setpoint, i changed it to "on,off", equal the Power reading. The primitive setup in fhem looks like thios: defmod MYSENSOR_100 MYSENSORS_DEVICE 100 attr MYSENSOR_100 DbLogExclude .* attr MYSENSOR_100 IODev mysensors attr MYSENSOR_100 mapReading_armed3 3 armed attr MYSENSOR_100 mapReading_armed4 4 armed attr MYSENSOR_100 mapReading_armed5 5 armed attr MYSENSOR_100 mapReading_level4 4 level attr MYSENSOR_100 mapReading_level5 5 level attr MYSENSOR_100 mapReading_power1 1 power attr MYSENSOR_100 mapReading_power2 2 power attr MYSENSOR_100 mapReading_status1 1 status attr MYSENSOR_100 mapReading_status2 2 status attr MYSENSOR_100 mapReading_tripped3 3 tripped attr MYSENSOR_100 mapReading_tripped4 4 tripped attr MYSENSOR_100 mapReading_tripped5 5 tripped attr MYSENSOR_100 mode node attr MYSENSOR_100 requestAck 1 attr MYSENSOR_100 room mysensor attr MYSENSOR_100 setReading_power1 on,off attr MYSENSOR_100 setReading_power2 on,off attr MYSENSOR_100 setReading_status1 on,off attr MYSENSOR_100 setReading_status2 on,off attr MYSENSOR_100 showtime 1 attr MYSENSOR_100 timeoutAlive 240 attr MYSENSOR_100 verbose 5 setstate MYSENSOR_100 alive setstate MYSENSOR_100 2019-04-22 10:54:10 R_RSSI_from_Parent -89 setstate MYSENSOR_100 2019-04-22 10:54:09 R_RSSI_to_Parent -82 setstate MYSENSOR_100 2019-04-22 10:54:11 R_TX_Powerlevel_Pct 100 setstate MYSENSOR_100 2019-04-22 10:54:11 R_TX_Powerlevel_dBm 13 setstate MYSENSOR_100 2019-04-22 10:54:12 R_Uplink_Quality -89 setstate MYSENSOR_100 2019-04-20 21:20:19 SKETCH_NAME Klingelmodul setstate MYSENSOR_100 2019-04-20 21:20:19 SKETCH_VERSION 1.1 setstate MYSENSOR_100 2019-04-22 11:01:15 heartbeat last setstate MYSENSOR_100 2019-04-22 11:01:14 level4 -93 setstate MYSENSOR_100 2019-04-22 11:01:15 level5 -88 setstate MYSENSOR_100 2019-04-20 21:20:19 parentId 0 setstate MYSENSOR_100 2019-04-21 22:49:37 power1 on setstate MYSENSOR_100 2019-04-20 21:32:44 power2 on setstate MYSENSOR_100 2019-04-22 11:01:15 state alive setstate MYSENSOR_100 2019-04-21 22:49:37 status1 1 setstate MYSENSOR_100 2019-04-20 21:32:45 status2 1 setstate MYSENSOR_100 2019-04-22 10:48:49 tripped3 off tripped3 is my Input from the Doorbell. Ok, guys, 1000 thanks for your help! BR Uwe