Any plan to implement Ethernet GW?

[martinhjelmare]

@Dave-Dan

Yes, please start from the beginning:

Remove the persistence file
Start hass
Wait until you see that hass has (:smile:) connected to the gateway
Start a node
Start the next node

If you can post the serial log from that here, and also the log from hass, that would be great.

[drock1985]

@martinhjelmare

Haven't had any issues with the sensors I have on my Dev unit; so far so good.

Are you thinking of releasing the ethernet GW code in this weeks update?

[Andrew Sanjanwala]

@martinhjelmare

Though I'm eager to try, I can't actually launch the Ethernet Gateway branch in a Windows environment. The best error I can provide is the generic failed to create process on calling hass. Platform is Windows Home Server 2011 running Python 3.5.1. All previous and current release branches of home assistant launch without error.

Any thoughts or other steps I can take to debug it further?

[martinhjelmare]

@drock1985

Good to hear. Have you tried connecting more than one node to the gateway at the same time?

Unfortunately I don't think it will make this release, cause I won't have time until Sunday, and the release might be finished before that. I will add some updates this weekend that you are welcome to try. After that we should be ready for release.

[martinhjelmare]

@Andrew-Sanjanwala

My experience with python on Windows is very limited. How do you normally start home assistant?

[Andrew Sanjanwala]

@martinhjelmare

I typically launch either using hass or hass --open-ui from an administrative powershell session. No-go in either of these two cases.

[martinhjelmare]

@Andrew-Sanjanwala

Did you install directly from my github branch using pip?

[Andrew Sanjanwala]

Alright, false alarm. Root issue in my case was a faulty environment and/or operator that resulted in binaries being compiled for the wrong platform.

Once corrected, it compiled and launched your branch and connected to the gateway without incident. Next up is experimenting with the nodes and actuators. I'll see if the persistence file can be written to.

[martinhjelmare]

@Andrew-Sanjanwala

:thumbsup:

[Dave Dan]

Hey @martinhjelmare,

I've been able to do some tests this time.

From a Sensoring standpoint (retreive information from sensors to show in dashboard) works perfetly fine.

I found the issue that I was referring before.

Let's say you have already included a number of nodes and everything is working but for any reason you want to reset and start again. My logic was to remove the MSPersistance.json file, create a new one and the system will reconfigure again.

What I'm seeing is that if you do that the system enters in a limbo situation where no nodes are added but those that were beforer are not added either. you can't see them in the dashboard nor in the Developers Tools section.

Next step is to start testing relays, dimmers, etc.

Let me know if you need more detils on the scenario.

thanks!

[martinhjelmare]

@Dave-Dan said:

My logic was to remove the MSPersistance.json file, create a new one and the system will reconfigure again.

Can you describe more in detail how you did this? Do you have an example persistence file before and after your modifications?

[Dave Dan]

Sure!

the persistence once I've added some nodes looks like this:

{"104": {"sketch_version": "1.0", "children": {"0": {"id": 0, "values": {"1": "38.0"}, "type": 7}, "1": {"id": 1, "values": {"0": "22.0"}, "type": 6}, "2": {"id": 2, "values": {"23": "34"}, "type": 16}, "3": {"id": 3, "values": {"16": "0"}, "type": 1}}, "battery_level": 0, "sensor_id": 104, "type": 17, "sketch_name": "dyaSensor (HTLM)"}, "106": {"sketch_version": "1.0", "children": {"0": {"id": 0, "values": {"1": "37.0"}, "type": 7}, "1": {"id": 1, "values": {"0": "22.0"}, "type": 6}, "2": {"id": 2, "values": {"23": "5"}, "type": 16}, "3": {"id": 3, "values": {"16": "0"}, "type": 1}}, "battery_level": 9, "sensor_id": 106, "type": 17, "sketch_name": "dyaSensor (HTLM)"}, "156": {"sketch_version": null, "children": {}, "battery_level": 0, "sensor_id": 156, "type": 17, "sketch_name": null}, "101": {"sketch_version": "1.2", "children": {"0": {"id": 0, "values": {"1": "34.0"}, "type": 7}, "1": {"id": 1, "values": {"0": "21.0"}, "type": 6}, "2": {"id": 2, "values": {}, "type": 16}, "3": {"id": 3, "values": {"16": "0"}, "type": 1}}, "battery_level": 0, "sensor_id": 101, "type": 17, "sketch_name": "dyaSensor (HTLM) v1.2"}, "102": {"sketch_version": "1.0", "children": {"0": {"id": 0, "values": {"1": "36.0"}, "type": 7}, "1": {"id": 1, "values": {"0": "18.0"}, "type": 6}, "2": {"id": 2, "values": {"23": "69"}, "type": 16}, "3": {"id": 3, "values": {"16": "0"}, "type": 1}}, "battery_level": 2, "sensor_id": 102, "type": 17, "sketch_name": "dyaSensor (HTLM)"}}

after my modification (meaning, clear everything) looks this way:

{}

[martinhjelmare]

@Dave-Dan

Did you do it like this?

1. Stop hass.
2. Remove old persistence file.
3. Create new persistence file with the same name and path, containing an empty JSON object, "{}".
4. Start hass.
5. Start node. Result: Messages are coming in to gateway, but node sensors are not added to entities nor shown in GUI.

[Dave Dan]

Exactly that.

maybe something to do with the fact that those items are already included in the DB (for history, etc) and the system can't add them again? (just guessing)

One more thing.

If I move the file and create a new one instead of deleting it. And after trying to add the items again I stop everything and restore the backup everything works again.

[martinhjelmare]

@Dave-Dan

I don't know yet, but I'll try to reproduce this and figure it out. Thanks for this report, and taking your time to test this.

I haven't had time to push my latest commits, that I had planned. I want to just test them quickly on my side before I push. But since you experience this problem, I think it's best to troubleshoot this first, before I push any new commits.

I'll post back here, once I have more info.

[Dave Dan]

hey @martinhjelmare,

would it be possible to have an updated compilation with the 0.16 versión? I think the one you have above is 0.15 still (or older, right?)

I'd like to do more testing and integrate other items (for example the new Vera integration) with MySensors actuations, etc.

thanks in advance.

[martinhjelmare]

@Dave-Dan

I'd like to investigate the issue you reported before I push any new commits or rebase off dev. Sorry to keep you waiting.

[Dave Dan]

ahh, ok, makes sense.

no problem at all! :)

[drock1985]

@Dave-Dan

out of curiosity, did you try a different name for the persistence file after deleting your first one, or did you use the same name?

[Dave Dan]

hey @drock1985,

No I didn't test that before, but I just did with the same results :(

I can see in the log how messages are arriving to HA (see below). It's just I can't see them either in the group I created for them or in the Developer Tools.

16-03-31 09:42:37 DEBUG (Thread-20) [mysensors.mysensors] Received 101;1;1;0;0;20.0

16-03-31 09:42:37 DEBUG (Thread-20) [mysensors.mysensors] Received 101;0;1;0;1;36.0

16-03-31 09:42:37 DEBUG (Thread-20) [mysensors.mysensors] Received 101;3;1;0;16;0

If I go back and restore the previous file I can see them on both the group and the Developer Tools section.

@martinhjelmare, hope this helps as well ... is is there any specific test you want me to perform please let me know.