another relay problem....



  • Hi,

    Sorry to post another relay problem.
    I read lot of problems solved but not of thos issues resolved mine.

    I copy paste the sketch on HA website for relay sketch on my working arduino.

    I switch on the arduino and thiks is what I see on py log:

    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 3-16-0 s=1,c=1,t=0,pt=7,l=5,sg=
    0:23.7
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=255,c=3,t=15,pt=2,l=2
    ,sg=0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=255,c=0,t=17,pt=0,l=5
    ,sg=0:1.5.4
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=255,c=3,t=6,pt=1,l=1,
    sg=0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:send: 0-0-18-18 s=255,c=3,t=6,pt=0,l=
    1,sg=0,st=ok:M
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=255,c=3,t=11,pt=0,l=5
    ,sg=0:Relay
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=255,c=3,t=12,pt=0,l=3
    ,sg=0:1.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=1,c=0,t=3,pt=0,l=0,sg
    =0:
    WARNING:mysensors.mysensors:child_id 1 already exists in children, cannot add ch
    ild
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=1,c=1,t=2,pt=2,l=2,sg
    =0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 5-16-0 s=6,c=1,t=23,pt=7,l=5,sg
    =0:6.0
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    

    The relay is registered I think, but no line with "add sensor" and no existence in HA......

    Another thing.. in configuration.yaml, I want t make a persistent file for mysensor, but don't how to. What path can I write to have the persistent file in .homeasssistant folder

    mysensors:
     gateways:
     - device: 'COM5'
     persistence_file: 'mysensors.json'
     baud_rate: 115200
     debug: true
     persistence: true
     version: '1.5'
     optimistic: 'true'
    

    I'm on windows 10
    and last version of HA.
    and mysensor 1.5.2

    Please help 😞
    Thanks in advance.


  • Contest Winner

    @Gefkuz I suggest you take this as a lead in solving your problem:

    WARNING:mysensors.mysensors:child_id 1 already exists in children, cannot add ch
    ild
    


  • @TheoL said:

    @Gefkuz I suggest you take this as a lead in solving your problem:

    WARNING:mysensors.mysensors:child_id 1 already exists in children, cannot add ch
    ild
    

    Search for initial value sending for HASS and mysensors 2.0.0



  • The message "already exist" is not displayed at the first power up.
    And in my log, We can see the first value sended :

    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 18-18-0 s=1,c=1,t=2,pt=2,l=2,sg
    =0:0
    

    Are we ok with this value sended???



  • Is it necessary to migrate to mysensors 2.0?


  • Contest Winner

    @Gefkuz It's hard to tell. I tried to look up the sketch on the HA site. But wasn't able to find it during lunch break. Would you mind posting a linl?



  • here is a link to the sketch i'm using :
    https://home-assistant.io/components/switch.mysensors/#example-sketch
    I'm using the first one. Simple switch sketch.


  • Contest Winner

    @Gefkuz I'm not sure who's responsible of generating the warning

    WARNING:mysensors.mysensors:child_id 1 already exists in children, cannot add ch
    ild
    

    I find it hard to believe that the gateway is generating this warning. But maybe @Hek or @tekka can tell us more about this. I haven't seen this warning before.


  • Plugin Developer

    Hi!

    Everything in the log looks OK, except the node already has the child registered. But you said that doesn't happen when you start the arduino the first time after restart of hass? In that case it should be fine. Otherwise it could be an indication that there are already children loaded from persistence, which could conflict with the new settings.

    It's not necessary to upgrade to mysensors 2.0.0. That's not fully supported either.

    Try setting persistence to false, restart hass and start your arduino node again. If that doesn't work I'd like to see the log from the start of hass with all lines regarding mysensors.


  • Plugin Developer

    @TheoL said:

    @Gefkuz I'm not sure who's responsible of generating the warning

    That would be me.πŸ˜„



  • No more result with persistent file to none (#) and persistent to false.
    Deleting mysensor1.picle file.
    Restarting homeassistant.
    modify the switch to nodeid 56.
    launch the switch.
    And same things.....
    For information, my temperatures sensors (mysensors) working perfectly.



  • I don't have some log file... can you tell me where it is in the folders?


  • Plugin Developer

    You said you're using mysensors 1.5.2, but the log indicates that atleast the node in question is 1.5.4. Is the gateway also on 1.5.4? There was a bug in 1.5.2-1.5.3 regarding payloads.


  • Plugin Developer

    @Gefkuz

    The log is usually in the same directory as the configuration.

    I prefer to just start hass manually and look/copy the output at the console.



  • i check it now


  • Contest Winner

    @martinhjelmare I already had a gut feeling that the gateway doesn't generate message's like this. Because it was designed to be a gateway with as less logic in it as possible πŸ˜‰ Glad you cleared that one.



  • Hi,

    I reprogram the gateway with same pc than the switch, then the same mysensor library.
    I launch homeassistant without persistent file mysensor.
    And same problem... 😞 😞

    Microsoft Windows [version 6.3.9600]
    (c) 2013 Microsoft Corporation. Tous droits rΓ©servΓ©s.
    
    C:\Users\Fabien>py -m homeassistant
    Config directory: C:\Users\Fabien\AppData\Roaming\.homeassistant
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=turn_off>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=turn_on>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=toggle>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=reload_core_config>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=persis
    tent_notification, service=create>
    INFO:homeassistant.bootstrap:Home Assistant core initialized
    INFO:homeassistant.loader:Loaded script from homeassistant.components.script
    INFO:homeassistant.loader:Loaded group from homeassistant.components.group
    INFO:homeassistant.loader:Loaded input_select from homeassistant.components.inpu
    t_select
    INFO:homeassistant.loader:Loaded media_player from homeassistant.components.medi
    a_player
    INFO:homeassistant.loader:Loaded http from homeassistant.components.http
    INFO:homeassistant.loader:Loaded weblink from homeassistant.components.weblink
    INFO:homeassistant.loader:Loaded automation from homeassistant.components.automa
    tion
    INFO:homeassistant.loader:Loaded shell_command from homeassistant.components.she
    ll_command
    INFO:homeassistant.loader:Loaded camera from homeassistant.components.camera
    INFO:homeassistant.loader:Loaded mysensors from homeassistant.components.mysenso
    rs
    INFO:homeassistant.loader:Loaded frontend from homeassistant.components.frontend
    
    INFO:homeassistant.loader:Loaded api from homeassistant.components.api
    INFO:homeassistant.loader:Loaded history from homeassistant.components.history
    INFO:homeassistant.loader:Loaded recorder from homeassistant.components.recorder
    
    INFO:homeassistant.loader:Loaded input_slider from homeassistant.components.inpu
    t_slider
    INFO:homeassistant.loader:Loaded switch from homeassistant.components.switch
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=recor
    der>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=input_
    select, service=select_option>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=input_select.station, new_state=<state input_select.station=BBC Radio Be
    rkshire; options=['BBC Radio Berkshire', 'BBC Radio Two', 'Heart'], friendly_nam
    e=Station, icon=mdi:radio-tower @ 2016-08-17T21:07:10.881326+02:00>>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=input
    _select>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=http>
    
    ERROR:homeassistant.bootstrap:Invalid config for [media_player]: required key no
    t provided @ data['platform']. Got None
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=weblink.freebox, new_state=<state weblink.freebox=http://192.168.1.1; fr
    iendly_name=FreeBox, icon=mdi:router-wireless @ 2016-08-17T21:07:11.146946+02:00
    >>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=webli
    nk>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=shell_
    command, service=battery>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=shell
    _command>
    INFO:homeassistant.loader:Loaded camera.generic from homeassistant.components.ca
    mera.generic
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=camera.london_road, new_state=<state camera.london_road=idle; entity_pic
    ture=/api/camera_proxy/camera.london_road?token=60691888, access_token=60691888,
     friendly_name=London Road @ 2016-08-17T21:07:11.240702+02:00>>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=camer
    a>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=mysen
    sors>
    ERROR:homeassistant.bootstrap:Invalid config for [switch]: required key not prov
    ided @ data['platform']. Got None
    INFO:homeassistant.loader:Loaded sensor from homeassistant.components.sensor
    INFO:homeassistant.loader:Loaded binary_sensor from homeassistant.components.bin
    ary_sensor
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=api>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=senso
    r>
    INFO:homeassistant.core:Bus:Handling <Event platform_discovered[L]: service=load
    _platform.sensor, platform=mysensors, discovered=>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=binar
    y_sensor>
    INFO:homeassistant.core:Bus:Handling <Event platform_discovered[L]: service=load
    _platform.binary_sensor, platform=mysensors, discovered=>
    INFO:homeassistant.loader:Loaded light from homeassistant.components.light
    INFO:homeassistant.loader:Loaded sensor.mysensors from homeassistant.components.
    sensor.mysensors
    INFO:homeassistant.loader:Loaded binary_sensor.mysensors from homeassistant.comp
    onents.binary_sensor.mysensors
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=front
    end>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=light,
     service=turn_on>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=light,
     service=turn_off>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=light,
     service=toggle>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=light
    >
    INFO:homeassistant.core:Bus:Handling <Event platform_discovered[L]: service=load
    _platform.light, platform=mysensors, discovered=>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=histo
    ry>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=input_
    slider, service=select_value>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=input_slider.volume, new_state=<state input_slider.volume=50; max=100, s
    tep=1, min=0, friendly_name=Volume, icon=mdi:volume-high @ 2016-08-17T21:07:13.0
    53199+02:00>>
    INFO:homeassistant.loader:Loaded light.mysensors from homeassistant.components.l
    ight.mysensors
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=input
    _slider>
    ERROR:homeassistant.bootstrap:Invalid config for [switch]: required key not prov
    ided @ data['platform']. Got None
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=group
    >
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=script.battery, new_state=<state script.battery=off; friendly_name=batte
    ry, icon=mdi:refresh @ 2016-08-17T21:07:13.178206+02:00>>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=script
    , service=battery>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=script
    , service=turn_on>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=script
    , service=turn_off>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=script
    , service=toggle>
    INFO:homeassistant.core:Bus:Handling <Event component_loaded[L]: component=scrip
    t>
    ERROR:homeassistant.bootstrap:Invalid config for [automation]: required key not
    provided @ data['action']. Got None
    required key not provided @ data['trigger']. Got None
    INFO:homeassistant.core:Starting Home Assistant (17 threads)
    INFO:homeassistant.core:Bus:Handling <Event homeassistant_start[L]>
    INFO:homeassistant.core:Timer:starting
    INFO:mysensors.mysensors:Trying to connect to COM4
    INFO:mysensors.mysensors:COM4 is open...
    INFO:mysensors.mysensors:Connected to COM4
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:gateway started, id=0, parent=0, dist
    ance=0
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=stop>
    INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=homeas
    sistant, service=restart>
    INFO:homeassistant.components.http:Serving /api/stream to 192.168.1.1 (auth: Tru
    e)
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:homeassistant.components.http:Serving /api/bootstrap to 192.168.1.1 (auth:
    True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=1,c=1,t=0,pt=7,l=5,sg
    =0:28.4
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 1-16-0 s=1,c=1,t=0,pt=7,l=5,sg=
    0:29.8
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 1-16-0 s=0,c=1,t=1,pt=7,l=5,sg=
    0:37.6
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=255,c=3,t=15,pt=2,l=2
    ,sg=0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=255,c=0,t=17,pt=0,l=5
    ,sg=0:1.5.4
    INFO:homeassistant.components.mysensors:No sketch_name: node 55
    INFO:homeassistant.components.mysensors:No sketch_name: node 55
    INFO:homeassistant.components.mysensors:No sketch_name: node 55
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=255,c=3,t=6,pt=1,l=1,
    sg=0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:send: 0-0-55-55 s=255,c=3,t=6,pt=0,l=
    1,sg=0,st=ok:M
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=255,c=3,t=11,pt=0,l=5
    ,sg=0:Relay
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=255,c=3,t=12,pt=0,l=3
    ,sg=0:1.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=4,c=0,t=3,pt=0,l=0,sg
    =0:
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 55-55-0 s=4,c=1,t=2,pt=0,l=3,sg
    =0:0.0
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=255,c=0,t=18,pt=0,l=5
    ,sg=0:1.5.1
    INFO:homeassistant.components.mysensors:No sketch_name: node 16
    INFO:homeassistant.components.mysensors:No sketch_name: node 16
    INFO:homeassistant.components.mysensors:No sketch_name: node 16
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=255,c=3,t=6,pt=1,l=1,
    sg=0:0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:send: 0-0-16-16 s=255,c=3,t=6,pt=0,l=
    1,sg=0,st=ok:M
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=3,c=1,t=18,pt=7,l=5,sg=
    0:73094056.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 3-16-0 s=0,c=1,t=1,pt=7,l=5,sg=
    0:51.8
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=4,c=1,t=18,pt=7,l=5,sg=
    0:49055452.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=5,c=1,t=39,pt=7,l=5,sg=
    0:0.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=6,c=1,t=39,pt=7,l=5,sg=
    0:0.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 2-2-0 s=0,c=1,t=1,pt=7,l=5,sg=0
    :86.9
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=7,c=1,t=39,pt=7,l=5,sg=
    0:5.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 7-2-0 s=2,c=1,t=2,pt=7,l=5,sg=0
    :0.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=255,c=3,t=11,pt=0,l=1
    1,sg=0:Sonde Salon
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=255,c=3,t=12,pt=0,l=3
    ,sg=0:1.0
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=0,c=0,t=7,pt=0,l=8,sg
    =0:Humidite
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=1,c=0,t=6,pt=0,l=11,s
    g=0:Temperature
    INFO:homeassistant.components.http:Serving /api/camera_proxy/camera.london_road
    to 192.168.1.1 (auth: True)
    INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1):
    62.255.244.49
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=1,c=1,t=0,pt=7,l=5,sg
    =0:28.6
    INFO:homeassistant.components.mysensors:Adding new devices: <Entity Sonde Salon
    16 1: None>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=sensor.sonde_salon_16_1, new_state=<state sensor.sonde_salon_16_1=unavai
    lable; friendly_name=Sonde Salon 16 1 @ 2016-08-17T21:07:48.412571+02:00>>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state s
    ensor.sonde_salon_16_1=unavailable; friendly_name=Sonde Salon 16 1 @ 2016-08-17T
    21:07:48.412571+02:00>, entity_id=sensor.sonde_salon_16_1, new_state=<state sens
    or.sonde_salon_16_1=28.6; node_id=16, unit_of_measurement=Β°C, child_id=1, batter
    y_level=0, device=COM4, V_TEMP=28.6, friendly_name=Sonde Salon 16 1 @ 2016-08-17
    T21:07:48.412571+02:00>>
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=0,c=1,t=1,pt=7,l=5,sg
    =0:1.0
    INFO:homeassistant.components.mysensors:Adding new devices: <Entity Sonde Salon
    16 0: None>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=None, en
    tity_id=sensor.sonde_salon_16_0, new_state=<state sensor.sonde_salon_16_0=unavai
    lable; friendly_name=Sonde Salon 16 0 @ 2016-08-17T21:07:50.412569+02:00>>
    INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state s
    ensor.sonde_salon_16_0=unavailable; friendly_name=Sonde Salon 16 0 @ 2016-08-17T
    21:07:50.412569+02:00>, entity_id=sensor.sonde_salon_16_0, new_state=<state sens
    or.sonde_salon_16_0=1.0; node_id=16, friendly_name=Sonde Salon 16 0, child_id=0,
     battery_level=0, V_HUM=1.0, device=COM4, unit_of_measurement=% @ 2016-08-17T21:
    07:50.443821+02:00>>
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 16-16-0 s=255,c=3,t=1,pt=0,l=0,
    sg=0:
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:send: 0-0-16-16 s=255,c=3,t=1,pt=0,l=
    10,sg=0,st=ok:14714608
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 5-16-0 s=1,c=1,t=0,pt=7,l=5,sg=
    0:29.6
    INFO:mysensors.mysensors:n:0 c:0 t:3 s:9 p:read: 5-16-0 s=0,c=1,t=1,pt=7,l=5,sg=
    0:27.1
    

    really, I don't know what's happen.


  • Plugin Developer

    I think I've found it. The switch platform errors on loading:

    ERROR:homeassistant.bootstrap:Invalid config for [switch]: required key not provided @ data['platform']. Got None
    

    The S_TYPE is 3 and V_TYPE is 2 of your child which maps to the switch platform in home assistant. The mysensors component will try to load the switch platform via discovery but if something else tries to config the same platform and fails, mysensors will also be affected in that platform.

    Can you provide relevant excerpt from your config, mysensors and switch entries?



  • Haha, I think we ahve something.
    My mysensor config is

    mysensors:
     gateways:
     - device: 'COM4'
    # persistence_file: 'mysensors.json'
     baud_rate: 115200
     debug: true
     persistence: false
     version: '1.5'
     optimistic: 'true'
    

    and switch file is empty.... I don't see anything about that in homeassistant website...
    What can I do?



  • I make some tests.
    I switch v_type and s_type values in my sketch.
    And when I write S_BINARY or S_LIGHT........ no add sensor appeared....


  • Plugin Developer

    @Gefkuz said:

    and switch file is empty.... I don't see anything about that in homeassistant website...

    What do you mean switch file is empty? Have you split your config into different yaml files? If so you can't point to an empty file in your main config file. Remove unused entries from your config. You seem to have problems with other platforms also besides switch.



  • You've got it.
    Your a chief.
    I have deleted all references of empty files in my config file.
    And it works perfectly....
    Youhou.!!!!!!!!!!!!!!!!

    Many thanks to all.....
    And now, automation.. Yeah!!!


 

442
Online

7.9k
Users

8.7k
Topics

93.6k
Posts