Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Integration with NEEO Controller

MikaelJones last edited by

Any idea what is needed to get MySensors to work with the new NEEO home automation system? Would it be even possible or would we need to go "via" another Controller such as Home Assistant or Domoticz?

Neeo consists of both a brain and a remote. However, it's custom so there's no USB port on the brain.
Reply Quote 0
1 Reply Last reply

1
Posts

569
Views

Suggested Topics

Contribution
General Discussion • • edoardoo

2

0
Votes

2
Posts

1246
Views

Hi @edoardoo I actually stumbled on your post a couple of weeks ago! Great writeup! We certainly need contributors. We need help with everything from the visualisation of sensordata in the frontend (considering using d3.js) to mqtt/node.js backend for receiving and processing sensor data. Please contact me or Johan for further discussions.
Serial terminal
Controllers • serialgateway serial protocol • • dzairo

10

3
Votes

10
Posts

5175
Views

Hi dzairo, Just wondering if you still monitor this thread. If so would love to know how to install the ComPort component so I can modify and use your terminal code. For some reason I don't have any luck with adding it to the IDE. thanks, Andy.
Best PC platform for running Esxi/Docker at home?
Controllers • • NeverDie

75

0
Votes

75
Posts

514
Views

@mfalkvidd said in Best PC platform for running Esxi/Docker at home?: @NeverDie ...You can also use the command line tool fstrim to manually discard unused data. Looking into this, I think checking the "Discard" box on the "Hard Disk" tab of the "Create a Virtual Machine" dialog box inside ProxMox may automatically accomplish the same thing. Also the ProxMox dataset that the VM is saved on needs to be set to thin-client. So, those two things plus the ssd emulation that you mentioned, and of course automatic file compression like lz4 needs to be enabled. So, in total, four things need to be set correctly for it to work optimally. Originally I was concerned that because, if using ZFS as the file system, ProxMox only allows storing a VM as a pre-allocated "raw" file (rather than as a qcow2 file as ProxMox would if ProMox were using a linux ext16 file system instead of ZFS) that the file would take up enormous space even if the raw file (i.e. the VM's virtual disk) is mostly empty. So, I did the experiment, and it turns out that is true if the ProxMox dataset isn't configured as "thin-client" or if automatic file compression isn't turned on, but fortunately the true size of the raw file does indeed shrink down if those two conditions are enabled. So, having proved that to myself, I'll pass on the tip: I now create a VM's disk to be as large as I can imagine it would ever need to grow, and then I let the thin-client mechanism maintain the true size of the virtual disk to be only as large as what is actually necessary. This way I don't have to worry that I created too small a VM disk, or that the VM will later outgrow the disk size that was originally allocated for it.
Homie MySensors bridge Controller. For use in OpenHab 3 (and others)
Controllers • • David Dawson

4

3
Votes

4
Posts

70
Views

@David-Dawson great idea for that translation from homie to mysensors and back. but I think it would be a better approach, if mysensors would have the ability to "speak" homie-convention in MQTT optionally (e.g. #MY_GATEWAY_MQTT_HOMIE) that would eliminate the need of tweaking on an extra binding and let mysensors talk an IOT-standard
Best choise for a controller
Controllers • • dzjr

48

0
Votes

48
Posts

938
Views

@monte said in Best choise for a controller: @neverdie but isn't Docker more efficient and simple solution compared to a VM? Considering it will be used for single process anyway. Yes, I think you're right.
testing with different controllers (mqtt brokers)
Controllers • gateway mqtt home assistant • • OldSurferDude

2

0
Votes

2
Posts

24
Views

@OldSurferDude use a host name for the broker in the configure command (--my-controller-url-address=). Add the host name to /etc/hosts on the rpi where the gateway is. Start the MySensors gatway. When you want to switch brokers, modify /etc/hosts again and restart the MySensors gateway.

Integration with NEEO Controller

Suggested Topics

Contribution
General Discussion • • edoardoo

Serial terminal
Controllers • serialgateway serial protocol • • dzairo

Best PC platform for running Esxi/Docker at home?
Controllers • • NeverDie

Homie MySensors bridge Controller. For use in OpenHab 3 (and others)
Controllers • • David Dawson

Best choise for a controller
Controllers • • dzjr

testing with different controllers (mqtt brokers)
Controllers • gateway mqtt home assistant • • OldSurferDude

61
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

Integration with NEEO Controller

Suggested Topics

Contribution General Discussion • • edoardoo

Serial terminal Controllers • serialgateway serial protocol • • dzairo

Best PC platform for running Esxi/Docker at home? Controllers • • NeverDie

Homie MySensors bridge Controller. For use in OpenHab 3 (and others) Controllers • • David Dawson

Best choise for a controller Controllers • • dzjr

testing with different controllers (mqtt brokers) Controllers • gateway mqtt home assistant • • OldSurferDude

61Online

11.4kUsers

11.1kTopics

112.7kPosts

Contribution
General Discussion • • edoardoo

Serial terminal
Controllers • serialgateway serial protocol • • dzairo

Best PC platform for running Esxi/Docker at home?
Controllers • • NeverDie

Homie MySensors bridge Controller. For use in OpenHab 3 (and others)
Controllers • • David Dawson

Best choise for a controller
Controllers • • dzjr

testing with different controllers (mqtt brokers)
Controllers • gateway mqtt home assistant • • OldSurferDude

61
Online

11.4k
Users

11.1k
Topics

112.7k
Posts