Navigation

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

    Posts made by tortoisedoc

    • RE: PiDome Domotica/Home Automation

      @John said:

      @tortoisedoc The solution then would be build one with a crystal, or keep on using the lower speed. I personally had no problems with data running at 57k

      @John I will definietly keep the 57 K ; it should be enough as the data transfered is minimal. I plan to add another 5 sensors at least, but I believe it should be ok.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John both board and FTDI are from sparkfun...I believe that is the official maker? But yes, this is exactly the same type of problem I have.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John Okay! Making progress here; after digging and digging, it appears my FTDI module is funky; as in, 115200 Baud seem to somehow be a problem for it.
      I made a quick test sketch where arduino increases a counter and writes out the current value, and i have the possibility to reset the value (between 1 and 9). Well, it works properly only up to 57600 baud. Weird. I will test a version of the mysensors @ 57600 Baud now.

      EDIT AND IT WORKS! COME ON :D!

      capture.png

      This is interesting indeed. I wonder how it comes baud rate 115k fails the FTDI (note : both on PC AND RPi)...

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Unable to use the SerialGateway code

      @hek : it happens that I have currently the same setup (3.3v mini pro as serial gw via FTDI); and am suffering from exactly the same symptoms (no reaction when I push commands to the GW). Reception, however, is ok. I plan to add a capacitor for the ripple; but given incoming reception is ok, I doubt it will make a difference?
      Needless to say that uploading the sketch works fine, and that upon writing the TX led flimmers.

      EDIT : nevermind, solved.

      posted in Troubleshooting
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John I think I just found something interesting here, which might actually match my case:

      [quote]
      I've tried two different pro mini 3,3v boards, and the SerialGateway does not respond to serial commands on them. I expect 0;0;4;4; to reply the firmware version of the serial gateway. And it works fine on non-3,3V-pro-mini. The vera lua script is doing the same on startup:
      [/quote]

      from :

      http://forum.mysensors.org/topic/66/unable-to-use-the-serialgateway-code/4

      I will dig a little into this before performing more tests.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John said:

      @tortoisedoc and @ceburge The builds on the build server are still test builds regarding discovery and driver web front end API. They are getting more stable but is still a work in progress. The builds which are following up are tests to test the progress of the current development roadmap regarding these.

      This is a known issue and am working on it while the development progresses.

      Excuse for any inconvenience, hope to have this functionality done asap.

      P.S. I'm looking into the possibility to also have the node address requests being passed to the discovery collection page, all though it is a complete different internal process trying to make it coherent.

      Sounds great !
      Thank you for your efforts!

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John said:

      @tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.

      @John Ok, here more logging:
      appLog.txt

      There is actually data coming in - but the visual part is empty both in the driver's section as well as the "new" section for non-discovered devices.

      PS I tested this in Chrome as well as in Firefox;

      and the result is empty : capture.png

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John said:

      @tortoisedoc Are you able to use the node assignment?

      Unfortunately not.

      See here: appLog.txt
      At this point, im starting to suspect about the PI. The miniterm shows correctly the gateway startup tho.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John thanks for the fix, will test it later today. Is the latest build still good to go?

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John Okay. Seems we have something here now; see the attached log here:

      appLog.txt

      in particular :
      2014-12-15 21:55:59,811 [USB-discovery] INFO org.pidome.server.system.hardware.drivers.Drivers - Something went wrong width the hardware: MEthod does not support NID to request driver.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Sensor radio vs Bluetooth ?

      @tbowmo said:

      @tortoisedoc

      Have you tried decoupling the radio in both ends with something like 4.7uF low ESR capacitor?

      Search the forum, there's lot's of advices.

      In my particular case sending by the gw seems to be the problem.
      I will try this trick with the capacitor as well, thanks!

      posted in Troubleshooting
      tortoisedoc
      tortoisedoc
    • RE: Sensor radio vs Bluetooth ?

      @tbowmo said:

      Bluetooth uses frequency hopping, so it never stays at the same frequency for that long,

      That being said, it could interfere slightly.. could jam the input in the nrf, if they are very close to each other, not because it transmits on the same frequency, but in the same band. If a high signal is received on adjacent channels, the radio might loose some sensitivity.

      You could try to use one of the higher frequencies that the NRF supports (I think it can go above 2.5Ghz, which is outside the bluetooth spectrum). Also you could try to turn off the bluetooth first, and see if that helps on radio sensitivity

      Thanks for your answer
      I will try with the bluetooth off.

      Any other suggestion on how to debug communication between gateway & Sensors?
      Thanks!

      posted in Troubleshooting
      tortoisedoc
      tortoisedoc
    • Sensor radio vs Bluetooth ?

      Hey;
      I have reason to believe my laptop's bluetooth to be interferring with gateway/sensor communication. Is this possible? At least technically, as the nrf24 relies on 2.4Ghz (same as Bluetooth), this sounds plausible. Has anyone experinced this?

      posted in Troubleshooting
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John Update:
      two things.

      1. the "Waiting for Gateway" is still here, even tho the gateway seems to be correctly receiving & sending data
        capture.png
      2. it appears the bluetooth of my laptop might potentially be jamming with the sensor radio signal. Is this possible? Knowing the protocols share the same radio band (2.4 ghz)? Or am I hallucinating?
      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      Ok, got ahold of some more components and am back up testing!

      One question : is the value displayed in the drop-down box correct?
      This appears once I try to connect the sensor.

      capture.png

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John pardon my ignorance - can I just send by typing in miniterm or is there some special character sequence to be used before I can do so?
      EDIT : Wrote a python program; data is going out (TX led on FTDI flashes right after writing) but has no effect. Funnily, miniterm does NOT see the written data passing by...

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John Yeah, well, seems trusting teh internet is not cutting it anymore (up to 12 V should be supported on the RAW-in according to the arduino website). But meh! One of the two is not dead yet, I can still power it on (and it works!).
      So here some miniterm.py data with the build of 8.12:
      Notice the "25" in front of the 255 (with the "stable" build it was 255)!

      --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 ---
      --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
      0;0;3;0;;read: 25-255-0 s255,c=3,=3,pt=0,=0:
      255;55;3;03;
      0;0;3;0;;read: 25-255-0 s255,c=3,=3,pt=0l=0:
      255255;3;0;;
      0;0;3;0;;read: 25-255-0 =255,c3,t=3,pt=0l=0:
      255;55;3;0;3;Exception in thread Thread-1:
      Traceback (most recent call last):
      File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
      self.run()
      File "/usr/lib/python2.7/threading.py", line 505, in run
      self.__target(*self.__args, **self.__kwargs)
      File "/usr/bin/miniterm.py", line 200, in reader
      data = self.serial.read(1)
      File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 456, in re ad
      raise SerialException('device reports readiness to read but returned no data (device disconnected?)')
      SerialException: device reports readiness to read but returned no data (device d isconnected?)

      Seems also the miniterm is not cutting it for some reason (port disconnected?)

      BUT still no success yet. Node keeps on asking for new ID...next, will generate a trace dump...

      ================== BEGIN ===================

      2014-12-09 13:24:03,320 [Thread-12] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 65 byte(s)
      2014-12-09 13:24:03,324 [Thread-12] TRACE org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Received from hardware driver: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      255;255;3;0;3;
      2014-12-09 13:24:03,338 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:03,340 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:03,344 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;
      2014-12-09 13:24:04,122 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - GET /jsonrpc.json?rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22HardwareService.getSoftwareDriverPresentation%22,%20%22params%22:%20{%22port%22:%22/dev/ttyUSB0%22}%20%22id%22:%22HardwareService.getSoftwareDriverPresentation%22}&=1418131338168 HTTP/1.1
      2014-12-09 13:24:04,138 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Host: 192.168.1.6:8080
      2014-12-09 13:24:04,141 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Connection: keep-alive
      2014-12-09 13:24:04,148 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept: /
      2014-12-09 13:24:04,151 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - X-Requested-With: XMLHttpRequest
      2014-12-09 13:24:04,159 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36
      2014-12-09 13:24:04,174 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Referer: http://192.168.1.6:8080/desktop/index.html
      2014-12-09 13:24:04,181 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Encoding: gzip, deflate, sdch
      2014-12-09 13:24:04,185 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Language: en-US,en;q=0.8
      2014-12-09 13:24:04,198 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Cookie: key=3e148748-34e5-4ce6-8336-fcd5c8aaa0af
      2014-12-09 13:24:04,203 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler -
      2014-12-09 13:24:04,206 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Having header collection: {REQUEST=/jsonrpc.json, PLAINFILE=jsonrpc, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=json, QUERYSTRING=rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22HardwareService.getSoftwareDriverPresentation%22,%20%22params%22:%20{%22port%22:%22/dev/ttyUSB0%22}%20%22id%22:%22HardwareService.getSoftwareDriverPresentation%22}&
      =1418131338168}
      2014-12-09 13:24:04,214 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.1.24 - GET: /jsonrpc.json
      2014-12-09 13:24:04,243 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Complete constructed from header: {REQUEST=/jsonrpc.json, PLAINFILE=jsonrpc, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=json, QUERYSTRING=rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22HardwareService.getSoftwareDriverPresentation%22,%20%22params%22:%20{%22port%22:%22/dev/ttyUSB0%22}%20%22id%22:%22HardwareService.getSoftwareDriverPresentation%22}&=1418131338168}
      2014-12-09 13:24:04,249 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Get query data: {rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22HardwareService.getSoftwareDriverPresentation%22,%20%22params%22:%20{%22port%22:%22/dev/ttyUSB0%22}%20%22id%22:%22HardwareService.getSoftwareDriverPresentation%22}, =1418131338168}
      2014-12-09 13:24:04,268 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - JSON String to parse: {"jsonrpc": "2.0", "method": "HardwareService.getSoftwareDriverPresentation", "params": {"port":"/dev/ttyUSB0"} "id":"HardwareService.getSoftwareDriverPresentation"}
      2014-12-09 13:24:04,282 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Parsed JSON Object: {method=HardwareService.getSoftwareDriverPresentation, id=HardwareService.getSoftwareDriverPresentation, jsonrpc=2.0, params={port=/dev/ttyUSB0}}
      2014-12-09 13:24:04,295 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Set request id: HardwareService.getSoftwareDriverPresentation
      2014-12-09 13:24:04,298 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Searching named parameter set for getSoftwareDriverPresentation in HardwareService
      2014-12-09 13:24:04,301 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Found param key: port
      2014-12-09 13:24:04,317 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - searching for getSoftwareDriverPresentation in HardwareService
      2014-12-09 13:24:04,320 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Declared params for getSoftwareDriverPresentation : [class java.lang.String]
      2014-12-09 13:24:04,324 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Passed in params for 'getSoftwareDriverPresentation': [/dev/ttyUSB0]
      2014-12-09 13:24:04,334 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data={presentation=[{description=Information about the hardware used by this driver, title=Hardware link, content=[{label=Hardware, type=SIMPLE_NVP, content=Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC}, {label=Hardware port, type=SIMPLE_NVP, content=/dev/ttyUSB0}]}, {description=Gateway information, title=Gateway info, content=[{label=Version, type=SIMPLE_NVP, content=Waiting for gateway}, {label=Last receive time, type=SIMPLE_NVP, content=09-12-2014 14:24:03}, {label=Last send time, type=SIMPLE_NVP, content=09-12-2014 14:23:28}]}, {description=When a new node is added it will be displayed below. You will then have the option to add the node to the server. When in AUTO mode you can only add one sensor at a time. When using fixed addresses you can add multiple at the same time. Also, if you mix AUTO and fixed, always, but always add the fixed first otherwise the address allocations of the AUTO node can allocate a fixed one. It is required for the nodes to use presentation., title=New nodes presentation, content=[{label=Address request presentation, type=LIST_NVP, content=[]}, {label=Presentation, type=COMPLEX_NVP, content={255=[{custom_driver_function={identifier=newNodeRequest, function_label=Add sensor node, ADDRESS=2, function_id=customFunction}, 09-12-2014 14:24:03=New device: Possible new address: 2 if not occupied before adding (Restart node after assigning).}]}}]}, {description=Below is a list of last known 20 messages, title=Last known messages, content=[{label=Messages list, type=LIST_NVP, content=[{custom_driver_function={identifier=clearLogList, function_label=Clear log list, function_id=customFunction}}, {09-12-2014 14:24:03=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:49=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:15=Trying assigning address '2' to a new node}, {09-12-2014 14:23:15=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:12=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:10=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:08=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:04=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}, {09-12-2014 14:23:02=0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:}]}]}], driver=MySensors USB (serial) driver API 1.4, port=/dev/ttyUSB0, hardware=Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC}, success=true, message=}
      2014-12-09 13:24:05,329 [Thread-12] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 65 byte(s)
      2014-12-09 13:24:05,333 [Thread-12] TRACE org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Received from hardware driver: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      255;255;3;0;3;
      2014-12-09 13:24:05,336 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:05,339 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:05,342 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;
      2014-12-09 13:24:07,337 [Thread-12] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 65 byte(s)
      2014-12-09 13:24:07,340 [Thread-12] TRACE org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Received from hardware driver: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      255;255;3;0;3;
      2014-12-09 13:24:07,343 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:07,346 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:07,350 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;
      2014-12-09 13:24:07,790 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - GET /jsonrpc.json?rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22DeviceService.peripheralDeviceFunction%22,%20%22params%22:%20{%22peripheralport%22:%22/dev/ttyUSB0%22,%22params%22:{%22identifier%22:%22newNodeRequest%22,%22function_label%22:%22Add%20sensor%20node%22,%22ADDRESS%22:%222%22,%22function_id%22:%22customFunction%22}}%20%22id%22:%22DeviceService.peripheralDeviceFunction%22}&
      =1418131338169 HTTP/1.1
      2014-12-09 13:24:07,795 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Host: 192.168.1.6:8080
      2014-12-09 13:24:07,800 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Connection: keep-alive
      2014-12-09 13:24:07,803 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept: /
      2014-12-09 13:24:07,807 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - X-Requested-With: XMLHttpRequest
      2014-12-09 13:24:07,812 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36
      2014-12-09 13:24:07,815 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Referer: http://192.168.1.6:8080/desktop/index.html
      2014-12-09 13:24:07,818 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Encoding: gzip, deflate, sdch
      2014-12-09 13:24:07,822 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Language: en-US,en;q=0.8
      2014-12-09 13:24:07,825 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Cookie: key=3e148748-34e5-4ce6-8336-fcd5c8aaa0af
      2014-12-09 13:24:07,838 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler -
      2014-12-09 13:24:07,841 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Having header collection: {REQUEST=/jsonrpc.json, PLAINFILE=jsonrpc, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=json, QUERYSTRING=rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22DeviceService.peripheralDeviceFunction%22,%20%22params%22:%20{%22peripheralport%22:%22/dev/ttyUSB0%22,%22params%22:{%22identifier%22:%22newNodeRequest%22,%22function_label%22:%22Add%20sensor%20node%22,%22ADDRESS%22:%222%22,%22function_id%22:%22customFunction%22}}%20%22id%22:%22DeviceService.peripheralDeviceFunction%22}&
      =1418131338169}
      2014-12-09 13:24:07,844 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.1.24 - GET: /jsonrpc.json
      2014-12-09 13:24:07,854 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Complete constructed from header: {REQUEST=/jsonrpc.json, PLAINFILE=jsonrpc, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=json, QUERYSTRING=rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22DeviceService.peripheralDeviceFunction%22,%20%22params%22:%20{%22peripheralport%22:%22/dev/ttyUSB0%22,%22params%22:{%22identifier%22:%22newNodeRequest%22,%22function_label%22:%22Add%20sensor%20node%22,%22ADDRESS%22:%222%22,%22function_id%22:%22customFunction%22}}%20%22id%22:%22DeviceService.peripheralDeviceFunction%22}&=1418131338169}
      2014-12-09 13:24:07,859 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Get query data: {rpc={%22jsonrpc%22:%20%222.0%22,%20%22method%22:%20%22DeviceService.peripheralDeviceFunction%22,%20%22params%22:%20{%22peripheralport%22:%22/dev/ttyUSB0%22,%22params%22:{%22identifier%22:%22newNodeRequest%22,%22function_label%22:%22Add%20sensor%20node%22,%22ADDRESS%22:%222%22,%22function_id%22:%22customFunction%22}}%20%22id%22:%22DeviceService.peripheralDeviceFunction%22}, =1418131338169}
      2014-12-09 13:24:07,864 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - JSON String to parse: {"jsonrpc": "2.0", "method": "DeviceService.peripheralDeviceFunction", "params": {"peripheralport":"/dev/ttyUSB0","params":{"identifier":"newNodeRequest","function_label":"Add sensor node","ADDRESS":"2","function_id":"customFunction"}} "id":"DeviceService.peripheralDeviceFunction"}
      2014-12-09 13:24:07,869 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Parsed JSON Object: {method=DeviceService.peripheralDeviceFunction, id=DeviceService.peripheralDeviceFunction, jsonrpc=2.0, params={peripheralport=/dev/ttyUSB0, params={identifier=newNodeRequest, function_label=Add sensor node, ADDRESS=2, function_id=customFunction}}}
      2014-12-09 13:24:07,872 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Set request id: DeviceService.peripheralDeviceFunction
      2014-12-09 13:24:07,875 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Searching named parameter set for peripheralDeviceFunction in DeviceService
      2014-12-09 13:24:07,878 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Found param key: peripheralport
      2014-12-09 13:24:07,881 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Found param key: params
      2014-12-09 13:24:07,884 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - searching for peripheralDeviceFunction in DeviceService
      2014-12-09 13:24:07,887 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Declared params for peripheralDeviceFunction : [class java.lang.String, interface java.util.Map]
      2014-12-09 13:24:07,890 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Passed in params for 'peripheralDeviceFunction': [/dev/ttyUSB0, {identifier=newNodeRequest, function_label=Add sensor node, ADDRESS=2, function_id=customFunction}]
      2014-12-09 13:24:07,894 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Sending internal message to device: '255;255;3;0;4;2'
      2014-12-09 13:24:07,899 [pool-11-thread-1] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - sending: [B@17ba9e8
      2014-12-09 13:24:07,902 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data=true, success=true, message=}
      2014-12-09 13:24:08,026 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - GET /desktop/driversedit.html?requesttype=ajax&
      =1418131338170 HTTP/1.1
      2014-12-09 13:24:08,029 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Host: 192.168.1.6:8080
      2014-12-09 13:24:08,032 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Connection: keep-alive
      2014-12-09 13:24:08,035 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept: text/html, /; q=0.01
      2014-12-09 13:24:08,039 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - X-Requested-With: XMLHttpRequest
      2014-12-09 13:24:08,046 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36
      2014-12-09 13:24:08,049 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Referer: http://192.168.1.6:8080/desktop/index.html
      2014-12-09 13:24:08,053 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Encoding: gzip, deflate, sdch
      2014-12-09 13:24:08,056 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Accept-Language: en-US,en;q=0.8
      2014-12-09 13:24:08,059 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Cookie: key=3e148748-34e5-4ce6-8336-fcd5c8aaa0af
      2014-12-09 13:24:08,064 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler -
      2014-12-09 13:24:08,067 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Having header collection: {REQUEST=/desktop/driversedit.html, PLAINFILE=desktop/driversedit, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=html, QUERYSTRING=requesttype=ajax&
      =1418131338170}
      2014-12-09 13:24:08,070 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.1.24 - GET: /desktop/driversedit.html
      2014-12-09 13:24:08,073 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Complete constructed from header: {REQUEST=/desktop/driversedit.html, PLAINFILE=desktop/driversedit, METHOD=GET, HOST=192.168.1.6:8080, FILETYPE=html, QUERYSTRING=requesttype=ajax&_=1418131338170}
      2014-12-09 13:24:08,080 [WEBCLIENT:192.168.1.24] TRACE org.pidome.server.services.clients.http.HTTPClientHandler - Get query data: {requesttype=ajax, _=1418131338170}
      c2014-12-09 13:24:11,360 [Thread-12] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 65 byte(s)
      2014-12-09 13:24:11,363 [Thread-12] TRACE org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Received from hardware driver: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      255;255;3;0;3;
      2014-12-09 13:24:11,366 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:11,369 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-09 13:24:11,372 [Thread-12] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John said:

      Well, i was also quite busy today (doing some arduino style "modifications" to a slot car track with my son), so no problem, otherwise i had to excuse ;).

      But uhm.. you are quite, how do i call it, enthusiastic.. Take your time, i will ask around regarding the address assignments and gateway ready message. If you find something, just mail to support at the project name with dot org. This is watched more closely then the forum

      You mean because of the Arduinos or because of fast moving 😉

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John Sorry for the late reply;
      I just managed to fry two arduino's today thanks to my stubborness to try to get them powered with a 9V on RAW. So, I am stuck until I can find more arduinos 😕
      It appears the regulator can only take so much incoming current if the output current is very low (3.3V in my case). Otherwise, it will overheat and bang, that's it.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Sensors & Pi Dome Controller - Sensor ID assignment on AUTO mode not completing assignment of ID to sensor

      @John said:

      @tortoisedoc You can send the whole thing, no problem, if you would be so kind to try to add a location which gave you an issue that would be nice also, then i can pick that one up also

      Ok, Ill get to it tomorrow - pretty late now around here, unfortunately.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Sensors & Pi Dome Controller - Sensor ID assignment on AUTO mode not completing assignment of ID to sensor

      @John said:

      Well ,the log should also display the send command. You can start the server with a trace option in the command line. The server then only has to be started in a different way. When the server is stopped. start it with the server.sh shell file (probably you have to set 755 first). Commandline then is "./server.sh trace". Could you try to assign an address while trace is on and send me the log?

      Are the last 20 lines of log enough or the appLog file would be better?

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      About the GW : Yes, same settings than the pidome server (no parity, 1 stop bit, 115200 bauds, 8 data bits); you can see it from the screenshot.

      About the SPI : Great to hear! I can imagine switching from the USB driver to the SPI's should not be too much of a hassle; I wanted to have a look at the code myself (out of curiousity), but did not get to it yet.
      One question, I noticed the tty used is exclusively locked by the server once it is started;
      I believe it would be of great help to be able to access it at the same time as the pidome server, from the shell (say with miniterm.py), for debugging purpouses.

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      @John said:

      Sorry for the late response!

      No problem 🙂

      The server waits for a message from the gateway which tells the server it is ready to serve data. When you attach the gateway to your pc, and watch it in the terminal, do you see a "Gateway ready" message?

      John.

      Yes, as a matter of fact i do (via ssh -> miniterm.py on RPi)

      capture.png

      EDIT : I Just now realized this is not necessarily the "Gateway ready signal" 👯
      Btw is there support for mysensors from the RPi SIO pins? It would be great to not need to use the FTDI 🙂

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Sensors & Pi Dome Controller - Sensor ID assignment on AUTO mode not completing assignment of ID to sensor

      Thanks for the support guys, after re-checking the sensor, I am pretty positive this is a sensor power issue (i.e. I need more power 🙂 ).

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Sensors & Pi Dome Controller - Sensor ID assignment on AUTO mode not completing assignment of ID to sensor

      Thanks for the suggestion;
      tried, same result. Node keeps on askig for valid ID.

      Below is a list of last known 20 messages

      07-12-2014 18:30:48: Trying assigning address '2' to a new node
      07-12-2014 18:30:48: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:26:31: Trying assigning address '2' to a new node
      07-12-2014 18:26:31: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:49: Trying assigning address '2' to a new node
      07-12-2014 18:23:49: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:46: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:44: Trying assigning address '2' to a new node
      07-12-2014 18:23:44: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:42: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:38: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:36: Trying assigning address '2' to a new node
      07-12-2014 18:23:36: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 18:23:34: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: PiDome Domotica/Home Automation

      Hey;
      can someone pinpoint what the "Waiting for gateway" means?

      Thanks!
      capture.png

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • Sensors & Pi Dome Controller - Sensor ID assignment on AUTO mode not completing assignment of ID to sensor

      Testing PiDome as my controller;
      have succesfully connected arduino pro mini over ftdi module;
      broadcast msg from sensor comes in OK, and pidome asks for assignment of id correctly;
      unfortunately, when I assign the id, it appears to not be SET on the sensor node - i.e., it keeps on re-asking it by broadcasting messages.

      GW works ok from FTDI check via serial monitor,
      but in PiDome I get "Waiting for gateway" in Gateway information page Version field.
      Has anyone seen this before?

      Here the log from the pidome

      Below is a list of last known 20 messages

      07-12-2014 13:02:38: Trying assigning address '2' to a new node
      07-12-2014 13:02:38: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:59:25: Trying assigning address '1' to a new node
      07-12-2014 12:59:25: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:58:51: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:57:45: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:54:31: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:46:31: Trying assigning address '1' to a new node
      07-12-2014 12:46:31: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:42:45: Trying assigning address '1' to a new node
      07-12-2014 12:42:45: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:42:11: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:41:38: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:40:32: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:36:14: Trying assigning address '1' to a new node
      07-12-2014 12:36:14: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:35:40: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      07-12-2014 12:35:07: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:

      Some more logs from pidome:

      2014-12-07 13:12:38,735 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Declared params for peripheralDeviceFunction : [class java.lang.String, interface java.util.Map]
      2014-12-07 13:12:38,736 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Passed in params for 'peripheralDeviceFunction': [/dev/ttyUSB0, {identifier=newNodeRequest, function_label=Add sensor node, ADDRESS=3, function_id=customFunction}]
      2014-12-07 13:12:38,742 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Sending internal message to device: '255;255;3;0;4;3'
      2014-12-07 13:12:38,743 [pool-45-thread-1] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - sending: [B@8b0e52
      2014-12-07 13:12:38,746 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data=true, success=true, message=}
      2014-12-07 13:12:38,916 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.1.24 - GET: /desktop/driversedit.html
      2014-12-07 13:12:40,191 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-07 13:12:40,192 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-07 13:12:40,193 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;
      2014-12-07 13:12:43,022 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 0;0;INTERNAL;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-07 13:12:43,023 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Log request: 0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
      2014-12-07 13:12:43,024 [Thread-89] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Handling internal: 255;255;INTERNAL;3;

      And some more logging from pidome upon adding a sensor 👍

      2014-12-07 13:24:44,420 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - searching for peripheralDeviceFunction in DeviceService
      2014-12-07 13:24:44,421 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Declared params for peripheralDeviceFunction : [class java.lang.String, interface java.util.Map]
      2014-12-07 13:24:44,422 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Passed in params for 'peripheralDeviceFunction': [/dev/ttyUSB0, {identifier=newNodeRequest, function_label=Add sensor node, ADDRESS=3, function_id=customFunction}]
      2014-12-07 13:24:44,424 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Sending internal message to device: '255;255;3;0;4;3'
      2014-12-07 13:24:44,426 [pool-45-thread-1] DEBUG
      org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - sending: [B@12b9811
      2014-12-07 13:24:44,428 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data=true, success=true, message=}
      2014-12-07 13:24:44,525 [WEBCLIENT:192.168.1.24] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.1.24 - GET: /desktop/driversedit.html

      Is the highlighted line supposed to be correct?
      Btw, Pidome does not allow for location adding for me - an exception prevents me to do so 😕

      posted in PiDome
      tortoisedoc
      tortoisedoc
    • RE: Arduino Pro Mini vs Arduino Nano for SerialGateway?

      @hek : Thanks for the answers; just for my better understanding, so the code snippet (given in the wiki ) for configuring an Arduino Nano as Serial GW can be used for a mini pro as well?

      posted in Controllers
      tortoisedoc
      tortoisedoc
    • RE: Arduino Pro Mini vs Arduino Nano for SerialGateway?

      @hek said:

      Pro mini is only important for serial gateway if you intent to use Vera as controller.

      The raspberry will probably recognize it fine.

      One more piece of info:
      I am running piDome.
      I hooked the radio to the pro mini (following instructions from the wiki) and attached it to the RPy via ftdi / USB; then I flashed it with the snippet provided in the wiki (which in the wiki is given for the nano).
      Although from piDome I can see the driver, it appears no devices are currently visible.
      Is there an easy way to verify connectivity between the serial gw and the sensors without pidome?

      posted in Controllers
      tortoisedoc
      tortoisedoc
    • Arduino Pro Mini vs Arduino Nano for SerialGateway?

      Hi folks!
      I am new around here and very much interested in getting things to work!
      I have some temperature sensors built on Pro mini's with dallas & radio (nfr24);
      I have a raspberry pi B+ model;
      so all I am missing is a serialgateway. I found this:
      http://mysensors.org/build/serial_gateway
      but it refers to Arduino Nano.
      Thing is, I would like to use an arduino pro mini (Atmel 328, 8Mhz ) instead, to keep cost-efficiency (via ftdi module).
      Can i use the same code snippet as provided by the page above?
      I think not, but before starting development I wanted to double-check if someone had tried the same before?

      Thanks!

      posted in Controllers
      tortoisedoc
      tortoisedoc