Posts made by mardah

Would it be possible to skip the 74HC86D and use a pin change interrupt instead? And still support on/off switches?

Hi

I think I have read all threads about adding nodes to HA but I have not found a solution to my problem.

I have an existing Ethernet GW and several nodes around the house. Currently I'm using Vera and all nodes and GW are working. I would like to switch to HA and have added the following to configuration.yaml

mysensors:
  gateways:
    - device: '192.168.1.31'
      persistence_file: '/home/homeassistant/.homeassistant/mysensors.json'
      tcp_port: 5003
  optimistic: false
  persistence: true
  retain: true
  version: 1.5

When I restart a node it should send presentation followed by initial values. Since it is working with the Vera I assume that part is working but still the nodes aren't added to HA.

2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] Update: node 6, child 255 sub_type 18
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [homeassistant.components.mysensors] No sketch_name: node 6
2017-07-19 09:39:06 DEBUG (Thread-7) [mysensors.gateway_tcp] Sending 6;255;3;0;6;M
2017-07-19 09:39:13 DEBUG (Thread-7) [mysensors.gateway_tcp] Sending 0;255;3;0;2;
2017-07-19 09:39:23 INFO (Thread-7) [mysensors.gateway_tcp] Closing socket at ('192.168.1.31', 5003).
2017-07-19 09:39:23 ERROR (Thread-7) [mysensors.gateway_tcp] Failed to shutdown socket at ('192.168.1.31', 5003).
2017-07-19 09:39:23 INFO (Thread-7) [mysensors.gateway_tcp] Socket closed at ('192.168.1.31', 5003).
2017-07-19 09:39:23 INFO (Thread-7) [mysensors.gateway_tcp] No response. Disconnected.
2017-07-19 09:39:23 INFO (Thread-7) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.31', 5003)
2017-07-19 09:39:23 INFO (Thread-7) [mysensors.gateway_tcp] Connected to ('192.168.1.31', 5003)
2017-07-19 09:39:23 DEBUG (Thread-7) [mysensors.gateway_tcp] Sending 0;255;3;0;2;
2017-07-19 09:39:23 DEBUG (Thread-7) [mysensors.gateway_tcp] Received 0;0;3;0;14;Gateway startup complete.

Why is the Ethernet GW disconnected after the node sends it presentation? Also, the node does send a sketch name and version, it is visible in Vera.

BR
Martrin

I found the problem: https://github.com/LowPowerLab/SPIFlash/issues/16

The sketch I used to verify the SPI Flash was missing a SPI.begin() in setup().

I hooked up a logic analyzer and discovered that there was no activity on SCK, MOSI and MISO when trying to use the SPI Flash.

Wrote my own sketch that only reads the jedec id from the SPI Flash and it worked. Must be something with the SPIFlash lib version.

Attaching a screenshot from the logic analyzer showing the jedec id read from the SPI Flash.

@tbowmo I'm getting pass the initialize which returns true. Since I don't provide a jeedec id it defaults to 0. When I later try to read jeedec I'd from the flash it returns 0 as well.

@scalz if I add the address I get "Init FAIL".

The DAC worked as well so there is only a problem with the SPI Flash. I even replaced the chip but get the same result. Maybe a software issue then.

I have checked wiring and soldering. The radio is working but I will for sure verify the DAC.

Hi

I have a problem with a AT25DF512C SPI flash module. Using the SPIFlash library I can initialize the flash but when I try to read the device ID it is zero. Also if I write data and then read it back it is also zero.

I'm using an ATMega328P-AU TQFP. The flash CS is connected to A2 (16). MOSI, MISO and SCK connected normally. CS has a 4.7k pullup.

Any ideas why the SPI only returns zeros? Please see my schematic at: https://www.openhardware.io/view/348

//Martin

Hello,

Would AT45DB041E be a good choice as a OTA flash? I see it's in the schematics for the new Sensebender Micro mk2.

https://www.adestotech.com/wp-content/uploads/doc8783.pdf

BR
Martin

Does anyone have footprint and 3D model for WS2812B?

I soldered just the two caps and an MCP1703 on a new board and have not manage to fry it. So maybe there is another cause. I'm suspecting the WS2812, it's new on my latest batch of sensor boards. But I don't understand how it could destroy the voltage regulator or ATMega.

Maybe something is wrong with the PCB layout causing some unwanted currents?

The MCP1703 should handle up to 20V input. Maybe the input cap is 10V , I guess it would handle 12V most of the time?

The MCP1703 does provide 3.3V until it fries. But yes, it could be a non genuine voltage regulator.

I have fried several sensor boards when using an external AC/DC adapter supplying 12V/1A. The voltage is regulated with a MCP1703 with 1u caps on both input and output.

I think the problem appears when I unplug and plug in the DC jack to quick? Not sure though. Sometimes just the voltage regulator fries and sometimes the ATMega
fries as well.

If it doesn't fry the first time I plug in the DC jack it can run for a long time.

What could be the problem? Build up of voltage in the AC/DC adapter, the caps? Voltage spikes?

When running on two CR123 in series I have not seen any problems with the sensor board.

I just replaced the batteries in two sensor nodes and got some unexpected battery voltage measurements. Each sensor has two CR123A batteries in series. The voltage is measured with a voltage divider connected to an analog input. Before the batteries was replaced both sensors worked as expected.

Both sensors got brand new Sony CR123A 3V batteries at the same time. The battery voltage measurements from one sensor looks strange. Any ideas?

Why not use a 4-pol screw terminal instead? One common and then one input for each switch. Also, consider if the corners could be 45 degrees instead of 90. That would make it fit more easly in a round back box. Aren't you missing a pull-up for reset and a few decoupling caps for the ATMega?