• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight Nano USB interface
Same thing here. I purchased my Nano here: http://www.amazon.de/gp/product/B00P7QO012 and the transmiter here: http://www.amazon.de/gp/product/B00YMMFJJO
The Nano has the latest pilight-usb-nano and pilight itself is on nightly (tested on v7.0-47 and v7.0-42)

- Sending is working fine
- Receiving works fine too and then stops after a few hours

@curlymo: does it make a difference where purchased / would it help if I purchase another one from you ;o)


Attached Files Thumbnail(s)
   
 
Reply
What does the black chip on back say?
 
Reply
- Atmel MEGA328P-AU 1514
- WCH CH340G
 
Reply
The CH340G is probably the issue. I only sell those with a RS232 (compatible) chip.
 
Reply
ok, I just purchased the full kit from your shop.
I will peep you posted if this solved the issue.
 
Reply
YES! got my pilight nano through the mail, very easy setup and fast learning curve in comparison to the pi setup and config the first time. Flashed it, copy-ed the config.json from my pi, changed the hardware settings and removed the webserver-http-port stetting and some invalid paths. started the deamon and pilight-receive is working! Stared my chrome browser (poort 5001) on the same machine and got the pilight screen shortly, but said that is could not connect, the daemon had stopped working, could not find a hint on the form, running win 10 in 64 bit, the pilight log and daemon -D did not give any clues. Any help appreciated.
 
Reply
Can you post the output of -D anyway? Is it reproducible?
 
Reply
Here is some more information about the crash. I have also run it on another windows system (win 7 x64), same resault. Also stripped the config.json to minimum, no help.

thanks for any help.

pilight-daemon -D
Code:
[Oct 12 18:01:31:977921] pilight-daemon: INFO: version 6.0, commit v6.0-43-ga27d09f
[Oct 12 18:01:31:977921] pilight-daemon: DEBUG: ssdp sent search
[Oct 12 18:01:31:993561] pilight-daemon: NOTICE: no pilight daemon found, daemonizing
[Oct 12 18:01:31:993561] pilight-daemon: INFO: daemon listening to port: 5000
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread socket, 1 thread running
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread ssdp, 2 threads running
[Oct 12 18:01:31:993561] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 50119
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread sender, 3 threads running
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread broadcaster, 4 threads running
[Oct 12 18:01:31:993561] pilight-daemon: INFO: connected to port COM3
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: client fd: 792
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: client id: 1
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread 433nano, 5 threads running
[Oct 12 18:01:31:993561] pilight-daemon: DEBUG: new thread receive parser, 6 threads running
[Oct 12 18:01:31:993561] pilight-daemon: NOTICE: php support disabled due to missing php-cgi executable
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: new thread events client, 7 threads running
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: new thread events loop, 8 threads running
[  Oct 12 18:01:32:9128] pilight-daemon: NOTICE: php support disabled due to missing cat executable
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: ssdp sent search
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: ssdp sent notify
[  Oct 12 18:01:32:9128] pilight-daemon: NOTICE: php support disabled due to missing base64 executable
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: webserver listening to port 5001
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: new thread webserver worker #0, 9 threads running
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: new thread webserver client, 10 threads running
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: new thread webserver broadcast, 11 threads running
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: ssdp sent search
[  Oct 12 18:01:32:9128] pilight-daemon: DEBUG: ssdp sent notify
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"core":1},"media":"web"}

[ Oct 12 18:01:32:24754] pilight-daemon: INFO: new client, ip: 192.168.1.236, port: 50120
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: client fd: 1136
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1},"media":"all"}

[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: client id: 2
[ Oct 12 18:01:32:24754] pilight-daemon: INFO: new client, ip: 192.168.1.236, port: 50121
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: client fd: 1144
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: client id: 3
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1},"media":"all"}
[ Oct 12 18:01:32:24754] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_wx500
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: called alecto_wx500 parseCode()
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_wsd17
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: called alecto_wsd17 parseCode()
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_ws1700
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: called alecto_ws1700 parseCode()
[Oct 12 18:01:55:199914] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1391,"temperature":20.7},"origin":"receiver","protocol":"alecto_wsd17","uuid":"0000-6c-62-6d-940910","repeats":1}
[Oct 12 18:01:55:215543] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1391,"temperature":20.7,"humidity":46.0,"battery":1},"origin":"receiver","protocol":"alecto_ws1700","uuid":"0000-6c-62-6d-940910","repeats":1}
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: caught minimum # of repeats 2 of alecto_wx500
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: called alecto_wx500 parseCode()
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: caught minimum # of repeats 2 of alecto_wsd17
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: called alecto_wsd17 parseCode()
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: caught minimum # of repeats 2 of alecto_ws1700
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: called alecto_ws1700 parseCode()
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1391,"temperature":20.7},"origin":"receiver","protocol":"alecto_wsd17","uuid":"0000-6c-62-6d-940910","repeats":2}
[Oct 12 18:01:55:621793] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1391,"temperature":20.7,"humidity":46.0,"battery":1},"origin":"receiver","protocol":"alecto_ws1700","uuid":"0000-6c-62-6d-940910","repeats":2}
[Oct 12 18:02:06:268044] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_wx500
[Oct 12 18:02:06:269027] pilight-daemon: DEBUG: called alecto_wx500 parseCode()
[Oct 12 18:02:06:269969] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_wsd17
[Oct 12 18:02:06:271034] pilight-daemon: DEBUG: called alecto_wsd17 parseCode()
[Oct 12 18:02:06:272079] pilight-daemon: DEBUG: broadcasted: {"message":{"id":250,"temperature":51.0,"humidity":34.0,"battery":1},"origin":"receiver","protocol":"alecto_wx500","uuid":"0000-6c-62-6d-940910","repeats":1}
[Oct 12 18:02:06:273001] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_ws1700
[Oct 12 18:02:06:274027] pilight-daemon: DEBUG: called alecto_ws1700 parseCode()
[Oct 12 18:02:06:275028] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1520,"temperature":8.7},"origin":"receiver","protocol":"alecto_wsd17","uuid":"0000-6c-62-6d-940910","repeats":1}
[Oct 12 18:02:06:276043] pilight-daemon: DEBUG: broadcasted: {"message":{"id":1520,"temperature":8.7,"humidity":77.0,"battery":1},"origin":"receiver","protocol":"alecto_ws1700","uuid":"0000-6c-62-6d-940910","repeats":1}
[Oct 12 18:02:19:203839] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50138
[Oct 12 18:02:19:204839] pilight-daemon: NOTICE: caching c:/pilight/web/default/index.html
[Oct 12 18:02:19:308845] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50139
[Oct 12 18:02:19:308845] pilight-daemon: NOTICE: caching c:/pilight/web/default/jquery-2.0.2.min.js
[Oct 12 18:02:19:340847] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50140
[Oct 12 18:02:19:341847] pilight-daemon: NOTICE: caching c:/pilight/web/default/jquery.mobile-1.4.2.min.js
[Oct 12 18:02:19:346847] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50142
[Oct 12 18:02:19:349848] pilight-daemon: NOTICE: caching c:/pilight/web/default/pilight.js
[Oct 12 18:02:19:353848] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50141
[Oct 12 18:02:19:356867] pilight-daemon: NOTICE: caching c:/pilight/web/default/moment.min.js
[Oct 12 18:02:19:360848] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50143
[Oct 12 18:02:19:366849] pilight-daemon: NOTICE: caching c:/pilight/web/default/jquery.mobile-1.4.2.min.css
[Oct 12 18:02:19:372849] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50144
[Oct 12 18:02:19:381849] pilight-daemon: NOTICE: caching c:/pilight/web/default/pilight.css
[Oct 12 18:02:19:399850] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50145
[Oct 12 18:02:19:399850] pilight-daemon: NOTICE: caching c:/pilight/web/default/pilight.jquery.theme.css
[Oct 12 18:02:19:601862] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50147
[Oct 12 18:02:19:601862] pilight-daemon: INFO: client connected, ip 192.168.1.236, port 50148
[Oct 12 18:02:19:604862] pilight-daemon: NOTICE: caching c:/pilight/web/default/images/ajax-loader.gif

config.json
Code:
{
    "devices": {
        "raam": {
            "protocol": [ "kaku_switch_old" ],
            "id": [{
                "unit": 1,
                "id": 0
            }],
            "state": "on"
        },
        "tafel": {
            "protocol": [ "kaku_switch_old" ],
            "id": [{
                "unit": 1,
                "id": 7
            }],
            "state": "on"
        }
    },
    "rules": {},
    "gui": {
        "raam": {
            "name": "Raam",
            "group": [ "woonkamer" ],
            "media": [ "all" ],
            "readonly": 0
        },
        "tafel": {
            "name": "Tafel",
            "group": [ "woonkamer" ],
            "media": [ "all" ],
            "readonly": 0
        }
    },
    "settings": {
        "port": 5000,
        "log-level": 4,
        "log-file": "./pilight.log"
    },
    "hardware": {
        "433nano": {
            "comport": "COM3"
        }
    },
    "registry": {
        "webgui": {
            "tabs": 1
        },
        "pilight": {
            "firmware": {
                "version": 3,
                "lpf": 80,
                "hpf": 16000
            },
            "version": {
                "current": "7.0"
            }
        }
    }
}
 
Reply
The -D output looks all right to me...
Can you post a screenshot and detailed explanation (steps) of what happens?
 
Reply
I don't see anything crashing.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  how to compile pilight with custom protocol code? am i missing something? stanwebber 2 90 07-05-2021, 03:49 AM
Last Post: stanwebber
  hardware info lost after pilight restart Rschnauzer 3 259 03-17-2021, 11:44 AM
Last Post: Rschnauzer
Question pilight stopped working sl4m01 3 957 11-26-2020, 09:17 PM
Last Post: PPacman
  pilight-raw changes output format from 7 to 8 Rschnauzer 1 641 11-26-2020, 01:52 PM
Last Post: curlymo
Question pilight nightly webgui offline after some hours fleisch 4 694 10-26-2020, 05:19 PM
Last Post: fleisch
  pilight bugs Ascenion 1 662 03-23-2020, 06:29 PM
Last Post: curlymo
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 4,520 12-21-2019, 09:46 AM
Last Post: curlymo
  pilight-control modify values coolinx 16 3,631 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 3,105 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 986 08-13-2019, 05:43 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)