Of course you could use rpi as gateway, but as personal advice I'd suggest to get some mini pro as sensor nodes and keep the Uno as the gateway or the prototype platform. The most flexible solution would be to make an mqtt ethernet gateway and use rpi as mqtt broker and controller with openhab or whatever else you like, since the mqtt in the middle allows also to have multiple controllers. I also wanted to try openhab and tried openhabian but it turned out to be too complicated, so I moved to domoticz and it was much easier to put things together.
@hakha4 said in Multiple relay arduino nano:
Or use a Mcp23017, 16 extra pins and only sda/scl pins from Arduino (I have a functioning sketch for this including reading multiple ds1820 sensors that can be used as a template. Let me know of you want this)
ds18x20 need 1 pin for up to 255 sensors(can't remember exactly but more than practical).
@robert said in Multiple relay arduino nano:
I would like to connect an 8 channel relays to arduino nano. I use rs485 communication. Rs485 uses pins 2,8,9. How to make 2,3,4 used? I miss pins.
Without knowing what else you're using it's impossible to know how to help you. but you may use A0-A7 as digital outputs too.
@nagelc Its al from jung. Series AS500. Its hard for me to search for sellers in the US.. Google forces me to search in the Netherlands.
My understanding that the standard inwall boxes in North America are pretty different than in Europe /Netherlands . The types I use always look like this
But I'll share my kicad files on openhardware.io, only thing you have to do is change the backplate.
This sensor : link
Also made a repeater, but this one is fairly unsafe( I got zapped installing it ). I just got the PCB's for a safer version I hope I can post pictures when everything works.
@tjog the gateway does not remember anything, regardless if you have a controller or not.
Nodes can be programmed to remember their state. The example with rotary encoder at https://www.mysensors.org/build/dimmer does that if you want something to base your sketch on. Note that the first example on that page does not store state; it relies on a controller instead.
Not sure what you mean by rules, but if you enter rules in your controller they will most likely depend on the controller being available.
@roberto Really supportive of the community to join this discussion.
I see there is a desire by the community unmet by what you're able to provide: local LAN controller. The obvious reasons include both the complexity that you might have in various cloud services that would be difficult to setup in a small LAN, the variance in server hardware or software to host the controller, and the IP that might become obvious if you ship a parsed language such as python.
This might actually be mitigated if you're willing to offer a docker image of a controller: supporting (or not-supporting: support yourselves, hackers!) is more consistent if one docker image can run on whatever orchestration we use, and we gain the ability to hit a local resource without uptime and latency and cloud-ness to worry about.
Understanding the subtle-but-continuous increase of cost in cloud services, this allows your uber-elite users that may generate above-average query load to shunt this load to their own resources.
Additionally, you'd seem like even more awesome people for doing this. Very cutting-edge. Define the next level of customer interaction and independence, GDPR privacy issues, etc.
I bet if you made a dummy service -- some go routine or python flask that simply responds with logical bogus values -- the open source community would build the docker image for you. Overnight.
Anyhow, it's a thought.