Troubleshooting

Hi! This project has been on hold since I burned my FTDI adapter. Back to you in a few weeks when a new one arrives from China :)

@torfinn said in ATMega328p 8Mhz internal, standalone, mysensors low power problem: #define MY_REGISTRATION_FEATURE Disabled This has no effect, the correct approach would be to comment this line: https://github.com/mysensors/MySensors/blob/master/MyConfig.h#L146

@mfalkvidd This worked well for me, for a vibration sensor: if (sleep(digitalPinToInterrupt(MOTION_INPUT_PIN), CHANGE, SLEEP_TIME) != -1) { // Interrupt occurred, do whatever is needed and then // clear any "floating" interrupts before going on. while (sleep(digitalPinToInterrupt(MOTION_INPUT_PIN),CHANGE,1000) != -1 ) { Serial.println("Clearing interrupts"); } }

The correct way to use any ESP8266 based boards with the current MySensors implementation is to configure them as WiFi Gateways with local sensors. You cannot make one ESP8266 an serial GW and expect all other ESPs to communicate via this one using the WiFi. I other words all your ESPs will be Gateways but without any transport (NRF24L01 or RFM69 that is currently supported).

@hugch It depends on what backend you use. If you use soft signing, all secrets and state-flags/preferences are in EEPROM. If you use ATSHA204A secrets are in the ATSHA204A while the state-flags/preferences are in EEPROM. The secrets are specific to the security infrastructure (HMAC, serial). The state-flags/preferences are specific to the MySensors library (node signing requirements). And if it was the wrong serial in the EEPROM, it was a whitelisting problem, as the serial is only used for whitelisting. If you use soft signing, your serial will be fetched from EEPROM (currently). If you use ATSHA204A serial will be fetched from ATSHA204A.

@logbuilder great work. Thanks for reporting back.

@user2684 Yes, if i remember I also encountered same kind of behaviour (packet collisions, not sync ..) Unfortunately, you'll have to wait a bit for the new rfm69 driver before it's in master branch, because it changes the packet format. The PR is now handled by Super @tekka , big thx again :) and my fork is deprecated for the moment. Actually i'm finishing some hardware before going back to software :disappointed_relieved: so i can take a look and test some part of your nice lib :+1: with my low power nodes

@mfalkvidd @exdj21 Thanks for reporting, bugfix submitted: https://github.com/mysensors/MySensors/pull/800 For an immediate fix in 2.1.1/RFM95.cpp line 58, change to: *ptx++ = (uint8_t)0x00;

@gohan said in New to MySensors - how to get started: Start reading around the site https://www.mysensors.org/build Thx, seems like there is some help there :-)

Alright I got this figured out, atleast my version of it. I wanted to document it here incase anyone else runs into Similar. I’m using ethernet gateway also(ESP8266) so my first thought was there was something wrong with that, even though it had just been working with Domitcz and OpenHAB days before. I connected to the gateway to view the serial output which returned following when being reset: dhcp client start... ...ip:192.168.1.172,mask:255.255.255.0,gw:192.168.1.1 .IP: 192.168.1.172 0;255;3;0;9;Init complete, id=0, parent=0, distance=0 I was able to ping, so it appeared to be connecting to my network fine. I then restarted HomeAssistant and received: 0;255;3;0;9;Client 0 connected and when restarting again 0;255;3;0;9;Client 0 disconnected So after that It seemed as though my configuration.yaml was correct and HA actually was connecting despite nothing showing up on the GUI. I turned my attention to my “Sensor”(window Opener) Node. The sketch I had used had worked just fine for Domoticz and OpenHAB, and I had assumed the gateway would appear in HA like it had in other controllers I’d used. Fixed/added a few things from the Sketch and WHALA problems solved. Things I fixed/Added using example sketch here as [https://home-assistant.io/components/mysensors/reference](link url): I noticed in void presentation function I was presenting as S_STATUS rather than S_BINARY present(CHILD_ID, S_BINARY); Added Following lines to in void loop function send Initial Status to controller if (!initialValueSent) { //initialValueSent is Global Variable Defined Above Serial.println("Sending initial value"); send(msg.set(<function to get current state>); Serial.println("Requesting initial value from controller"); request(CHILD_ID, V_STATUS); wait(2000, C_SET, V_STATUS); } added corresponding lines in void receive to change initialValueSent to false. This wasn’t really part of the fix just wanted to note another change I made if (!initialValueSent) { Serial.println("Receiving initial value from controller"); initialValueSent = true; } So to sum it up, I believe the main issue was presenting as wrong type, and not sending initial status in my nodes sketch. It wasn’t straight forward to track down since I my gateway/node worked fine in Domoticz and OpenHAB. I also assumed the HA log would show gateway as connected. In the end, I should have just followed/verified the rest of the HA mysensors Instructions ([https://home-assistant.io/components/mysensors/reference](link url)). Hopefully this helps anyone else out with same issue. @tubby after reading over your problem again, It looks like you did the presentation and initial send correctly. I wonder if your Gateway is not actually connecting to your network correctly. It seems as though its connected to your sensor. Are you able to ping your EthernetGateway?

@Straydog it seems to be possible with the cc3000 shield, at least according to https://forum.mysensors.org/topic/2709/mysensors-wifi-gateway-with-arduino-uno-and-cc3000/

That happens because the voltage regulator from usb isn't able to supply enough current during transmission while when on battery probably it had sufficiently stable voltage for transmitting correctly.

@conde From what I can see both of them are Nano 'clones' with with different serial-usb converters. Some clones get the 3.3v supply (what you use for the radio) from the converter chip. This is a weak (low-amperage) supply possibly causing the radio to malfunction. Also when a separate 3.3v ldo is used it can be very weak. As you notice there are many assumptions here. Possilbe solutions: add an extra capacitor to the radio power supply > 47uF -or- power the radio from a different power supply (ldo).

@mfalkvidd Thanks for the help, well, it looks like I have to use a repeater... Anyways, if someone can come up with an explanation, please share! :)

@gohan said in MQTT message does not show (MySensors on ESP8266): Have you considered using easy esp or other similar firmware? Esay esp won't work for me since it depends on the Arduino IDE but I am using platform.io. Any incentives to change? @Yveaux said in MQTT message does not show (MySensors on ESP8266): @pansen said in MQTT message does not show (MySensors on ESP8266): mosquitto_sub -h localhost -t Sonoff-Out Try subscribing to all topics starting with the Sonoff-Out prefix, using a wildcard, and see if that makes a difference: mosquitto_sub -h localhost -t Sonoff-Out/# That was it, thanks! 0 1 0 1 0 1 2.1.1 Sonoff PIR Switch 1.1 0 edit: and some verbose output for completeness: x@x:~$ mosquitto_sub -h localhost -v -t Sonoff-Out/# Sonoff-Out/0/73/1/0/2 1 Sonoff-Out/0/73/1/0/2 0

@AWI Turns out, I was using 47k resistor instead of 4.7k resistor. Now it's working with no issue :)

Well, the gateway does not retain any information about sensors so it is up to the controller to keep sensors info and data. When gateway is restarted all nodes needs to present themselves again but that should not be a problem for the controller, so there should be something wrong with the Vera or plug in

The problem is that domoticz only works with its own fixed topics. It may be worth trying to see if adding a unique sub topic for each gateway, the controller can still recognize the mysensors protocol