Looks like I got the V0.9 Mozilla Gateway update last night, everything seems to be working fine. I now have a decimal digit on my temp readings that was not there prior to the upgrade. (73.4 F now, 73 F previous version)

@mfalkvidd Thank you, I was unsure where to post the question and as you can tell, unsure what code was responsible for the C or F setting.

I didn't know for sure which thread to put this update under but I'll put it here: I updated to the new add-on version. I rebooted everything and I can confirm this the 'imperial' setting is working with my sensors. I had one sensor that has the code in it to check that setting and before I was getting the reading in C and the C label. Now with that sensor I am getting a F reading and a F label. GREAT! I did have to reboot a couple of things more than once! At this point I'm wondering that the boot order should be. Also I'm thinking that I need to unplug everything in the chain and plug things back in the right order, like Mozzilla gatewat first, then the MySensors gateway, the plug the MySensor sensors back in to get it all to work right. Anyway, this is really looking good!

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!

This isn't really a gateway issue but it happened to my rasp pi gateway so I thought I would put this out here in case it happens to someone else: My Mozilla Webthings with MS addon has been running fine since last June and then a few days ago I could no longer connect. I tried rebooting and still no go, tried a few more times and no connection. So,, I'm thinking my SSD might be corrupted so I reinstalled the M gateway code and it doesn't work. So,,, then I put a full rasbian os SD card in the rasp pi and it boots up with the LIGHTENING BOLT (with same power supply I've been using the whole time). So anyway, I try another power supply that works on another (same version) rasp pi 3b+ and it gets lightening bolt also. Anyway, the whole thing was getting a little old so I ordered a new power supply that is certified for 3b+ and now it's working again. So, my rasp pi 3B+ looks like it's started to draw more power for some reason all of the sudden and faked me out on what the problem was. I guess I'll see if the rasp pi is going bad or something but it's running again for now. Moral of the story, check for power issues FIRST, LOL!

Yes, that worked to user the V_DIMMER! Not sure if I can post a screenshot: (I guess I can!)

@alowhum I see that one of the requirements for this new candle webthing gateway is "Sonoff Zigbee 3.0 USB stick". If I don't use any zigbee 'things', do I still need that for an install to work? I have mysensor things and native webthing things only. I lost remote access a month or so ago to my webthing controller (known issue but doesn't appear to be fixed) so I am thinking about switching to this 'new' candle controller. I use remote monitoring when I am away from the house to make sure the furnaces, etc. are working. Also, can I run my old webthing controller and this new candle webthing controller at the same time on my network while I get it going (probably a dumb question but I don't know)? I have another rasp pi I can install the new one on.

Is this a good thing or a bad thing? in other words, will this help the evolution of the gateway or should I start looking for something else?

It's a mysensor esp8266 wifi gateway to a rasp pi3+ mozilla webthings gateway running the mysensor plugin (and weather).

I'm not sure how long this has been going on because I've been out of town but for a few weeks in the Mozilla WebThings Gateway my 'mysensors' suddenly appear as inactive, all of them (six). The 'weather addon is active and still works the whole time. To get they mysensors back all I have to do is reboot the webthings (PI) gateway and they all come back working. This setup has/had been working for almost a year. In the gateway logs the last messages I see are: 2020-06-18 03:39:06.759 INFO : getValue for property 7-0-1 for: TempHumFeelBat returning 49.9
2020-06-18 03:39:06.764 INFO : getValue for property 7-1-0 for: TempHumFeelBat returning 73.94
2020-06-18 03:39:06.766 INFO : getValue for property 7-2-0 for: TempHumFeelBat returning 73.91
2020-06-18 06:45:38.231 INFO : getValue for property 3-0-0 for: Temperature Sensor returning 72
2020-06-18 11:19:18.821 INFO : Starting certificate renewal.
2020-06-18 11:19:18.834 INFO : Certificate not yet due for renewal.
2020-06-18 11:19:26.413 INFO : Checking for add-on updates...
2020-06-18 11:19:26.951 INFO : Finished updating add-ons

It's almost like after check for updates it shut down. What other logs should I be looking at to help figure out what's going on. Oh, my Mozilla gateway code is on autoupdate, I'm on the latest version, 0.12.

@Ray So the weather addon is not even working/being found?

@Ray Have you rebooted the mysensor sensor after everything else has been running.

@skywatchYup same software, just a boot to the raspbain desktop on each one, just idling at the desktop after boot from same sd card, one shows lightening bolt, other one fine. Same sd card, same power supply, same cable, just two different rasp pi 3b+ boards.

Yes, that worked to user the V_DIMMER! Not sure if I can post a screenshot: (I guess I can!)

I was just thinking, V_DIMMER is there for light dimmers - percentage, I'll just use that to get my send battery percentage back to a Webthing, it looks like 'dimmer' is supported!

Title really has it all, is there a way to send: sendBatteryLevel percentage to be displayed as a 'thing' to monitor the battery level of a sensor. I think this is a trace of the sendBatteryLevel message in the mysensor log: "98655 TSF:MSG:SEND,7-7-0-0,s=255,c=3,t=0,pt=1,l=1,sg=0,ft=0,st=OK:100" Is there a 'generic' way of sending a percentage to a Mozilla 'thing'?