HASSIO 0.70 on RPi with serial gateway attached still having configuration check problem with mysensors when executing

hassio ha check

This is what I did to try to solve:

• Deleted the configuration.yaml and the mysensors.json

• Restarted the RPi and hassio installed the default configuration.yaml

• Added the following mysensors configuration to the default configuration.yaml

mysensors:
  gateways:
    - device: '/dev/ttyUSB0'
      persistence_file: 'mysensors.json'
  persistence: true
  retain: true
  version: '2.2'

• Restarted the Rpi and checked that hassio had installed the mysensors.json in the /config directory
  All my sensors were added to the mysensors.json

• The whole system seems to work OK!

• However when I run "hassio ha check" on the RPi I get the following error:

core-ssh:~# hassio ha check
ERROR
Testing configuration at /config
Failed config
  mysensors:
    - Invalid config for [mysensors]: /config directory does not exist or is not                                   writeable for dictionary value @ data['mysensors']['gateways'][0]['persistence_                                  file']. Got 'mysensors.json'
not a valid value for dictionary value @ data['mysensors']['gateways'][0]['devic                                  e']. Got '/dev/ttyUSB0'. (See /config/configuration.yaml, line 59). Please check                                   the docs at https://home-assistant.io/components/mysensors/
    - config: ?
      frontend: ?
        javascript_version: auto
      group: ?
      history: ?
        exclude: ?
        include: ?
        use_include_order: False
      http: ?
      introduction: ?
      logbook: ?
      logger: [source /config/configuration.yaml:52]
        default: info
        logs: [source /config/configuration.yaml:54]
          homeassistant.components.mysensors: debug
          mysensors: debug
      mysensors: [source /config/configuration.yaml:59]
        gateways: [source /config/configuration.yaml:60]
          - device: /dev/ttyUSB0
            persistence_file: mysensors.json
        persistence: True
        retain: True
        version: 2.2
      script: ?
      updater: ?
        include_used_components: False
        reporting: True
Successful config (partial)
  mysensors

• There are no errors in the system log! According to the log the system is reading and writing fine to and from the mysensors.json

• The secondary annoyance from this problem is the fact that I cannot reload the configuration file after a change. The only way to reload the configuration file is by powering off/on the RPi

• I added an issue on github: https://github.com/home-assistant/hassio/issues/478

Any help appreciated

peerv created this issue in home-assistant/hassio

closed Configuration error with MySensors #478

I am now at 0.69.1 HASS on Rpi and still having configuration check problem.

This is my configuration:

mysensors:
  gateways:
    - device: '/dev/ttyUSB0'
      persistence_file: '/config/mysensors.json'
      baud_rate: 115200
  optimistic: false
  persistence: true
  retain: true
  version: '2.0'

And this is the configuration check ERROR:

core-ssh:~# hassio ha check
ERROR
starting version 3.2.4
Testing configuration at /config
Failed config
  mysensors:
    - Invalid config for [mysensors]: /config directory does not exist or is not writeable for dictionary value @ data['mysensors']['gateways'][0]['persistence_ file']. Got /config/mysensors.json'
not a valid value for dictionary value @ data['mysensors']['gateways'][0]['device'].
Got '/dev/ttyUSB0'. (See /config/configuration.yaml, line 85). Please check the docs at https://home-assistant.io/components/mysensors/

A secondary result of this error is the restarting the Rpi does NOT load a new configuration!
The only way to load a new configuration file is to power off/on the Rpi.

However all the rest seems to funtion well !?

Really need help with this.

@iteafreely When I make a configuration change, this change is not gone thru after a restart. I have to power off/on the RPi to activate the configuration change.
So, you think this is also because of this configuration error

On the latest HASSIO release now and still not solved Can someone help with this problem?

core-ssh:~# hassio ha check
ERROR
starting version 3.2.4
Testing configuration at /config
Failed config
  mysensors:
    - Invalid config for [mysensors]: /config directory does not exist or is not writeable        
for dictionary value @ data
['mysensors']
['gateways'][0]
['persistence_file']. Got '/config/mysensors.json'not a valid value for dictionary value @ data
['mysensors']
['gateways']
[0]
['device']. Got '/dev/ttyUSB0'. 
(See /config/configuration.yaml, line 85). 
Please check the docs at https://home-assistant.io/components/mysensors/

The mysensors.json and configuration.yaml are in the same config directory.
Despite the above problem the system seems to work fine.

Is this a fake error?

How can I prevent all the "state_changed" events being written in the hassio database.
It is taken up a lot of dataspace and has no historic meaning.
The Recorder component does not seem to support excluding "events" . The recorder component seems to support only the exclusion of "entities" and "domains".
Any suggestions welcome.

How can I implement the new 2.2.0 function

#define MY_SIGNAL_REPORT_ENABLED

Should it be defined in the node and/or the gateway?
Can it be used with NRF24?
How is the RSSI value reported?
Could not find a writeup on this new function.

@qqlapraline Just use a 5V pro mini and get rid of level converter and mosfet!
Power the 5V HC-SR04 sonar with a pro mini digital pin.
Switch on the sonar for doing a measurement and then switch off again and put the promini to sleep till the next measurement.

@mfalkvidd Thanks for confirming about the BC message being normal protocol.
I have used the log parser (great!) and the trouble shooting flowchart (great!).
I am currently powering thru USB but as the comms problem is intermittend I need some further investigation.

I have a serial gateway with one nodeid=20 running for some time with no problems.
Getting comms problems with a second nodeid=22 when added to the same gateway.

Below is the debug log from nodeid=22 with the communication problems.
On the 4th line is a READ from nodeid=20. I don't have REPEATER MODE defined!
There is also a broadcast message MSG:BC

What could be wrong here?

124187 !TSF:SND:TNR
124194 MCO:SLP:MS=6000,SMS=0,I1=255,M1=255,I2=255,M2=255
124199 !MCO:SLP:TNR
124436 TSF:MSG:READ,20-20-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
124441 TSF:MSG:BC
124585 TSF:MSG:READ,0-0-22,s=255,c=3,t=8,pt=1,l=1,sg=0:0
124591 TSF:MSG:FPAR OK,ID=0,D=1
126053 TSM:FPAR:OK
126054 TSM:ID
126056 TSM:ID:OK
126057 TSM:UPL
126095 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
126220 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
126225 TSF:MSG:BC
126537 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=1,st=NACK:0
126647 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
126652 TSF:MSG:BC
127391 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=2,st=NACK:0
128102 TSM:UPL
128139 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=3,st=NACK:1
128690 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
128695 TSF:MSG:BC
129430 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=4,st=NACK:0
130147 TSM:UPL
130184 !TSF:MSG:SEND,22-22-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=5,st=NACK:1```

Found a new distance sensor HC-SR04P .
De spec shows that the input voltage of this model is 3-5V. So this model can be used with a 3.3V arduino.
https://www.aliexpress.com/snapshot/0.html?spm=a2g0s.9042647.6.2.1AslKf&orderId=89862296499774&productId=32711959780