Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

hvacThermostat thing missing V_STATUS binary switch?

aivarl last edited by

Hi,

I'm using Arduino/MySensors as thermostat and wanted to integrate it with OpenHAB as HVAC sensor type (temperatures, heating modes and status - on/off).

However it seems that OpenHAB binding thing definition for hvacThermostat has only either string or number type channels and missing basic binary switch channel. In MySensors serial protocol S_HVAC has relation to V_STATUS type.

So currently I'm trying to use V_HVAC_FLOW_STATE for indicating heating status but this seems not to work when mapped to Switch item in OpenHAB side:

Switch FF_Bedroom_Heating_State "Bedroom heating state [MAP(on_off_switch_ee.map):%s]" (gHVAC, gFF_BedroomHeatingState, gHistory) {channel="mysensors:hvacThermostat:gateway:ff_bedroom_temp:hvac-flow-state"}
Thing defined as: hvacThermostat ff_bedroom_temp [ nodeId="10", childId="31" ]

From debug output it is seen that MySensors messages are correctly sent and received but no item state is changed in OpenHAB side. I tried to send binary true/false values and also with "ON"/"OFF" strings.

Temperature is received and processed by OpenHAB correctly so thing definition and item definitions is most likely correct.

So my question is, is it possible to add V_STATUS to hvacThermostat definition or do I miss something in my configuration?

wbr,
Aivar
Reply Quote 0
1 Reply Last reply

1
Posts

762
Views

Suggested Topics

Boxes and Enclosures
Enclosures / 3D Printing • • PITP2

22

0
Votes

22
Posts

14855
Views

To add another option to this thread. I have not yet used them but I am collecting these. They look like they are made for these types of sensors
voltage sensor via esp and mqtt
OpenHAB • • muhammed

1

0
Votes

1
Posts

26
Views

No one has replied
OH3, RPi3, GPIO-NRF24 gateway. MySensors binding (ETH or MQTT?)
OpenHAB • • perIpI

2

0
Votes

2
Posts

34
Views

Replying myself after more reading and testing. *MQTT vs ETH probably is equivalent in my system, if the choice if given I think MQTT is preferred. *NRF24 or RFM69, maybe both as I already have a bunch of NRF24 radios home and can start build directly. *PC based MQTT could be an idea, but probably its as easy to work through an Arduino-example using the serial monitor in an Arduino-environment. My way forward will be: Remove the RPi-GPIO-gateway (I built a basic node and tested it, but could not communicate with the GW) and replace it with ESP8266-based WIFI/MQTT/Radio-gateway (one with NRF24 and eventually one with RFM69). I believe that will be an easier way into mySensors-world also limiting the amount of required Linux-related knowledge. It will be easier to debug the system from Arduino IDE-serial console. Ie start and confirm OH3 to MySensors-MQTT-gateway, then proceeding with sensor to gateway communication etc.
openHAB 2.2 binding
OpenHAB • • TimO

132

3
Votes

132
Posts

58135
Views

The 2.5-version of the binding does not work out of the box in OpenHAB 3 for me. 2020-12-22 22:53:34.555 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.mysensors-2.5.0-SNAPSHOT.jar org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.mysensors [272] Unresolved requirement: Import-Package: org.eclipse.smarthome.config.core at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?] at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4] at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4] at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4] at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4] I guess it might have something to do with this? https://community.openhab.org/t/guide-binding-development-changes-for-openhab-3-from-2-5-x/104134 Namespace change of openHAB core classes With the migration of Eclipse Smart Home to openHAB the namespace of all classes in openHAB core needed to be changed. This means all imports done by bindings that refer to org.eclipse.smarthome have been changed to org.openhab.core. With your binding code you can simply do a file level replace of this text string in the java source files to migrate the binding. On linux you can use the following commands in you src/main/java directory: find . -name *.java -exec sed -i "s/org.eclipse.smarthome.core/org.openhab.core/g" {} ; find . -name *.java -exec sed -i "s/org.eclipse.smarthome/org.openhab.core/g" {} ;
openhab binding mysensors
OpenHAB • • MDS

3

0
Votes

3
Posts

65
Views

@ncollins Great! Seem the problem is the delay. With 1 ms or 100 ms I have double message, but with 200 ms I only one message. Thanks a lot.
MQTT losing messages...
OpenHAB • • ben999

7

0
Votes

7
Posts

59
Views

@ben999 Check out Serial Protocol I have four Arduinos. Each has a different MY_NODE_IDs (I use 130, 131, 132, 133). Each has four sensors: moisture, humidity, temperature, and voltage each of which has a CHILD_ID: CHILD_ID_MOISTURE is 0 , CHILD_ID_HUMIDITY is 1, CHILD_ID_TEMPERATURE is 2, CHILD_ID_VOLTAGE is 3. When an Arduino makes a measurement, it sends that measurement to a unique MQTT topic. In the case of the Arduino with MY_NODE_ID of 130 that is sending the moisture measurement, that MQTT topic is mysensors_out/130/0/1/0/35 and the message is [something like] 760 (35 is the value type) Similarly, when a controller sends a command to a device (Arduino), the topic is unique. If you have two actuators with the same MY_NODE_ID and CHILD_ID (MQTT topic) there would be confusion as to what you want each actuator to do. Likewise, if two sensors had the same MQTT topic, how would the controller know how to handle the data.

hvacThermostat thing missing V_STATUS binary switch?

Suggested Topics

Boxes and Enclosures
Enclosures / 3D Printing • • PITP2

voltage sensor via esp and mqtt
OpenHAB • • muhammed

OH3, RPi3, GPIO-NRF24 gateway. MySensors binding (ETH or MQTT?)
OpenHAB • • perIpI

openHAB 2.2 binding
OpenHAB • • TimO

openhab binding mysensors
OpenHAB • • MDS

MQTT losing messages...
OpenHAB • • ben999

69
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

hvacThermostat thing missing V_STATUS binary switch?

Suggested Topics

Boxes and Enclosures Enclosures / 3D Printing • • PITP2

voltage sensor via esp and mqtt OpenHAB • • muhammed

OH3, RPi3, GPIO-NRF24 gateway. MySensors binding (ETH or MQTT?) OpenHAB • • perIpI

openHAB 2.2 binding OpenHAB • • TimO

openhab binding mysensors OpenHAB • • MDS

MQTT losing messages... OpenHAB • • ben999

69Online

11.4kUsers

11.1kTopics

112.7kPosts

Boxes and Enclosures
Enclosures / 3D Printing • • PITP2

voltage sensor via esp and mqtt
OpenHAB • • muhammed

OH3, RPi3, GPIO-NRF24 gateway. MySensors binding (ETH or MQTT?)
OpenHAB • • perIpI

openHAB 2.2 binding
OpenHAB • • TimO

openhab binding mysensors
OpenHAB • • MDS

MQTT losing messages...
OpenHAB • • ben999

69
Online

11.4k
Users

11.1k
Topics

112.7k
Posts