Windows GUI/Controller for MySensors
-
@tekka right. Signing exchange is currently only done in the rf protocol, not to the controller. So are there currently any ways for the controller to populate that field?
A future addition of a I_CONFIG message is under discussion where node properties such as signing and other things can be published to a controller, so I suppose that field in the ui is for future use then :) -
@petewill said:
Is there a way to see Variables that are sent from my controller (Vera)?
No, not to my knowledge - anybody?
Is there a way to send a message to a node that hasn't checked in with the controller yet? I tried to manually type in a Node and Sensor but was unable to.
You can manually add a node, but not a sensor: in the node tree view: right click | Add node | enter ID.
I will add the manual sensor adding to the feature requests.
@tekka said:
I will add the manual sensor adding to the feature requests.
Great, thanks!
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
Thanks again for all the hard work!
-
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
@tekka said:
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
I have to do more testing over the weekend, but i updated my gateway to 1.5, as my nodes where 1.5 but gate was 1.4, the 1st one i tried, worked without issue.
dont know if it was a fluke/lucky or updating to 1.5 on the gateway solved my issue.. i'll post more as i test more nodes -
@tekka said:
I will add the manual sensor adding to the feature requests.
Great, thanks!
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
Thanks again for all the hard work!
@petewill said:
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
The controller receives messages from the GW but does not intercept messages sent from other controllers (due to the architecture). Similarly, messages sent with MYSController won't appear in Vera.
But this leads me to an interesting idea...let's see :)
-
looking for some help with OTA and a sensebender board.
if i manually reset the board, then it will take the OTA and that works fine.
however, that's the only way i can get it to work.
it doesn't respond to a reboot command (I assume this is because it's sleeping)
and even if i select the battery/sleeping option, when a transmission does come in, it doesn't reset or start an OTA.
the only way so far is to physically PF the device and then the OTA works.
what am i missing?
thanks!EDIT: so this does seems to work.. i spent all morning trying to come up with hack-y ways to get this to work.
using the default sensebender sketch the OTA wait time is set to 300 milli seconds. which is like .3 seconds.
i changed that 3000 (3 seconds) set the FW and waited for the next transmission..boom off it went (the OTA).
so for anyone running into this issue. try this solution.
I cant imagine 3 seconds vs .3 seconds is going to make a huge difference in battery life. -
Looking for help to interpret log data after an OTA update. I am just learning, and successfully OTA'ed a simple DS18B temperature sketch to a node using MysController. Now I am trying to OTA an DHT22 node (the example sketch in 1.5 version, no changes to it.) The firmware OTA seems to go fine, but the Pro Mini never seems to start. Below is the log, I have bolded the log entries I don't understand. As shown, the first bold section comes right after the OTA. The second 16 minutes later is because I pushed the reset button on the pro mini. Any help understanding the log entry is appreciated.
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000200
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010001000C94AE010C94AE010C94ED020C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000100
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010000000C9486010C94D11A0C94FE1A0C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000000
10/5/2015 7:04:01 INFO BL version=257
10/5/2015 7:04:01 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:04:01 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:04:01 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:07:23 RX 24;1;1;0;0;60.5
10/5/2015 7:07:23 RX 24;2;1;0;1;59
10/5/2015 7:11:41 RX 24;1;1;0;0;60.5
10/5/2015 7:11:41 RX 24;2;1;0;1;59
10/5/2015 7:13:24 RX 23;0;1;0;1;55.7
10/5/2015 7:15:59 RX 24;1;1;0;0;60.5
10/5/2015 7:15:59 RX 24;2;1;0;1;59
10/5/2015 7:18:27 CHILD New child discovered, node id=23, child id=1
10/5/2015 7:18:27 RX 23;1;1;0;0;63.0
10/5/2015 7:18:27 RX 23;0;1;0;1;55.9
10/5/2015 7:20:14 INFO BL version=257
10/5/2015 7:20:14 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:20:14 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:20:14 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:21:50 TX 2;0;3;0;13;0
10/5/2015 7:23:32 RX 23;0;1;0;1;56.0
10/5/2015 7:24:26 RX 24;3;1;0;24;78 -
@petewill said:
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
The controller receives messages from the GW but does not intercept messages sent from other controllers (due to the architecture). Similarly, messages sent with MYSController won't appear in Vera.
But this leads me to an interesting idea...let's see :)
@tekka said:
The controller receives messages from the GW but does not intercept messages sent from other controllers (due to the architecture). Similarly, messages sent with MYSController won't appear in Vera.
But this leads me to an interesting idea...let's see :)
Oh, sorry. I thought it did. I can see my light (relays) messages when turning on/off with my Vera but maybe that's the ACKs?
-
Looking for help to interpret log data after an OTA update. I am just learning, and successfully OTA'ed a simple DS18B temperature sketch to a node using MysController. Now I am trying to OTA an DHT22 node (the example sketch in 1.5 version, no changes to it.) The firmware OTA seems to go fine, but the Pro Mini never seems to start. Below is the log, I have bolded the log entries I don't understand. As shown, the first bold section comes right after the OTA. The second 16 minutes later is because I pushed the reset button on the pro mini. Any help understanding the log entry is appreciated.
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000200
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010001000C94AE010C94AE010C94ED020C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000100
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010000000C9486010C94D11A0C94FE1A0C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000000
10/5/2015 7:04:01 INFO BL version=257
10/5/2015 7:04:01 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:04:01 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:04:01 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:07:23 RX 24;1;1;0;0;60.5
10/5/2015 7:07:23 RX 24;2;1;0;1;59
10/5/2015 7:11:41 RX 24;1;1;0;0;60.5
10/5/2015 7:11:41 RX 24;2;1;0;1;59
10/5/2015 7:13:24 RX 23;0;1;0;1;55.7
10/5/2015 7:15:59 RX 24;1;1;0;0;60.5
10/5/2015 7:15:59 RX 24;2;1;0;1;59
10/5/2015 7:18:27 CHILD New child discovered, node id=23, child id=1
10/5/2015 7:18:27 RX 23;1;1;0;0;63.0
10/5/2015 7:18:27 RX 23;0;1;0;1;55.9
10/5/2015 7:20:14 INFO BL version=257
10/5/2015 7:20:14 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:20:14 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:20:14 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:21:50 TX 2;0;3;0;13;0
10/5/2015 7:23:32 RX 23;0;1;0;1;56.0
10/5/2015 7:24:26 RX 24;3;1;0;24;78 -
@tekka Thank you for your response. The sketch does not have a static ID - the line is "gw.begin();" So it should receive a node ID. I had MysController set to "AutoID" and it successfully issued the next free ID, which was 2. How would I test further to see why it does not begin execution. (I am using ethernet gateway with authentication, but the configuration is set to 'false', so a node not asking for Atsha response does not get one. Other non-atsha nodes work fine-as shown in the log. Don't know if this would make a difference.)
-
@tekka, In thinking about your question .... As the sketch begins execution after OTA'ing, it then asks for a node id to be issued (even though it has received one from the MysController) - and since I am using an ethernet gateway (& Domoticz) which does not automatically issue a node ID, the pro mini just sits there and waits for a node id? Would it then work if I put in a static node ID, even if it is different than the one issued by Myscontroller? And the node then adopts the static ID. ??
-
@tekka I tried 2 new nodes with static id assigned [gw.begin(incomingMessage, 21, false);] and [gw.begin(NULL, 23, false);] ---- still same frozen response.
10/5/2015 17:18:46 TX 3;255;4;0;3;1400010000000C9486010C94D81A0C94051B0C94AE01
10/5/2015 17:18:46 RX 3;255;4;0;2;140001000000
10/5/2015 17:18:47 INFO BL version=257
10/5/2015 17:18:47 INFO Send FW info to node 3: type=14, version=1, blocks=0x0570, CRC=0xE30B
10/5/2015 17:18:47 TX 3;0;4;0;1;1400010070050BE3
10/5/2015 17:18:47 RX 3;255;4;0;0;1400010070050BE30101
10/5/2015 17:20:32 RX 1;0;1;0;0;19.5and:
10/5/2015 16:59:29 TX 2;255;4;0;3;1400010000000C9486010C94D11A0C94FE1A0C94AE01
10/5/2015 16:59:29 RX 2;255;4;0;2;140001000000
10/5/2015 16:59:29 INFO BL version=257
10/5/2015 16:59:29 INFO Send FW info to node 2: type=14, version=1, blocks=0x0570, CRC=0x2E9E
10/5/2015 16:59:29 TX 2;0;4;0;1;1400010070059E2E
10/5/2015 16:59:29 RX 2;255;4;0;0;1400010070059E2E0101
10/5/2015 17:00:59 RX 24;1;1;0;0;62.8Any idea what the nodes are waiting for?
I also reset the gateway to see if it sent anything that cleared the freeze, but no response. Hmmm.
-
@tekka I tried 2 new nodes with static id assigned [gw.begin(incomingMessage, 21, false);] and [gw.begin(NULL, 23, false);] ---- still same frozen response.
10/5/2015 17:18:46 TX 3;255;4;0;3;1400010000000C9486010C94D81A0C94051B0C94AE01
10/5/2015 17:18:46 RX 3;255;4;0;2;140001000000
10/5/2015 17:18:47 INFO BL version=257
10/5/2015 17:18:47 INFO Send FW info to node 3: type=14, version=1, blocks=0x0570, CRC=0xE30B
10/5/2015 17:18:47 TX 3;0;4;0;1;1400010070050BE3
10/5/2015 17:18:47 RX 3;255;4;0;0;1400010070050BE30101
10/5/2015 17:20:32 RX 1;0;1;0;0;19.5and:
10/5/2015 16:59:29 TX 2;255;4;0;3;1400010000000C9486010C94D11A0C94FE1A0C94AE01
10/5/2015 16:59:29 RX 2;255;4;0;2;140001000000
10/5/2015 16:59:29 INFO BL version=257
10/5/2015 16:59:29 INFO Send FW info to node 2: type=14, version=1, blocks=0x0570, CRC=0x2E9E
10/5/2015 16:59:29 TX 2;0;4;0;1;1400010070059E2E
10/5/2015 16:59:29 RX 2;255;4;0;0;1400010070059E2E0101
10/5/2015 17:00:59 RX 24;1;1;0;0;62.8Any idea what the nodes are waiting for?
I also reset the gateway to see if it sent anything that cleared the freeze, but no response. Hmmm.
-
@tekka, problem solved! I took a debug log from the node per your suggestion and was surprised to get:
radio init fail
radio init fail
radio init fail
This of course surprised me after it just finished downloading 20kb+. Turns out after I made the first test of OTA which worked fine, my home network automatically synchronized my laptops & desktop. This brought over a copy of myconfig.h which had softspi enabled! (I had been setting up the gateway on a different computer). So when I went to OTA on the second and third nodes it picked up the synched myconfig.h. Ugh, such little strange things that take so much time to find.
@tekka, my apologies for using some of your time. And my Thanks for your great work and sharing with the community!! Hopefully others will avoid similar mistakes by reading this. -
Hi @tekka , I'm trying to create a simple thermostat device and I'm usually using your fantastic controller for prototype testing and debugging. Now I would need the possibility to send setpoint values from the controller and the current version of MYSController does not seem to support the following:
V_HVAC_SETPOINT_COOL 44 HVAC cold setpoint S_HVAC
V_HVAC_SETPOINT_HEAT 45 HVAC/Heater setpoint S_HVAC, S_HEATER
V_HVAC_FLOW_MODE 46 Flow mode for HVAC ("Auto", "ContinuousOn", "PeriodicOn") S_HVACI would greatly appreciate it is these features were implemented to your fantastic controller also.
Best regards,
Tomas -
sorry if this has been asked before.
but I have a nano with mySbootloader installed and when i look at it in the serial monitor its just all gibberish.
i tried different speeds, but still the same.
is it not possible if you have that bootloader installed? or do i need to do something else.?
thx -
Hi @tekka , I'm trying to create a simple thermostat device and I'm usually using your fantastic controller for prototype testing and debugging. Now I would need the possibility to send setpoint values from the controller and the current version of MYSController does not seem to support the following:
V_HVAC_SETPOINT_COOL 44 HVAC cold setpoint S_HVAC
V_HVAC_SETPOINT_HEAT 45 HVAC/Heater setpoint S_HVAC, S_HEATER
V_HVAC_FLOW_MODE 46 Flow mode for HVAC ("Auto", "ContinuousOn", "PeriodicOn") S_HVACI would greatly appreciate it is these features were implemented to your fantastic controller also.
Best regards,
Tomas -
sorry if this has been asked before.
but I have a nano with mySbootloader installed and when i look at it in the serial monitor its just all gibberish.
i tried different speeds, but still the same.
is it not possible if you have that bootloader installed? or do i need to do something else.?
thx