Mozilla Webthings MySensors add-on / adapter
-
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 :)
-
@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.
-
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
-
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.
-
The new version has been accepted.
-
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.
-
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.
-
Version 0.1.4 has now been accepted.
-
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.
-
It has been accepted.
-
Thank you !
-
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!
-
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!
@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.
-
A bit of a side-note, but I've created a theme (the very first one!). It also adds thermostat setpoint buttons.

-
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
-
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
@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

-
@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

-
@badmannen not even, was working with the humidity percentage so I kept the same for the battery :)
MyMessage batPercentMsg(CHILD_ID_BATTERY, V_HUM);