Navigation

    • Register
    • Login
    • Search
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. waspie
    3. Topics
    • Continue chat with waspie
    • Start new chat with waspie
    • Flag Profile
    • Profile
    • Following
    • Followers
    • Blocks
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by waspie

    • [SOLVED] ds18b20 vs si7021 loss of granularity in measurement
      Troubleshooting • • waspie

      9
      0
      Votes
      9
      Posts
      207
      Views

      @yveaux Thanks for the hint and explanation. I appreciate that! I always used the search term: "conversion" (English is not my native language). I tried "casting" in combination with "c#" and I was almost immediately directed to my favorit c++ internet source (cplusplus.com) http://www.cplusplus.com/doc/tutorial/typecasting/ Many thanks! Boozz
    • Questions regarding smartsleep/request heartbeat/request ack?
      OpenHAB • • waspie

      3
      0
      Votes
      3
      Posts
      189
      Views

      @timo said in Questions regarding smartsleep/request heartbeat/request ack?: I'm using rules to detect if a thing changes its status to offfline You wrote the 2.4.0 binding, right? If so...I'm getting this error if I add a Mysensors MQTT GW while mysgw is not running: 12:51:49.096 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:13cd0a37' changed from INITIALIZING to OFFLINE 12:52:02.804 [ERROR] [ransport.mqtt.internal.ClientCallback] - MQTT message received. MqttMessageSubscriber#processMessage() implementation failure java.lang.NullPointerException: null at org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection$MySensorsMqttSubscriber.processMessage(MySensorsMqttConnection.java:134) ~[?:?] at org.eclipse.smarthome.io.transport.mqtt.internal.ClientCallback.lambda$3(ClientCallback.java:90) ~[207:org.eclipse.smarthome.io.transport.mqtt:0.10.0.oh240] at java.util.ArrayList.forEach(ArrayList.java:1257) ~[?:?] at org.eclipse.smarthome.io.transport.mqtt.internal.ClientCallback.messageArrived(ClientCallback.java:90) [207:org.eclipse.smarthome.io.transport.mqtt:0.10.0.oh240] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.deliverMessage(CommsCallback.java:499) [206:org.eclipse.paho.client.mqttv3:1.2.0] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:402) [206:org.eclipse.paho.client.mqttv3:1.2.0] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:206) [206:org.eclipse.paho.client.mqttv3:1.2.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] This is a quite vanilla install with only the Mysensors binding for testing.
    • Problem with battery powered temperature sensor
      Development • • waspie

      8
      0
      Votes
      8
      Posts
      425
      Views

      Hi, @waspie ! First of all i'd like to say about value "85" - according to DS18B20 datasheet page 6, note after table 4.1: *The power-on reset value of the temperature register is +85°C. Your code looks fine and similar to my mains-powered DS18B20 sensor (because we used same example). I have some thoughts: you may have power problems: a. from logs i see that you have 1 sensor, but you left defined #define MAX_ATTACHED_DS18B20 16 . If (suddenly) you would have 16 sensors - when you ask them for conversion they would consume 16* 1.5mA(max at 5v) = 24mA which is above recomended 20mA for atmega pin b. you are powering from battery: DS18B20 oficially requres minimum of 3 v (as for datasheet). People say that with lower voltage it may have strange readings or even do not work at all c. you are powering from battery through pin: is voltage raise fast enougth before start reading? is voltage drop low enought so voltage supplied to ds18b20 is >=3v? i'd suggest you to measure voltages (but multimeter won't show you short drop-outs when start conmsuming) and try to feed VCC of DS18b20 directly from power source. If not possible - at least measure voltage and try to add some wait() after powering up pin (or also before measure start or after sleep). When running from 3v, what frequency of atmega processor is? If it is 16mHz - that it is not in safe operating area for that voltage. you should run 8 mHz. (>=2.4v for 8mHz and >=3.78v for 16mHz) Also i suggest you try to change sleep(conversionTime); with wait(conversionTime); and check if it will change anything (especially when ds18b20 directly powered from source). Also try with fresh batteries. If nothing helped, then for "85" value simple solution will be if (temperature != 85) send(); because it is very rarely that people need to measure 85 degrees of Celsius at home... ~~ ~~ For advanced battery-powering i highly recommend to read this. Also you can find there about frequency vs voltage. And for internal battery voltage reading: i don't remember where i found it: here1 or here2 or somwhere else.. but you may want to get more accurate readings by measuring and setting Internal Reference Voltage value and using it in the code, and give it some time to stabilize and/or use some type of averaging.
    • Battery powered motor actuator?
      Development • • waspie

      4
      0
      Votes
      4
      Posts
      278
      Views

      @waspie almost. The gateway does not store anything though. Storage is handled by the controller.