Mozilla Webthings MySensors add-on / adapter

[alowhum]

@nca78 So the first issue is gone, right?

The short version:

Your log shows this error: Nanomsg library was terminated, which indicates that the Gateway component that the add-on communicates with has crashed. Your best bet is to restart the WebThings Gateway/Raspberry Pi.

The long version:

If you disable persistence, it does not remove the persistence file. That file is always used to remember all the node ID's that have been handed out.

If you disable persistence, all that happens is that it no longer re-generates all the things after a restart of the gateway/add-on. If persistence is disabled, nodes will only show up once they present themselves. To speed this up, the add-on goes over the list of stored node ID's and asks all of them, one per second, to re-present themselves. Another way to get them to re-present themselves is to simply restart the node.

If you remove a thing in the Gateway, the latest version (0.0.5) also removes its data from the persistence file. In other words: if you remove a thing, you will most likely have to restart the node if you want it to show up on the 'add things' page again.

"It's recreating the sensor from Persistance, but that sensor was removed from the thing detail page before, so it should not have any persistance left ?"

Correct, it should theoretically no longer be in the persistence file.

"Also the recreated thing/sensor is not visible anywhere: not in add things, not in things view."

Then how do you know it's been recreated? From the log?

Strange that the add-on files are still there after removing the add-on. I'm not even sure those files should have ever been there. Did you do a git clone at some point? Perhaps the crashed part of the Gateway also resulted in the add-on not really being removed.

[Nca78]

@alowhum said in Mozilla Webthings MySensors add-on / adapter:

@nca78 So the first issue is gone, right?

No, not at all. I still can't add any node in MySensors.

Your log shows this error: Nanomsg library was terminated, which indicates that the Gateway component that the add-on communicates with has crashed. Your best bet is to restart the WebThings Gateway/Raspberry Pi.

I did, it didn't work

"It's recreating the sensor from Persistance, but that sensor was removed from the thing detail page before, so it should not have any persistance left ?"

Correct, it should theoretically no longer be in the persistence file.

Well from the log I believe it's still here ?

"Also the recreated thing/sensor is not visible anywhere: not in add things, not in things view."

Then how do you know it's been recreated? From the log?

Yes, from the log as it's not visible anywhere else. And neither are new nodes. Very frustrating :(

Strange that the add-on files are still there after removing the add-on. I'm not even sure those files should have ever been there. Did you do a git clone at some point? Perhaps the crashed part of the Gateway also resulted in the add-on not really being removed.

No I never fiddled directly with the files. I think I will do it now, my guess is the problem is related to those messages I see in log when I remove the add-on:

2019-05-30 09:45:07.158 INFO   : Unloading MySensorsAdapter
2019-05-30 09:45:07.166 INFO   : mysensors: AddonMangerProxy: recv: b'{"messageType":"unloadAdapter","data":{"adapterId":"mysensors-adapter","pluginId":"mysensors-adapter"}}'
2019-05-30 09:45:07.179 INFO   : mysensors: Shutting down MySensors adapter
2019-05-30 09:45:07.181 INFO   : mysensors: MySensors adapter was unable to cleanly close PyMySensors
2019-05-30 09:45:07.183 INFO   : mysensors: AddonMangerProxy: recv: b'{"messageType":"unloadPlugin","data":{"pluginId":"mysensors-adapter"}}'
2019-05-30 09:45:10.188 INFO   : Killing mysensors-adapter plugin.

[Nca78]

So connected with SSH and the directory is gone now.
I reinstalled the add-on and I didn't have those messages about files already existing, only success messages.

But I don't get why it still has my configuration for MySensors gateway URL etc. I install the add-on and after install it connects directly to the MySensors gateway.

I don't know what happened also but it seems I had a problem with the gateway too as I didn't have sensor info in it's log. Now I reprogrammed it and I see log when sensor sends and I have the sensor in the add sensor view.

No idea of what happened, but it seems problem was with my own sensors/gateway and not the add-on :)

[alowhum]

@Nca78 Glad to hear it.

I suspect that because part of the gateway had crashed, all the things you thought you did never actually happened. You never really deleted the thing, and hence the persistence data was still there. You never really deleted the add-on, and hence the files were still there.

[alowhum]

Version 0.0.7 has been created, and should hopefully be accepted soon.

It fixes the issue that the user's preference for which capability should be shown centrally was reset every time the add-on restarted.

Internally, the add-on always uses persistence. Whether devices are shown as 'connected' is now an option. You can either immediately show all MySensors nodes as 'connected' upon a restart, or wait until nodes have sent a signal.

// It has been accepted

[alowhum]

Version 0.1.0 has been accepted. Persistence is a bit faster and hopefully more robust. Hopefully it fixes an issue @rmalbers was experiencing.

[alowhum]

Version 0.1.2 has been uploaded. It has a lot of new features:

• Automatic serial port searching. User doesn't need to add a serial port ID manually anymore (but can if they want)
• Support for metric/imperial units. You can set your preference in the add-on settings.
• Support for multipleOf. This should help show a sane amount of decimals on numeric variables.
• Experimental MQTT support based on user feedback.
• Anticipates switch to version 0.9 of the WebThings gateway by implementing title support.

[alowhum]

The new version has been accepted.

[alowhum]

I have uploaded a new version (0.1.4) that should hopefully be accepted in the coming days.

It allows MySensors devices to better work with voice control.

Its main new ability is that it can split up a single MySensors device into several. The reason this is important is that in the webthings gateway you currently cannot change property names, only thing names. By essentially creating many things with only one property, this problem is circumvented.

It also has some small improvements in MySensors V-types support.

[Nca78]

Thanks you @alowhum, is the splitting systematic or done in settings/configured ?

[alowhum]

@nca78 It's a setting, it's optional.

[alowhum]

Version 0.1.4 has now been accepted.

[alowhum]

Version 1.0.0 has been submitted to Mozilla.

• Support for time-outs. After a user-defined period of not receiving any sign of life (data/heartbeat), a node will be set to disconnected.
• Support for the new WebThings thermostat capability.

[alowhum]

It has been accepted.

[Nca78]

Thank you !

[rmalbers]

Thanks, I have the timeout set (to 30 minutes) and it seems to be working, GREAT! In other news, it looks like they added metric to the gateway with the new release last night and all my temp readings reverted to 'Cent', the new default, until I switched it off 'metric', scared me for a second!

[alowhum]

@rmalbers Thanks for suggesting the idea.

@rmalbers said in Mozilla Webthings MySensors add-on / adapter:

In other news, it looks like they added metric to the gateway with the new release last night and all my temp readings reverted to 'Cent', the new default, until I switched it off 'metric', scared me for a second!

Yeah I have to figure out how the add-on can get this value from the gateway instead.

[alowhum]

A bit of a side-note, but I've created a theme (the very first one!). It also adds thermostat setpoint buttons.

[badmannen]

I been searching around in the forum but I cannot find a way how to send the Battery % so the WEBTHINGS will recognize it , can anyone give me a hint?

at the moment I report it in from my battery node with:
sendBatteryLevel(batteryPcnt);

but I assume this does not get forwarded to the controller?
so should I send it as a separate "child node ID , message?
and which one would be most clever?

thank you

[Nca78]

@badmannen said in Mozilla Webthings MySensors add-on / adapter:

so should I send it as a separate "child node ID , message?

This is what I do at the moment