ivesdebruycker / node-red-contrib-maxcube Goto Github PK
View Code? Open in Web Editor NEWA node-red node to control the eQ-3 Max! Cube
License: Other
A node-red node to control the eQ-3 Max! Cube
License: Other
Hi,
I cloned your repo to the node_modules/node-red-node-maxcube/ directory and tried to install it via sudo npm install
after I renamed package.js to package.json.
But I think I meese up a LITTLE?
Can you help how I can use it?
Hi,
I've installed the node-red-contrib-maxcube and it worked fine. Since two days I am not able to send the temperature. I get all information (in debug) like before an no errors.
I have no idea how to fix this.
Problem: Right now it's a bit confusing to keep track of rf_address in flows for maxcube. To make life a lot simpler, I would propose to add one or maybe two config fields to the out node:
And maybe a bit forward looking, but nevertheless:
Hi Team,
I was wondering is it possible this note to connect when we request data and then dissect from the cube.
If the cube is always in use there is no way to access the data from other apps.
Thanks.
Hi there, would you mind, putting this on npmjs for the ease of installation?
P.S.:
would you mind renaming your package to node-red-contrib-maxcube? It's considered the convention for third-party packages and it might be easier for others to find it.
All getting this error when installing node-red-contrib-maxcube with node-red
this is stopping the package from installing and being usable alas
Hi
I get a missing sample file when I start nodered
17 Sep 13:00:48 - [warn] [sample] Error: /home/pi/.node-red/node_modules/node-re d-contrib-maxcube/sample/sample.js does not exist
17 Sep 13:00:48 - [warn] ------------------------------------------------------
17 Sep 13:00:48 - [warn] Missing node modules:
17 Sep 13:00:48 - [warn] - node-red-contrib-maxcube: maxcube
I used NPM to install and when I list the nodes installed...
~/.node-red $ npm ls --depth=1
/home/pi/.node-red
├─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]
└── [email protected]
I have an amazon dash installed and the node shows up
Looks like maxcube is missing in dependencies section of package.json.
I've got the error:
31 Oct 10:24:31 - [info] Added node types:
31 Oct 10:24:31 - [info] - node-red-contrib-maxcube:maxcube in : Error: Cannot find module 'maxcube'
31 Oct 10:24:31 - [info] - node-red-contrib-maxcube:maxcube out : Error: Cannot find module 'maxcube'
31 Oct 10:24:31 - [info] - node-red-contrib-maxcube:maxcube-server : Error: Cannot find module 'maxcube'
Hi,
I have installed -and am using- this node-red-contrib. It works as in I can read from and send commands to my thermostats. However, there are three major problems that I am not sure how to solve:
This could be quick-n-dirty fixed by setting all thermostats to AUTO mode, but
{"rf_address": "<rf_address>, "degrees": 15, "mode": "AUTO"}
, this command will only set degrees
but not mode
. Therefore, even when a window is opened, my thermostat will let node-red set it to something other than 5 degrees (which it should always be on when a window is open) and therefore, sometimes I have a window opened while the thermostat right below it is set to 18 degreesThe third one is more of a question:
Error: Maxcube not initialised
. Do I need to only have one node each so they do not get in each others way when requesting (or possibly sending) data?Thanks in advance :)
Hi,
I seem to have two related problems with this node and I'm having a hard time figuring out how it could be fixed:
2016-12-30 21:24:02 { [Error: connect ETIMEDOUT 192.168.0.49:62910]
2016-12-30 21:24:02 code: 'ETIMEDOUT',
2016-12-30 21:24:02 errno: 'ETIMEDOUT',
2016-12-30 21:24:02 syscall: 'connect',
2016-12-30 21:24:02 address: '192.168.0.49',
2016-12-30 21:24:02 port: 62910 }
2016-12-30 21:24:02 30 Dec 21:24:02 - [red] Uncaught Exception:
2016-12-30 21:24:02 30 Dec 21:24:02 - Error: Uncaught, unspecified "error" event. (undefined)
2016-12-30 21:24:02 at MaxCubeLowLevel.emit (events.js:144:17)
2016-12-30 21:24:02 at Socket. (/data/node_modules/node-red-contrib-maxcube/node_modules/maxcube/maxcube-lowlevel.js:46:10)
2016-12-30 21:24:02 at emitOne (events.js:77:13)
2016-12-30 21:24:02 at Socket.emit (events.js:169:7)
2016-12-30 21:24:02 at emitErrorNT (net.js:1269:8)
2016-12-30 21:24:02 at nextTickCallbackWith2Args (node.js:442:9)
2016-12-30 21:24:02 at process._tickCallback (node.js:356:17)
2016-12-30 21:24:02
2016-12-30 21:24:02 �[37m�[40mnpm�[0m �[0m�[32minfo�[0m �[0m�[[email protected]�[0m Failed to exec start script
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Linux 3.10.77
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m �[0m�[35margv�[0m "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--" "--userDir" "/data"
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m �[0m�[35mnode�[0m v4.4.7
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m �[0m�[35mnpm �[0m v2.15.8
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m �[0m�[35mcode�[0m ELIFECYCLE
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m [email protected] start: node $NODE_OPTIONS node_modules/node-red/red.js -v $FLOWS "--userDir" "/data"
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Exit status 1
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Failed at the [email protected] start script 'node $NODE_OPTIONS node_modules/node-red/red.js -v $FLOWS "--userDir" "/data"'.
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m This is most likely a problem with the node-red-docker package,
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m not with npm itself.
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Tell the author that this fails on your system:
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m node $NODE_OPTIONS node_modules/node-red/red.js -v $FLOWS "--userDir" "/data"
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m You can get information on how to open an issue for this project with:
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m npm bugs node-red-docker
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Or if that isn't available, you can get their info via:
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m npm owner ls node-red-docker
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m There is likely additional logging output above.
2016-12-30 21:24:02 �[0m
2016-12-30 21:24:02 �[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m Please include the following file with any support request:
2016-12-30 21:24:02 �[0m�[37m�[40mnpm�[0m �[0m�[31m�[40mERR!�[0m�[35m�[0m /usr/src/node-red/npm-debug.log
2016-12-31 10:43:17,stdout,31 Dec 10:43:17 - [error] [maxcube out:b53a8714.1bfd48] Error: Maxcube not initialised
2016-12-31 10:43:16,stdout,31 Dec 10:43:16 - [error] [maxcube in:f19f204d.16c07] Error: Maxcube not initialised
Is there something I'm doing wrong?
Thanks!
Jesse
Hi
as the title implies, on every try to send a payload of the type:
{ "rf_address": "insert_id_here", "degrees": 27 }
I get this error:
'room_id' of undefined
Do I have to parse a room id to the maxcube output node or is there an other error?
it is possible to disable the duty circle.
This is annoying especially during testing.
thanks in advance chris
Hi,
Wall mounted thermostats seems don't report correct data: Actual Temperature is always at 0 and setpoint is too high.
{
"rf_address":"18eb18",
"initialized":true,
"fromCmd":false,
"error":false,
"valid":true,
"mode":"AUTO",
"dst_active":true,
"gateway_known":true,
"panel_locked":false,
"link_error":false,
"battery_low":false,
"valve":4,
"setpoint":81,
"temp":0
}
node-red 0.17.5
node-red-contrib-maxcube 0.0.5 (from master)
maxcube 1.0.6 (npm install)
Using the version of node-red-contrib-maxcube on npm as of today (2016-11-30) on Node Red 0.15.2, I get the above error in the Node Red debug console. Due to this, it seems I cannot send commands to my thermostats. This is also mentioned in ivesdebruycker/maxcube#12 which I guess is the same problem/bug.
I also see entries like
{ "rf_address": "0ba773" }
Which I guess are my window sensors that AFAICS are not (yet) supported?
Hi there,
would it be possible to add the property to set the thermostat mode as well?
cheers,
Ted
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.