Posts made by andreground

@TimO

Thanks!
This should fit for OH2!

Do you know if something similar exists also for OH1?

Hi guys!

I’m happily using the openHAB connectors to control my sensors through both openhab1 and openhab2.

Today, while I was developing a new sketch, I realized that I needed to periodically send a request message to my sensor to receive back in updated value.

I didn’t find a way to sort this out!

Is there anything I can do to have either openhab1 or 2 managing this?

Thanks in advance!

Ethernet gw binding source seems to be missing in github repo.

Any clue?

Thanks

: Compilation failure:
[ERROR] /root/openhab/bundles/binding/org.openhab.binding.mysensors/src/main/java/org/openhab/binding/mysensors/internal/MySensorsBinding.java:[17]
[ERROR] import org.openhab.binding.mysensors.internal.gateway.Ethernet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.openhab.binding.mysensors.internal.gateway.Ethernet cannot be resolved
[ERROR] /root/openhab/bundles/binding/org.openhab.binding.mysensors/src/main/java/org/openhab/binding/mysensors/internal/MySensorsBinding.java:[117]
[ERROR] gateway = new Ethernet(prop.getProperty("host"), Integer.parseInt(prop.getProperty("port", "5003")));
[ERROR] ^^^^^^^^
[ERROR] Ethernet cannot be resolved to a type
[ERROR] 2 problems (2 errors)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.openhab.binding.mysensors

@tekka thanks, it works.

2 more questions:

1. Should the clearing eeprom function in MYSBootloader be working?
2. From what I understand, Watchdog is enabled by default (8S timeout) in the bootloader; that means that I've to either call wdt_reset in my loop or call wdt_disable in setup to prevent unexpected reboots. Am i right?

@tekka

First of all, thanks for working so hard on the new version of the BL.

My setup:

• MYSBootloader 1.3.0-beta3 (md5 49ef3dc263110613c9c25ac21a8c3d83)
• MYSController 1.0.0.beta (updated to latest version)
• GW on Arduino Nano
• Node on Arduino Pro Mini @ 5V 16 Mhz with MockMySensors sketch running

What I did:

• Flashed latest bootloader version from github on the Pro Mini ATMEGA328P (using AVRDUDESS 2.4 & USBasp, fuses L: 0xFF, H: 0xDA, E: 0x05)
• Flashed latest mysensors lib on both node & gw (tested with both 2.0.0 & 2.1) on the Nano

What I got:

• FW upgrade through MYSController: Working
• Reboot through MYSController: Working
• Serial flashing with Arduino IDE: Working
• Request presentation through MYSController: Working
  Request heartbeat through MYSController: Working

But...

Reassign ID through MYSController: NOT WORKING (the node reboots but still preserves the old ID)
(MY_NODE_ID IS NOT DEFINED / THUS SET AS AUTO AS PER MYSENSORS DEFAULTS)
Clear EEPROM through MYSController: NOT WORKING (the node reboots but still holds the value saved in EEPROM using saveState)

Node bootlog after Clear EEPROM from MYSBootloader (you can see my debug LOADSTATE which still loads the value 123 from EEPROM):

Starting sensor (RNNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=4)
TSM:FPAR
TSP:MSG:SEND 4-4-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 150-150-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
TSP:MSG:BC
TSP:MSG:READ 0-0-4 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=4)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 4-4-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-4 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
GW Started
LOADSTATE
123

And...is it expected that the "Info" tab on my node shows bootloader version 1.2?

Is there anything I'm missing to have these features working?

Thanks in advance